Service Health
Incident affecting Apigee
Apigee is experiencing issues loading the Apigee UI at apigee.google.com.
Incident began at 2022-01-11 12:50 and ended at 2022-01-11 15:04 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 12 Jan 2022 | 13:43 PST | We apologize for the inconvenience this service disruption 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 Support by opening a case using https://cloud.google.com/support. (All Times US/Pacific) Incident Start: 11 January 2022 12:50 Incident End: 11 January 2022 15:04 Duration: 2 hours, 14 minutes Affected Services and Features:
Regions/Zones: Global Description: Apigee X and Apigee Hybrid experienced elevated page errors loading the console user interface globally for 2 hours, 14 minutes. From preliminary analysis, the root cause of the issue was due to an uncaught error in a new release. Customer Impact:
Additional details:
|
| 11 Jan 2022 | 16:00 PST | The issue with Apigee has been resolved for all affected users as of Tuesday, 2022-01-11 15:58 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 11 Jan 2022 | 15:22 PST | Summary: Apigee is experiencing issues loading the Apigee UI at apigee.google.com. Description: We believe the issue with loading the Apigee UI is resolved. Engineers are working to confirm full resolution. We will provide an update by Tuesday, 2022-01-11 16:30 US/Pacific with current details. Diagnosis: Users may receive a message "Internal Server Error". Runtime traffic is unaffected. Workaround: None at this time. |
| 11 Jan 2022 | 14:53 PST | Summary: Apigee is experiencing issues loading the Apigee UI at apigee.google.com. Description: We are experiencing an issue with Apigee beginning at Tuesday, 2022-01-11 12:50 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2022-01-11 15:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Users may receive a message "Internal Server Error". Runtime traffic is unaffected. Workaround: None at this time. |
- All times are US/Pacific