Major incidents SaaS vendor changes, page 3

GitHub’s critical incident degraded Pull Requests and Webhooks and paused enterprise migrations, starting 2026-10-06 19:57 UTC and resolving 2026-10-06 23:40 UTC (3 h 43 min). GitHub reported an outage from 19:44 to 19:50 UTC affecting 12 services, with approximately 1.16 million failed requests. It identified GitHub Enterprise Importer as the trigger and reported deploying a mitigation.

GitHub reported a critical outage affecting Pull Requests, Webhooks and other services, with approximately 1.16 million failed requests. The incident started at 2026-10-06 19:57 UTC and resolved at 2026-10-06 23:40 UTC, lasting 3 h 43 min. Enterprise migrations remained paused after other services recovered; GitHub reported deploying a mitigation.

Cursor reported a major service degradation affecting some Cloud Agents and Grok Bot features, starting at 2026-10-06 19:27 UTC and resolved at 2026-10-06 22:06 UTC, lasting 2 h 39 min. Grok Bot was restored at 10-06 21:25 UTC while Cloud Agents degradation remained under investigation; no cause or fix was stated.

Sentry’s Dashboard was down in both US and EU regions in a critical incident starting at 2026-10-06 18:57 UTC and lasting 42 min. Sentry deployed a fix at 19:20 UTC and marked the Dashboard operational at 2026-10-06 19:40 UTC.

Ashby reported a major incident affecting Recruiting: availability was slow or failed to load through candidate availability links, disrupting candidate booking. It started at 2026-10-06 18:47 UTC and lasted 45 min, resolving at 2026-10-06 19:33 UTC; Ashby applied a fix and confirmed candidate booking was operating normally.

Cursor reported a major service degradation affecting Security Reviewer agents (Review Agents), starting 2026-10-06 17:49 UTC and resolved at 2026-10-06 18:56 UTC after 1 h 7 min. No cause or fix was stated.

Vercel Auth logins failed for pages with Deployment Protection enabled in a major-impact incident affecting Routing Middleware. It started at 2026-10-06 16:10 UTC and was resolved at 2026-10-06 16:26 UTC, lasting 15 min; Vercel reported implementing a fix.

Vercel Auth logins failed for pages with Deployment Protection enabled, affecting Routing Middleware in a major-impact outage. It started at 2026-10-06 16:10 UTC and was resolved at 2026-10-06 16:26 UTC; the reported duration was 15 min. A fix was implemented, but no cause was stated.

CircleCI reported a major incident starting 2026-10-06 16:00 UTC, lasting 5 h 18 min and resolved at 21:18 UTC. Customers experienced pipeline failures, periods when no workflows or jobs started, and delayed UI data, notifications, webhooks, and commit status updates; workflows and jobs were starting normally by 20:31 UTC, and customers whose jobs failed to start were advised to rerun them.

Pulumi reported a major incident affecting inbound OIDC, with API and ESC listed as affected components. It started at 2026-10-06 15:35 UTC and was resolved at 2026-10-06 16:17 UTC, lasting 42 min; no cause or specific fix was stated.

Snowflake’s major outage affected user connections and page loading in AWS - Africa (Cape Town), Azure - UAE North (Dubai), and GCP - Middle East (Dammam). It lasted from 2026-10-06 14:44 UTC to 2026-10-06 15:57 UTC (1 h 13 min); service was restored after a third-party network provider implemented a fix.

Elastic Cloud reported a major incident delaying Cloud UI metrics for Serverless projects in Azure UAE North, starting 2026-10-06 14:04 UTC and resolved at 2026-10-06 17:54 UTC (3 h 50 min). At resolution, delayed “Usage and performance” metrics were recovering and queued usage records were being processed; no data loss was expected.

AssemblyAI reported a major degradation of Universal-3.5 Pro async transcription on its US endpoint: slower processing and failed requests; EU was unaffected. The incident started at 2026-10-06 14:00 UTC and resolved at 2026-10-06 14:25 UTC (25 min), with impact reported beginning at 1:35p UTC. A fix restored normal processing; failed requests can be safely resubmitted.

Claude reported a major incident involving elevated errors for Claude Opus 5.5 across claude.ai, Claude API (api.anthropic.com), Claude Code, and Claude Cowork. It started at 2026-10-06 12:24 UTC and was resolved at 2026-10-06 12:43 UTC, lasting 18 min. Claude said it identified the cause but did not disclose the cause or fix.

Claude Opus 5.5 requests experienced elevated errors affecting claude.ai, Claude API (api.anthropic.com), Claude Code, and Claude Cowork. Anthropic rated the impact major; the incident started at 2026-10-06 12:24 UTC and was resolved at 2026-10-06 12:43 UTC, lasting 18 min. Anthropic identified the cause but did not disclose it or the fix.

ElevenLabs reported a major disruption to Agents SIP calls in its EU residency from 2026-10-06 09:53 UTC to 2026-10-06 12:51 UTC, lasting 2 h 58 min. Error rates returned to normal during monitoring, and ElevenLabs confirmed EU SIP services were operational and stable at resolution; no cause was stated.

Baseten reported a major DeepSeek v4.1 outage on Model APIs from 2026-10-06 04:35 UTC to 2026-10-06 04:48 UTC, lasting 13 min. Dedicated Inference was not affected; the incident was resolved, with no cause or fix specified.

Apollo GraphQL reported a major outage affecting deployment of new graph artifacts builds from 2026-10-06 00:26 UTC to 2026-10-06 00:45 UTC, lasting 19 min. The vendor corrected a cloud configuration issue and confirmed that data was delayed, not lost.

GitHub reported a major degradation affecting organization and enterprise billing, licensing, and settings pages, with slow loads, timeouts, and errors. The incident started at 2026-10-05 23:47 UTC, lasted 1 h 44 min, and was resolved at 2026-10-06 01:32 UTC; GitHub cited a networking failure and reported deploying a mitigation.

GitHub reported a major degradation causing slow loads, timeouts, and errors on organization and enterprise billing, licensing, and settings pages. The incident started at 2026-10-05 23:47 UTC and was resolved at 2026-10-06 01:32 UTC, lasting 1 h 44 min; GitHub cited a networking failure and reported deploying a mitigation.

Expo reported a major degradation starting 2026-10-05 20:38 UTC, with resolution recorded earlier at 2026-10-05 20:11 UTC; duration is unknown. High primary-database CPU load left the website and API at 80-90% availability, affecting builds, submissions, CI/CD jobs and publishing updates. Serving updates to end users was unaffected.

Temporal Cloud reported a critical incident causing increased errors and timeouts across its control plane, Cloud Ops API, and Temporal UI, starting 2026-10-05 20:23 UTC. A fix was implemented by 2026-10-05 20:39 UTC; normal operation was confirmed at resolution on 2026-10-05 20:52 UTC, after 28 min.

Mux reported a major Mux Video - VOD incident affecting Direct Uploads, thumbnails, gifs, subtitles and storyboards; some customers experienced failures creating or uploading to direct upload URLs. It started at 2026-10-05 19:44 UTC and lasted 3 h 3 min, resolving at 2026-10-05 22:47 UTC after a fix was implemented and monitored.

Drata reported a major incident: some downloaded policy PDFs lacked the “Policy version history” page; policy content remained complete and no data was lost. It ran from 2026-10-05 19:28 UTC to 2026-10-10 00:01 UTC (4 days 4 h). Drata restored pages across all regions for Policy Builder and uploaded PDFs; customers who downloaded or shared affected PDFs should download again.

GitHub reported critical Actions and Pages degradation starting 2026-10-05 19:11 UTC, resolved at 2026-10-05 22:49 UTC (3 h 37 min). Runner delays meant 26.5% of GitHub-hosted jobs did not start within five minutes, delaying customer workflows. GitHub applied mitigations, cleared queued jobs, and reported both services operating normally.

GitHub reported critical Actions and Pages degradation starting 2026-10-05 19:11 UTC, resolved at 2026-10-05 22:49 UTC (3 h 37 min). GitHub-hosted runner jobs were delayed or failed; 26.5% did not start within five minutes. GitHub applied mitigations, cleared queued jobs, and reported both services operating normally.

Zapier reported a major outage affecting Facebook and Microsoft SSO: authentication succeeded, but users saw a blank page; a hard refresh or new tab allowed access. It started at 2026-10-05 18:54 UTC and was resolved at 2026-10-05 19:46 UTC, lasting 51 min. Engineering released a fix and confirmed both SSO methods were working.

BigCommerce reported a major Checkout & Payment Processing outage: QuickBooks Payments stores could not transact from 2026-10-05 18:45 UTC to 2026-10-05 22:24 UTC, lasting 3 h 39 min. A fix was deployed; at resolution, BigCommerce said merchants could disconnect and reconnect their QuickBooks.

Pipedream reported a major outage preventing string.com from responding to chats, starting 2026-10-05 17:58 UTC and resolved at 2026-10-05 18:32 UTC after 34 min. The vendor investigated an issue with its Anthropic account and confirmed chats were restored; all pipedream.com services and workflows were expected to be unaffected.

Semgrep reported a major Login/SSO outage causing intermittent semgrep.dev login failures for GitHub and GitLab users, who could see an "unrecoverable error" after clicking Continue. It started at 2026-10-05 16:00 UTC and lasted 14 min, resolving at 2026-10-05 16:14 UTC after a fix was rolled out.

Anthropic reported a major incident with elevated errors for Claude Mythos 5.1 and Claude Fable 5.1 across claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork. It started 2026-10-05 13:05 UTC and resolved at 2026-10-05 13:21 UTC (computed duration: 15 min); the vendor reported impact from 12:40 UTC to 13:10 UTC.

Claude reported major elevated errors for Claude Mythos 5.1 and Claude Fable 5.1 across claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork. The incident started at 2026-10-05 13:05 UTC and resolved at 2026-10-05 13:21 UTC (computed duration: 15 min); the vendor separately stated an impact window of 12:40 UTC to 13:10 UTC.

Gong reported a major Engage disruption affecting access to or use of the To-dos page, starting 2026-10-05 11:18 UTC and resolved at 2026-10-05 13:28 UTC; the reported duration was 2 h 9 min. Gong implemented a fix and monitored system performance across all cells before resolving the incident.

AssemblyAI’s major EU asynchronous transcription degradation delayed Universal-3 Pro and Universal-3.5 Pro requests and caused some failures. It started at 2026-10-05 10:21 UTC and was resolved at 2026-10-05 11:39 UTC (1 h 18 min); processing returned to normal, and failed requests can be safely resubmitted. The US endpoint and real-time services were unaffected.

Bitrise reported a major Builds (CI) incident: users may have been unable to open or use the Website UI’s Start Build dialog, while underlying build triggers were unaffected. It started at 2026-10-05 08:36 UTC and was resolved at 2026-10-05 10:55 UTC, lasting 2 h 18 min. A fix was implemented at 08:46 UTC.

Front reported a major outage affecting outbound sending on a subset of custom SMTP channels, listed as SMTP (non-Gmail / O365). It started at 2026-10-05 07:42 UTC and was resolved at 2026-10-05 09:45 UTC, lasting 2 h 2 min. Front deployed a fix but did not specify the cause.

Codecov’s app and services were down, affecting Codecov Backend and Codecov Frontend, with impact rated critical. The incident started at 2026-10-05 06:53 UTC and was resolved at 2026-10-05 09:15 UTC, lasting 2 h 22 min.

Fly.io reported a critical partial outage in AMS starting 2026-10-03 08:01 UTC, lasting 56 min and resolved at 2026-10-03 08:57 UTC. Offline hosts made some machines unavailable and blocked Managed Postgres v1 and v2 control-plane operations; some MPGv1 clusters later experienced possible degradation. Hosts and all impacted services recovered.

Brex reported a critical partial notifications outage: some notifications, including MFA and 3DS challenges, were not sent between 18:18–18:54 UTC. The incident record started and resolved at 2026-10-02 22:36 UTC (computed duration: 0 min); Brex attributed it to a transient issue and confirmed notifications were sending correctly again.

Heap reported a major Salesforce integration outage starting 2026-10-02 21:49 UTC: data wasn't syncing into Heap, and new connections or reconnections were failing. Heap identified the root cause but did not disclose it; a fix was underway. The incident remained open after 8 minutes at the last update; customers were told not to reconnect until an update.

Box reported a major incident affecting File Requests, now resolved with no current impact. The recorded start is 2026-10-02 03:43 UTC and resolution is 2026-10-01 10:00 UTC; these timestamps conflict, and the computed duration is unknown.

Astronomer reported a critical incident involving tasks stuck queued or failing on several hosted deployments, initially citing worker autoscaler scaling issues. It started at 2026-10-01 22:40 UTC and was resolved at 2026-10-01 23:47 UTC, lasting 1 h 7 min; the final update called it a false alert and said multiple deployments were not affected.

ChatGPT reported a major outage affecting login, signup, and ads from 2026-10-01 18:46 UTC to 2026-10-01 19:39 UTC, lasting 53 min. A mitigation was applied at 19:26 UTC, and all impacted services fully recovered by resolution.

OpenAI reported a major incident affecting login, signup, and ads from 2026-10-01 18:46 UTC to 2026-10-01 19:39 UTC, lasting 53 min. A mitigation was applied at 19:26 UTC, and all impacted services fully recovered.

MongoDB Atlas reported a major global incident affecting Triggers: unordered processing was delayed, and some triggers were not firing or visible in the Atlas UI. The incident started at 2026-10-01 15:41 UTC and was resolved at 2026-10-01 20:54 UTC, lasting 5 h 12 min; trigger processing was operational by 19:59 UTC.

Ably reported a major DDoS incident causing token-request errors across all Ably Realtime regions (503 responses) and intermittent ably.com unavailability. Recorded start: 2026-10-01 15:36 UTC; duration: 26 min, with token errors lasting approximately six minutes. Ably restored token-request service by increasing capacity and added targeted traffic-blocking and rate-limiting rules.

Census reported a major Sync Engine outage in azure-eastus starting 2026-10-01 14:20 UTC, with syncs failing amid spotty Azure Redis connectivity. Redis connectivity was restored and syncs were completing successfully by 2026-10-01 15:14 UTC; the incident was resolved at 2026-10-01 17:36 UTC, lasting 3 h 16 min.

Brevo reported a major SMS degradation causing soft bounces and sending disruptions for some customers, starting 2026-10-01 10:19 UTC and resolved at 2026-10-01 12:21 UTC, lasting 2 h 1 min. Brevo confirmed SMS campaigns and transactional SMS were processing normally again; it did not disclose the cause or specific fix.

Buffer reported a major publishing outage affecting some posts to Mastodon accounts on mastodon.social and mastodon.online from 2026-10-01 10:11 UTC to 2026-10-01 12:37 UTC, lasting 2 h 26 min. The mastodon.social team reported connectivity issues; Buffer confirmed resolution and advised customers to click Retry Now on each failed post.

Contentful reported major issues with advanced caching, specifically Stale While Revalidate (SWR), affecting Content Delivery API and EU data residency - Content Delivery API. The incident started 2026-10-01 09:27 UTC and resolved 2026-10-02 09:43 UTC, lasting 24 h 15 min. A fix resolved the issue for remaining customers after most had already recovered.