ApigeeLogin errors observed on SAML-enabled Apigee Integrated Developer portals
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
We identified it as an OOM Error, Service was resolved and back to normal.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. We apologize for the disruption and will be improving our processes to avoid having this particular issue happen again.
Resolved
This incident has been resolved.
Resolved
It looks like we're back to normal. AWS finally updated their status page. ;) https://phd.aws.amazon.com/phd/home?region=us-east-1#/account/dashboard/open-issues?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_SVALH_1646859683&eventTab=details
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We are continuing to monitor but systems have returned to normal at this time.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Metric ingestion has caught up and all charts are now current.
Resolved
This is a retroactive post on an incident that occurred this morning between 05:39-06:18 PST. We detected elevated errors with our Cassandra service in the US-East region related to a single node event. During this time, customer API calls in this region would have seen intermittent API 5XX errors for approximately 5-10% of their calls for approx. 40 mins. Services in all other regions were not impacted by this incident. The node in question was removed from service to mitigate impact pending further analysis. We're investigating the root cause of this incident and will make the necessary changes to prevent a recurrence of this issue. We apologize for the inconvenience this may have caused you and your business -- and we don't take that lightly. If you have any further questions or may be seeing impacts related to this, please file a case with Support.
Resolved
This incident has been resolved.
Resolved
Increased load caused API service to experience errors from 10:03 - 10:15 PST.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Due to elevated traffic, we experienced intermittent timeouts and errors in serving public pages between 5:57 and 5:58 AM PST. We have made updates to our services to prevent similar problems from happening.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All apps are reachable via the UI and the metrics backlog has been processed.
Resolved
From 2.30 PM UTC to around 4.40 PM UTC, instability in our JCenter mirror and JCenter itself caused disruption for plugin and plugin dependency resolution on the plugin portal.
Resolved
Postmortem can be found at [https://blog.gradle.org/plugins-jcenter](https://blog.gradle.org/plugins-jcenter)
Resolved
We're all good now, thanks folks!
Resolved
Full service has been restored and verified.
Resolved
Between a 6:55am and 7:10am, some API requests from authentic users were rejected by the WAF due to a configuration change. The changes were rolled back immediately and a fix has been implemented. All traffic resumed normally after 7:10am 1/10/2022
Resolved
Between 5:20 to 5:24 AM PST, a slow performing API query resulted in an elevated number of 500 errors on the manage portal. The root cause of the degraded performance has been identified and a fix has been deployed. The manage portal is now operating normally.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
AWS has resolved the incident and we are not experiencing issues anymore. Please contact Support for any queries.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Our records indicate that there was an internet connectivity outage which lasted on our service from approximately 7:20am to 7:50am on December 15, 2021. AWS corroborates this with their own status messages. Because this was a partial internet connectivity outage, some requests continued to resolve during this period. From AWS Service health page on December 15 2021: 7:43 AM PST We are investigating Internet connectivity issues to the US-WEST-2 Region. 8:01 AM PST We have identified the root cause of the Internet connectivity to the US-WEST-2 Region and have taken steps to restore connectivity. We have seen some improvement to Internet connectivity in the last few minutes but continue to work towards full recovery. 8:14 AM PST We have resolved the issue affecting Internet connectivity to the US-WEST-2 Region. Connectivity within the region was not affected by this event. The issue has been resolved and the service is operating normally. 12:14 PM PST Between 7:14 AM PST and 7:59 AM PST, customers experienced elevated network packet loss that impacted connectivity to a subset of Internet destinations. Traffic within AWS Regions, between AWS Regions, and to other destinations on the Internet was not impacted. The issue was caused by network congestion between parts of the AWS Backbone and a subset of Internet Service Providers, which was triggered by AWS traffic engineering, executed in response to congestion outside of our network. This traffic engineering incorrectly moved more traffic than expected to parts of the AWS Backbone that affected connectivity to a subset of Internet destinations. The issue has been resolved, and we do not expect a recurrence.
Resolved
Application down for some users due to regional outage caused by Amazon Web Services
Resolved