Stripe: Elevated API errors
What happened?
We're currently investigating elevated error rates and response times with the API. We'll post an update soon.
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
We are investigating an emerging issue with Edge Delivery related to Edge DNS report with record change on master DNS server not reflected to Akamai Edge DNS. We are actively investigating the issue and will provide another update within the next 30 minutes. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support), or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.
View incident →Click any outage to explore the incident.
We're currently investigating elevated error rates and response times with the API. We'll post an update soon.
On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval. If you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select "Re-run all jobs." This preserves the workflow run ID but starts a new attempt, rebuilds artifacts, and requires fresh deployment approvals. Before rerunning, check whether any deployment steps already completed to avoid repeating changes.
We’ve detected email delivery delays affecting a small number of email service providers. The team is actively investigating to identify the full scope and impact. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23061
We are currently investigating an incident that impacted our services. Users may experience issues with authentication functionality. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.
We are investigating an issue with Atlas metrics ingestion that may delay cluster management operations, including cluster creation and modification.
We are investigating increased latency processing Events generated by RUM, Trace Analytics, Service Checks, CI Visibility, Cloud Network Monitoring, and Error Tracking. As a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards since Sep 30, 2026, 5:25 PM UTC To prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally.
Cloudflare is investigating issues with network performance in Madrid (MAD). We are working to analyse and mitigate this problem. More updates to follow shortly.
We are aware of an issue that caused domains hosted on Railway to return 404 errors. The issue lasted approximately 5 minutes and has since been mitigated, this is a post facto report. We are investigating the root cause and will provide updates as we learn more.
We are investigating an issue with the Messaging Logs API. Users may experience higher latency than normal and errors fetching and listing Messaging Logs. We will provide another update in 1 hour or as soon as more information becomes available.
We have identified that users may experience errors creating or interacting with Pages, including failures when using Page tools or connecting to live Page sessions. We are working on implementing a mitigation.
Some Visa transactions may experience lower authorization rates due to a network token processing issue, starting 00:53 UTC September 30th. Eligible payments can continue using card-number fallback. We're working to resolve the issue; no action is required.
We are investigating an emerging issue with Configuration Deployment related to errors while activating delivery configurations in Property Manager. We are actively investigating the issue and will provide another update within the next 30 minutes. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support), or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.
We are investigating an issue causing a high percentage of Access One Time Pin emails to fail. All other authentication methods are operating as normal.
Security and vulnerability reports are not loading or being ingested for some users. We are investigating now. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23024
We’re investigating elevated errors affecting ChatGPT, Codex, and the API. Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more.
We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks. We are actively working on a fix. We will provide updates as the fix is implemented.
We are seeing recovery and are monitoring this incident. Hobby deployments have been re-enabled.
We are investigating elevated error rates affecting Claude.ai (including the desktop and mobile apps), Claude Code and Claude Cowork. Users may see failed requests, errors loading or sending conversations, or be asked to sign in again; retrying may succeed. We will provide an update as soon as possible.
From approximately 06.39 AM to 06:44 AM US Pacific time, we observed an issue impacting All Files Page, Box Notes, API calls, logins and downloads. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.
Flex Plugins CLI is degraded and is unable to publish plugins. Engineering teams have figured out the issue and are actively working to have a patch out. We expect to provide another update in 1 hour or as soon as more information becomes available.
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.