Segment event delivery issues
What happened?
We have identified that a small no of event delivery is failing. We are currently investigating the issue.
GitHub, OpenAI, Cloudflare, AWS and the other services your product runs on: what is down, when it started and how long it lasted. Check here before you debug your own stack.
Watch your own site, or get an alert when any of the 6,300+ providers you depend on has an incident.
Active incident
There’s a Salesforce service feature degradation. During a feature degradation, some features are unavailable or run at less than optimal performance. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
View incident →Click any outage to explore the incident.
We have identified that a small no of event delivery is failing. We are currently investigating the issue.
We are currently investigating this issue.
There’s a Salesforce service feature disruption. During a feature disruption, end users sometimes can’t access certain aspects of the service. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
A fix has been applied and deployments in EU West (Amsterdam) should now succeed. If a deployment failed during this incident, please redeploy it. We are monitoring the results.
We are investigating elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5. We will provide an update as soon as possible.
We're currently investigating a Partial Service disruption of the Blik payment method that began at 17:12 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the Blik payment method. We are actively monitoring the situation and will provide updates as more information becomes available.
Railway is not currently under attack. Recent API key revocations by AI providers are precautionary actions in response to the October 21 incident, not a new security incident. On October 23, after the attacker’s access had been fully removed on October 22 at 03:32 UTC, AI providers requested another batch of potentially affected keys. We provided that batch to OpenAI and Anthropic, but because we could not filter keys by when they were added, it inadvertently included newer keys. As a result, providers may have revoked replacement keys you created after the incident. These revocations do not indicate that your replacement keys were compromised. You should also receive communications directly from the providers taking action, explaining their response and any steps you need to take. If a provider revoked your key, create a replacement, update the corresponding Railway environment variable, and redeploy the services that use it. If your keys are still working, this notice does not require you to repeat completed rotations. We’re sorry for the confusion and additional disruption.
Cloudflare is investigating issues causing an increase of errors for Workflow Operations. We are working to analyze and mitigate this problem. More updates to follow shortly.
We are investigating elevated errors on requests to Claude Opus 5.5. We will provide an update as soon as possible.
We are investigating elevated errors on requests to Claude Fable 5.1. We will provide an update as soon as possible.
We are investigating the issue for the listed services.
We are monitoring improvement in an incident with delays in incident notifications. We have deployed a fix, and we expect systems to continue to improve. Event ingestion is not affected. We will provide an update within the next 15 minutes.
Our support and community site, station.railway.com, is now restored, you can raise support threads on that property. We have caught up with most support requests. New account signups remain paused and some non-essential product features remain disabled. We will update this notice as functionality restores.
We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23320
We have identified the issue causing delays in Logs and Observability data and are working on a fix. We will provide additional updates as they become available.
We are currently investigating a service degradation affecting multiple Zoom Services. Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available. We appreciate your patience as we work to resolve this issue.
Akamai is aware of the recently published remote code execution vulnerability: CVE-2026-111497.Our subject matter experts are actively investigating and taking the appropriate mitigation actions, while we continue to monitor our platform in parallel. We will provide updates as additional information becomes available.In the interest of time, we are providing you with the most current information available, which is subject to changes, corrections, and updates.
Some customers using the Salesforce Pardot integration are experiencing connection errors that prevent their Zaps from running. Other Pardot connections continue to run normally. We are investigating the ongoing errors and checking recovery of affected connections and delayed Zap runs. If you need any assistance in the meantime, please contact our support team here "here": https://zapier.com/app/get-help.
We are investigating reports of degraded performance for Actions
Users are experiencing issues accessing Notion, including signing in and loading pages. Some users may see a blocked-access message or pages stuck loading. We are investigating and working to restore access.
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.