Dashboard - Operational
US-Central1 (Google Cloud) - Operational
Europe-West1 (Google Cloud) - Operational
US-East-1 (AWS) - Operational
US-West-2 (AWS) - Operational
US-West-2 (AWS)
Notice history
View current statusOct 2026
Sep 2026
- Resolved · UTC
This incident has been resolved, noted both on our end and by GCP below. All databases appears to be functioning.
Any continuing issues, please email us immediately at support@gigalixir.com.
GCP Note regarding the outage:
September 1, 2026 at 11:09:16 AM UTC-5 Multiple products in us-central1-b are experiencing network service degradation. We are experiencing a networking issue starting Tuesday, 2026-09-01 07:41 US/Pacific. The issue is affecting a portion of the us-central1-b zone. The remaining zones in the region are unaffected. Our network engineering team has put in mitigations and we are seeing services starting to recover. We will provide more information by Tuesday, 2026-09-01 09:30 US/Pacific with current details. - Update · UTC
The AZ is recovering, we are seeing most back online now.
If you still are experiencing issues, write us immediately at support@gigalixir.com so we can investigate. - Update · UTC
Note from GCP:
Google Cloud multi-product customers are experiencing elevated packet loss and errors to/from us-central1-b.
Most recent update – 17 minutes ago September 1, 2026 at 10:38:32 AM UTC-5
Google Cloud multi-product customers are experiencing elevated packet loss and errors to/from us-central1-b. We are experiencing an issue with Hybrid Connectivity Tuesday, 2026-09-01 07:44 US/Pacific. Our engineering team continues to investigate the issue. We will provide more information by Tuesday, 2026-09-01 09:15 US/Pacific with current details. - Monitoring · UTC
We are seeing the zone recovery and most databases should be reachable again. we are still monitoring and will post when all is healthy.
- Investigating · UTC
The us-central1-b availability zone appears to be offline for GCP. Some of our standard tier database in us-central1 region are unreachable at the moment.
We are currently investigating this incident and awaiting GCP action.

