Service Health
Incident affecting Apigee
Some Customers may receive errors while trying to access development Apigee portal.
Incident began at 2024-04-23 13:24 and ended at 2024-04-23 15:53 (all times are US/Pacific).
Previously affected location(s)
Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Osaka (asia-northeast2)Seoul (asia-northeast3)Mumbai (asia-south1)Delhi (asia-south2)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Melbourne (australia-southeast2)Warsaw (europe-central2)Finland (europe-north1)Madrid (europe-southwest1)Belgium (europe-west1)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)Zurich (europe-west6)Milan (europe-west8)Paris (europe-west9)Doha (me-central1)Tel Aviv (me-west1)Montréal (northamerica-northeast1)Toronto (northamerica-northeast2)São Paulo (southamerica-east1)Santiago (southamerica-west1)Iowa (us-central1)South Carolina (us-east1)Northern Virginia (us-east4)Columbus (us-east5)Dallas (us-south1)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)
Date | Time | Description | |
---|---|---|---|
| 23 Apr 2024 | 15:53 PDT | The issue with Apigee has been resolved for all affected customers as of Tuesday, 2024-04-23 15:15 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 23 Apr 2024 | 14:24 PDT | Summary: Some Customers may receive errors while trying to access development Apigee portal. Description: We are experiencing an issue with Apigee beginning at Tuesday, 2024-04-23 12:25 US/Pacific. Our engineering team has mitigated the issue and is currently monitoring the situation for any recurrence. We will provide an update by Tuesday, 2024-04-23 16:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Impacted customers may receive HTML errors instead of correct data while trying to access Apigee portal. Workaround: None at this time. |
- All times are US/Pacific