Service Health
-
-
-
-
Incident affecting Apigee
Apigee Edge customers may observe 5xx errors in us-central1 region
Incident began at 2024-06-06 04:27 and ended at 2024-06-06 06:47 (all times are US/Pacific).
Previously affected location(s)
Iowa (us-central1)
| Date | Time | Description | |
|---|---|---|---|
| | 6 Jun 2024 | 09:10 PDT | Mini Incident ReportWe apologize for the inconvenience this service disruption/outage may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support. (All Times US/Pacific) Incident Start: 6 June 2024 00:00 Incident End: 6 June 2024 06:00 Duration: 6 hours Affected Services and Features: Apigee Edge Public Cloud Regions/Zones: us-central1 Description: Apigee Edge Public Cloud customers located in the us-central1 region observed errors and their traffic may have been interrupted. From preliminary analysis, the root cause of the issue is a misconfiguration of the Apigee Edge NATs (Network Address Translation) that caused the expected Elastic IPs not to be present on the NAT nodes. Customer Impact: Apigee Edge Public Cloud customers located in the us-central1 region experienced: Errors for all traffic routed through the affected NAT instances Traffic interruptions Additional details: Elastic IPs attached to NAT instances in us-central1 were unintentionally removed. A manual fix was applied to reattach the correct Elastic IPs. |
| | 6 Jun 2024 | 06:47 PDT | The issue with Apigee Edge has been resolved for all affected users as of Thursday, 2024-06-06 06:30 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| | 6 Jun 2024 | 06:15 PDT | Summary: Apigee Edge customers may observe 5xx errors in us-central1 region Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2024-06-06 07:00 US/Pacific. Diagnosis: Apigee Edge customers located in us-central1 region may observe 5xx errors and their traffic may be interrupted Workaround: None at this time. |
| | 6 Jun 2024 | 05:20 PDT | Summary: Apigee Edge customers may observe 5xx errors in us-central1 region Description: We are experiencing an issue with Apigee Edge beginning on Thursday, 2024-06-06 00:00 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2024-06-06 06:30 US/Pacific with current details. Diagnosis: Apigee Edge customers located in us-central1 region may observe 5xx errors and their traffic may be interrupted Workaround: None at this time. |
| | 6 Jun 2024 | 04:53 PDT | Summary: Apigee Edge customers may observe 5xx errors in us-central1 region Description: We are experiencing an issue with Apigee Edge beginning on Thursday, 2024-06-06 00:00 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2024-06-06 05:30 US/Pacific with current details. Diagnosis: Apigee Edge customers located in us-central1 region may observe 5xx errors and their traffic may be interrupted Workaround: None at this time. |
| | 6 Jun 2024 | 04:50 PDT | Summary: Apigee customers may observe 5xx errors in us-central1 region Description: We are experiencing an issue with Apigee beginning on Thursday, 2024-06-06 00:00 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2024-06-06 05:30 US/Pacific with current details. Diagnosis: Apigee customers located in us-central1 region may observe 5xx errors and their traffic may be interrupted Workaround: None at this time. |
- All times are US/Pacific