Check here before you debug your own stack. A live record of major internet outages: what broke, when it started, and how long the service was down.
Active incident
Our team is investigating an issue affecting the Object Storage for the US-Southeast (Atlanta) region. During this time, users may experience connection timeouts and errors with this service.
View incident →Click any outage to explore the incident.
Starting on 2026-09-16 ~19:00 UTC customers were experiencing 503 errors while calling comms-api messages endpoints. 128 requests took 1 minute and eventually got failed by the timeout. After 19:30 there were no 503 errors observed anymore but the root cause of the issue is unclear.
Some users may not see results from connected content in Notion AI. We’re investigating and will share another update within two hours.
We are investigating an issue with website https://baui.zscalerfeed.net/ba/login. User may observe issue while accessing the reports for malicious md5s.We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.
Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries. An update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.
Some Pruna models may not be able to scale up and are therefore either experiencing long queue times or entirely unavailable. We are working with Pruna to resolve the issue.
Some users on iOS and iPadOS may experience duplicate characters when editing text with a Korean keyboard in the Notion app or Safari. We’ve identified the issue and are working on a fix. We’ll share another update after the fix is available.
We are currently investigating an issue causing formatting anomalies with S3 action destinations. Our team is working on a mitigation.
Starting at 2PM ET, Crashlytics and Performance Monitoring console started experiencing low availability. We are working to remediate ASAP.
We are experiencing a disruption with Kitchen Display System (KDS). Your business operations are our top priority and our Engineering team is working rapidly to resolve this issue. We appreciate your patience during this disruption.
We are investigating elevated errors affecting ChatGPT Work. We will provide updates as we learn more.
We are experiencing an issue with Twilio Console. Twilio Console users will have degraded experience while creating/viewing Restricted API Keys and Oauth Applications. Our engineers are working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
We are aware of an issue affecting users interacting with subscriptions via Google Play, such as when creating a new subscription on Android devices. Google has confirmed an issue with Google Play, and we are awaiting their further updates.
We're currently experiencing an issue that prevents users from completing purchases (including Nitro subscriptions and Shop items) through the Android app. This is caused by an ongoing outage with Google Play. Purchases on other platforms (iOS, web, and desktop) are unaffected, and existing subscriptions remain active. We're monitoring Google's status and will post an update as soon as service is restored. No action is needed on your part — please try again later. https://pay.google.com/status/incidents/gQJsjf662F7KwPyiNqav
We're currently investigating elevated errors on Google Pay payments. We'll post an update soon.
We are investigating a delay in pipeline data becoming available. Pipelines are still running, but data about them may be delayed in the UI or API.
We are experiencing elevated errors within our Image CDN service starting at 12:37 UTC. We are currently investigating this issue.
Fin for Salesforce customers may experience issues due to an upstream error. We have confirmation a fix is being worked on and will update here as soon as we know more.
Zendesk reported a resolved major incident.
There’s a Salesforce service disruption. During a service disruption, end users can’t access the service. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
Our helpdesk provider is currently experiencing issues, and as such customers might encounter errors while submitting or viewing tickets. Responses on customer inquiries may be delayed during this time.
Where our outage data comes from, and how we treat it.
We watch the status pages of the major providers around the clock, so you do not have to check twenty of them.
Every entry comes from an incident reported for that provider. No guess work at play.
Each entry names the provider and the time it was reported, in UTC, so you can check it against their own status page.
Some providers never close an incident. We stop showing an incident as ongoing after 3 days rather than let it run forever.
There's nothing to install. No credit card required. 50 monitors for free.
