Major incidents SaaS vendor changes, page 4

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.

Mobile device pairing with Pendo Designer failed, affecting on-device guide testing and Mobile Debugger across AU, EU, JPN, US1 and US environments. Pendo rated the incident major; it started at 2026-10-01 06:29 UTC and was resolved at 2026-10-01 08:16 UTC, lasting 1 h 47 min. No cause or fix was stated.

Aircall reported a major outage affecting Workspace Desktop and Web: users could not log in or make and receive calls. It started at 2026-10-01 05:36 UTC and was resolved at 2026-10-01 07:01 UTC, lasting 1 h 25 min. Aircall said a spike in errors between 05:10 and 05:23 UTC appeared to cause the issue.

Wix reported a major outage affecting some users of checkout, payments, shipping, storefront, store management, Wix Editor and Wix Studio. It started at 2026-10-01 05:17 UTC and was resolved at 2026-10-01 05:42 UTC, lasting 25 min; Wix reported normal performance across all services at 05:23 UTC.

Major job processing and scheduling degradation affected Confluence Automations and other Atlassian products across all commercial cloud regions, delaying or missing background tasks; interactive use was unaffected. The incident started at 2026-10-01 02:55 UTC and lasted 4 h 55 min. Atlassian implemented a fix and confirmed recovery, including missing SLA components and delayed notifications.

Major job-processing degradation affected Jira, Confluence, Bitbucket Cloud, Forge apps and Jira Service Management across all commercial cloud regions, delaying tasks and notifications and leaving SLA components missing; interactive use was unaffected. Logged from 2026-10-01 02:55 UTC to 2026-10-01 07:51 UTC (4 h 55 min), it was resolved after a fix.

Major job-processing and scheduling degradation affected Bitbucket Cloud Pipelines and other Atlassian products across all commercial cloud regions, delaying or missing background tasks; interactive use was unaffected. The recorded incident started 2026-10-01 02:55 UTC and lasted 4 h 55 min. Atlassian implemented a fix and confirmed recovery.

Box reported a major-impact incident causing missing or outdated data in Enterprise Reports, including User Engagement Reports, and Admin Console collaboration insights. It started at 2026-09-30 18:08 UTC and was resolved at 2026-10-05 14:09 UTC, lasting 4 days 20 h. Box confirmed the Report Service was restored to full functionality.

Gorgias reported a major latency incident affecting AI Agent and Automate - AI Agent, slowing AI Agent responses due to high latency at external LLM providers. It started at 2026-09-30 17:21 UTC and was marked resolved at 2026-09-30 20:59 UTC, lasting 3 h 38 min; no fix was stated.

Brex reported a critical spike in Admin home page load errors affecting the Home Page, starting at 2026-09-30 16:38 UTC and resolved at 2026-09-30 17:12 UTC; the computed duration was 33 min. Brex said a fix was in place at 09-30 16:55 UTC and monitored for further issues before resolution.

Asana reported a major partial API outage affecting API, Mobile, US - API, and US - Mobile, starting 2026-09-30 14:31 UTC and resolved at 2026-09-30 15:21 UTC after 50 min. Asana reported system recovery and monitoring at 15:09 UTC; no cause or specific fix was stated.

Buildkite reported a major outage preventing macOS hosted agent jobs from starting because of a misconfigured agent image update. Recorded start: 2026-09-30 06:30 UTC; recorded resolution: 2026-09-28 01:30 UTC; duration unknown. The vendor reported a fix and normal operation for new jobs; affected jobs still in Scheduled must be canceled and retried.

RudderStack reported a critical Data Ingestion issue in the EU region from 2026-09-29 21:57 UTC to 2026-09-29 22:58 UTC, lasting 1 h 1 min. A fix was implemented at 09-29 22:39 UTC, and the incident was resolved; no cause was stated.

Baseten reported a major incident affecting Dedicated Inference, with elevated 500s in a single us-central region starting 2026-09-29 19:44 UTC. A fix was implemented at 2026-09-29 19:52 UTC, and the incident was resolved at 2026-09-29 19:57 UTC after 13 min.

Cursor reported a major xAI model degradation affecting CLI, Cloud Agents, Grok Bot, and IDE: users could see errors, slow responses, rate limiting, and failed Agent requests or Cloud Agent tasks. It started at 2026-09-29 19:43 UTC and was resolved at 2026-09-29 20:18 UTC; the reported duration was 34 min.

Rippling reported a critical outage that prevented its app from loading, starting 2026-09-29 19:20 UTC and resolved at 2026-09-30 03:55 UTC (8 h 35 min). The vendor observed authentication database overload; access initially recovered with degraded performance, and the app was fully operational by 09-29 19:51 UTC while root-cause investigation continued.

Descript reported a major outage in its transcription pipeline: transcription jobs could become stuck or fail. The incident started at 2026-09-29 18:12 UTC and was resolved at 2026-09-29 20:30 UTC, lasting 2 h 17 min; Descript reported restoring functionality but did not specify the underlying cause.

Close reported a major Application UI outage in which parts of the application failed to load. The incident started at 2026-09-29 17:48 UTC and was resolved at 2026-09-29 18:15 UTC, lasting 26 min. Close said the issue was identified and reverted.

ElevenLabs reported a major outage affecting Agents and STT, with increased latency, conversation failures and STT 429 errors; Creative Platform impact was possible but unclear. It began at 2026-09-29 16:00 UTC and lasted 4 h 23 min, resolving at 2026-09-29 20:23 UTC after a fix for the likely root cause; all services were reported operational and stable.

Contentful reported a major incident affecting some customers: CORS preflight failures for browser requests to cross-space references on CDA, including EU data residency. It started at 2026-09-29 14:39 UTC and was resolved at 2026-09-29 15:44 UTC, lasting 1 h 5 min; Contentful identified the cause but did not disclose it or the fix.

Anthropic reported major errors affecting claude.ai, Claude Code, Claude Cowork and the Claude API, blocking sign-ins, new sessions, purchases and uploads; some messages may not have been saved. Impact occurred from 14:00 UTC to 14:59 UTC; the incident started 2026-09-29 14:21 UTC and resolved at 2026-09-29 16:27 UTC (recorded duration: 2 h 5 min).

A major incident caused errors across claude.ai, Claude Code, Claude Cowork and the Claude API, disrupting sign-ins and other workflows; some messages may not have been saved. Reported impact was 14:00–14:59 UTC on 2026-09-29. The incident record started at 2026-09-29 14:21 UTC and resolved at 2026-09-29 16:27 UTC (computed duration: 2 h 5 min).

Box reported a critical outage affecting All Files Page, Box Notes, API calls, logins and downloads, starting 2026-09-29 14:15 UTC and resolved at 2026-09-29 15:30 UTC (computed duration: 1 h 14 min). Box said its systems automatically detected and corrected the underlying issue, with no current impact.

Chargebee reported major degradation affecting API (US), with failed requests for some merchants between 11:58 UTC and 12:08 UTC. The incident started at 2026-09-29 12:35 UTC and resolved at 2026-09-29 14:35 UTC (2 h 0 min); Chargebee said services had recovered and were monitored for stability.

Redpanda reported a major partial sign-in outage at cloud.redpanda.com, with failed logins detected starting at 2125 UTC. The incident ran from 2026-09-28 22:14 UTC to 2026-09-29 01:16 UTC (3 h 1 min); Redpanda identified upstream-provider rate limiting and closed it reporting no observed impact and all systems normal.

GitHub reported a critical Copilot Code Review degradation starting 2026-09-28 21:16 UTC, resolved at 2026-09-28 22:08 UTC (51 min). Approximately 70% of requested reviews did not complete across all environments; affected users needed to re-request reviews. GitHub attributed the issue to a dependent-service change and reported a revert underway before recovery.

GitHub Copilot reported a critical Code Review outage starting 2026-09-28 21:16 UTC, resolved at 2026-09-28 22:08 UTC (51 min). Approximately 70% of requested reviews failed across all environments; failed reviews were not automatically retried, so users needed to re-request them from their pull requests. GitHub attributed the issue to a dependent-service change and reported a rollback underway.

Convex’s AI Gateway rejected requests during a critical outage starting 2026-09-28 21:09 UTC and resolved at 2026-09-28 22:13 UTC, lasting 1 h 3 min. Convex attributed the failures to an upstream provider, implemented a fix, and confirmed service was restored.

Xero reported a critical outage preventing US customers from accessing US Payroll (Powered by Gusto), starting 2026-09-28 20:32 UTC and resolved at 2026-09-28 21:23 UTC, lasting 51 min. Xero attributed the outage to an issue on Gusto's side; Gusto implemented a fix and resolved it.

Some Drift customers could not see conversations and playbooks after logging in during a major outage starting 2026-09-28 19:06 UTC. Salesloft reported a fix and monitoring at 09-28 22:00 UTC, then confirmed resolution at 2026-09-29 14:39 UTC; the incident lasted 19 h 33 min.

Grafana Cloud reported a critical platform access outage affecting AWS US East - prod-us-east-3 and Grafana - AWS US East - prod-us-east-3 from 2026-09-28 17:32 UTC to 2026-09-28 19:21 UTC, lasting 1 h 49 min. Grafana identified the issue and applied a mitigation before resolving it; no cause was stated.