We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d, beginning on Monday, 2020-06-29 07:54 US/Pacific, affecting multiple Google Cloud Services.
Services in us-east1-d have been restored. Most services in us-east1-c are restored except for Persistent Disk. No ETA for Persistent disk recovery as of now.
Impact is due to power failure. A more detailed analysis will be available at a later time.
Our engineering team is working on recovery of impacted services.
We will provide an update by Monday, 2020-06-29 11:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones.
Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.
We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d, beginning on Monday, 2020-06-29 07:54 US/Pacific, affecting multiple Google Cloud Services.
Services in us-east1-d have been restored. Services in us-east1-c are still being restored. No ETA as of now.
Impact is due to power failure. A more detailed analysis will be available at a later time.
Our engineering team is working on recovery of impacted services.
We will provide an update by Monday, 2020-06-29 10:30 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones.
Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.
The issue with issue with Google Compute Engine in zones us-east1-c and us-east1-d where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:20 US/Pacific has been resolved for all affected users as of Monday, 2020-06-29 09:45 US/Pacific.
We are experiencing an issue with Google Compute Engine in zones us-east1-c and us-east1-d where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:20 US/Pacific.
The impact to us-east1-d looks has been mitigated by Monday, 2020-06-29 08:45 US/Pacific.
The impact to us-east1-c looks has been mitigated by Monday, 2020-06-29 09:45 US/Pacific.
We thank you for your patience while we're working on resolving the issue.
Description: We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d, beginning on Monday, 2020-06-29 07:54 US/Pacific, affecting multiple Google Cloud Services.
We expect services in us-east1-d to be recovering within the next 30 minutes, there is no eta for service recovery for us-east1-c yet.
Impact is due to power failure. A more detailed analysis will be available at a later time.
Our engineering team is working on recovery of impacted services..
We will provide an update by Monday, 2020-06-29 10:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones.
Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.
As a DevOps Engineer at Tenfold you will build out the real-time infrastructure to power the world's first artificial intelligence for sales. You will be setting up and maintaining our cloud-based infrastructure and work to constantly improve our performance and reliability. You will also work closely with developers to set up continuous delivery and ensure that new features can be deployed quickly and smoothly.
THE DAY TO DAY - Use cutting-edge technologies such as AWS, Go, Docker, and Terraform to continue to scale our infrastructure. - Building infrastructure to process terabytes of data per day and thousands of API calls per second. - Relentlessly measure and optimize as Tenfold builds the highest-scale and most advanced analytics platform in the world. - Building fault-tolerant systems to handle millions of events per hour with each event processing under 100ms.
THE PERKS & BENEFITS
(We offer market competitive salaries)
Stock Options (Every employee is an owner in the company)
Health Benefits (Medical, Dental, and Vision)
Transportation (Downtown parking or commuter reimbursement)
Want to learn more? Email either kessiler@tenfold.com or patrick@tenfold.com or check out our Angel List at https://angel.co/growtenfold/jobs/.
Services in us-east1-d have been restored. Most services in us-east1-c are restored except for Persistent Disk. No ETA for Persistent disk recovery as of now.
Impact is due to power failure. A more detailed analysis will be available at a later time.
Our engineering team is working on recovery of impacted services.
We will provide an update by Monday, 2020-06-29 11:00 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones.
Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.