Everything SaaS vendor changes, page 3

ChatGPT reported a major Android outage where some content displayed “This content is unavailable in this version of the app,” starting 2026-10-09 21:00 UTC and lasting 3 h 26 min. A fix rolled out gradually in the latest Android version, with web access offered as a workaround; all impacted services recovered by 2026-10-10 00:26 UTC.

A major ChatGPT Android outage caused some content to display “This content is unavailable in this version of the app” from 2026-10-09 21:00 UTC to 2026-10-10 00:26 UTC, lasting 3 h 26 min. OpenAI rolled out a fix in the latest Android version and suggested using the web meanwhile; all impacted services fully recovered.

RunPod reported a critical network storage outage in US-CA-2 starting at 2026-10-09 16:31 UTC. It lasted 1 h 31 min and was resolved at 2026-10-09 18:02 UTC, when RunPod confirmed network storage was operating normally.

MongoDB Atlas reported a major Atlas Search incident causing mongot crashes and potential search and vector search outages for a subset of users. It started at 2026-10-09 16:29 UTC and was resolved at 2026-10-09 18:17 UTC, lasting 1 h 47 min. A fix was deployed at 10-09 17:09 UTC.

CircleCI reported a major degradation starting 2026-10-09 11:33 UTC, resolved 2026-10-10 02:08 UTC after 14 h 35 min. Customers experienced pipeline, workflow and job delays and failures, delayed UI/API data, and disrupted webhooks and Slack/email notifications; retriggering could create duplicate pipelines. The vendor identified a delay in its data infrastructure.

Fly.io reported a critical outage affecting Sprite creates in all regions outside Europe, starting 2026-10-08 21:23 UTC and resolved at 2026-10-08 21:54 UTC (31 min). Fly.io applied a fix for a potential issue; Sprite pools recovered and creates resumed succeeding.

Sanity reported a major degradation starting 2026-10-08 18:27 UTC, lasting 13 h 29 min and resolved at 2026-10-09 07:57 UTC. Elevated listener latency affected Studio performance for some customers; Dataset Embeddings could be stale, and Functions triggering could be delayed or time out. Sanity reported a fix fully implemented at 10-08 20:08 UTC while embedding processing caught up.

A major outage caused delayed or unavailable operations for some Elastic Cloud Serverless projects in GCP us-central1 from 2026-10-08 16:42 UTC to 2026-10-09 00:54 UTC, lasting 8 h 11 min. Elastic identified an upstream cloud storage issue; the provider applied mitigations, and project operations returned to normal.

Some Canva users had issues creating designs from templates on the home page in a major-impact incident starting at 2026-10-08 16:42 UTC. Canva reported a fix and resolution at 2026-10-08 17:20 UTC; the incident lasted 37 min.

ElevenLabs reported a major Dubbing degradation with increased latency and request failures, starting at 2026-10-08 15:38 UTC and resolved at 2026-10-08 22:10 UTC, lasting 6 h 32 min. Errors recurred during monitoring; ElevenLabs worked with an upstream provider on mitigation and reported a stable error-rate baseline since 17:55 UTC.

Klaviyo reported a critical incident preventing some customers from logging in or loading app pages, starting 2026-10-08 15:00 UTC and resolved at 2026-10-08 16:13 UTC (reported duration: 1 h 12 min). A fix restored access; campaign and flow sending were not impacted, and customers logged out during the incident may need to log in again.

ElevenLabs reported a major outage causing call failures in Agent conversations using SIP; non-SIP conversations were unaffected. The incident started at 2026-10-08 14:21 UTC and was resolved at 2026-10-08 15:43 UTC, lasting 1 h 22 min. ElevenLabs reported no continuing failures as of 15:15 UTC and promised a Root Cause Analysis after investigation.

ActiveCampaign reported a major WhatsApp degradation starting 2026-10-08 14:03 UTC: incoming responses were delayed, while message sending was unaffected. The vendor reported the issue resolved and responses catching up at 14:29 UTC; all delayed messages had caught up by 2026-10-08 17:26 UTC, ending the incident after 3 h 22 min.

Drata reported a major degradation delaying scheduled compliance checks and ticket synchronization for some US-region customers, including expiration checks, compliance and vendor review reminders, and linked ticket status updates. It started 2026-10-08 13:40 UTC and was resolved 2026-10-09 23:30 UTC, lasting 33 h 49 min. The web application and API remained available; no data loss was reported.

JFrog reported a major Xray service disruption in Azure US East affecting approximately 119 customers, starting 2026-10-08 11:13 UTC and resolved 2026-10-08 13:13 UTC (2 h 0 min). Unexpected issues during emergency database maintenance caused the disruption; JFrog completed database recovery and fully restored services.

Confluent Cloud users in Azure’s Germany West Central region could face elevated error rates in a major-impact incident starting 2026-10-08 11:00 UTC and lasting 55 min. A fix was implemented by 2026-10-08 11:38 UTC, and the incident was resolved at 2026-10-08 11:56 UTC.

Sanity reported critical elevated listener latency and error rates affecting Studio loading, with slower performance and lag for some customers. The recorded incident ran from 2026-10-08 09:55 UTC to 2026-10-08 14:28 UTC (4 h 33 min), though Sanity noted issues began around 9:10 UTC. A fix was fully implemented and the incident resolved.

Box reported a critical outage affecting the All Files page, API, uploads, downloads, Box Sign and Notes, starting 2026-10-08 09:27 UTC and resolved at 2026-10-08 09:33 UTC (computed duration: 5 min). Box confirmed services were restored to full functionality; no cause was stated.

Fly.io reported a major outage in LHR (London, UK): regional anycast and static egress IPs were nonfunctional, with anycast traffic rerouted to nearby regions. The incident started at 2026-10-08 05:40 UTC and was resolved at 2026-10-08 06:00 UTC, lasting 19 min. Fly.io identified BGP announcement issues and restored BGP before resolution.

Box’s major-impact incident caused missing or outdated data in Admin Console event-based reports and Insights, Enterprise Events API results, and Box AI unit usage. It ran from 2026-10-08 01:48 UTC to 2026-10-08 03:54 UTC (2 h 5 min); Box processed delayed enterprise event data and restored full functionality.

Newly created Pinecone serverless indexes on GCP in us-central1 failed to initialize, affecting Index Management. The vendor rated the incident major; it began at 2026-10-07 20:40 UTC and was resolved at 2026-10-07 21:49 UTC, lasting 1 h 9 min. No cause or fix was stated.

Axiom reported major EU Monitor alerting degradation starting 2026-10-07 17:28 UTC, with an execution backlog delaying monitor evaluation. A fix was deployed, and the backlog fully drained with processing latency back to normal by 2026-10-07 18:36 UTC; the reported duration was 1 h 7 min.

GitHub reported a critical incident affecting Actions, Git Operations, Issues and Pull Requests, opened at 2026-10-07 17:17 UTC and resolved at 2026-10-07 18:04 UTC (47 min). Actual write-operation disruption occurred from 16:52 UTC to 17:01 UTC, recurring from an earlier outage with the same root cause; mitigations were applied.

GitHub reported a critical degradation affecting Actions, Git Operations, Issues and Pull Requests, with a recurring write-operation outage from 16:52 to 17:01 UTC. The incident opened at 2026-10-07 17:17 UTC and resolved at 2026-10-07 18:04 UTC, lasting 47 min. GitHub applied mitigations and said both outages shared the same root cause, without specifying it here.

GitGuardian reported a major degradation from 2026-10-07 16:39 UTC to 2026-10-08 07:07 UTC, lasting 14 h 27 min. Check-runs slowed or timed out, and real-time scanning delays meant secrets could appear in dashboards up to 2 hours late. Check-run delays cleared while the real-time backlog was processed; normal operations were restored at resolution.

GitHub reported critical write-operation failures affecting Git Operations, Pull Requests, Issues, Actions, API, webhooks and authentication. Incident metadata lists start and resolution at 2026-10-07 16:25 UTC (computed duration: 0 min), while the vendor described two outage windows totaling about 19 minutes. GitHub reported recovery and an identified root cause, without specifying the cause.

GitHub reported a critical outage affecting write operations across Git Operations, Pull Requests, Issues, Actions, the API, webhooks and authentication. The record starts and resolves at 2026-10-07 16:25 UTC (computed duration: 0 min), although GitHub described two outages totaling about 19 minutes. GitHub said the root cause was identified and preventive mitigations were being applied.

Lovable reported a major outage affecting message sending in the editor and new project creation from 2026-10-07 14:05 UTC to 2026-10-07 15:56 UTC, lasting 1 h 50 min. A provider capacity problem caused some new projects to fail to start; Lovable said it was fixed and advised affected users to try again.

Anthropic reported a major incident affecting usage data on platform.claude.com Usage and Rate limits pages and the Admin API usage report, starting 2026-10-07 13:25 UTC and resolved 2026-10-13 18:00 UTC (6 days 4 h). Mitigations reduced errors, but recent usage could remain delayed while a full fix was pending; core functionality and API requests were unaffected.

Claude reported a major incident affecting usage data on the Console Usage and Rate limits pages and Admin API usage report, starting 2026-10-07 13:25 UTC and resolved 2026-10-13 18:00 UTC (6 days 4 h). Mitigations restored reporting, though recent usage could be delayed by about 30 minutes; core functionality and API requests were unaffected.

Brevo reported a critical Ecommerce orders incident that disrupted some customers from 2026-10-07 12:21 UTC to 2026-10-07 12:32 UTC, lasting 11 min. Impact was mitigated by 12:27 UTC, and all affected services were functioning normally at resolution; no cause or specific fix was stated.

Gorgias reported a major incident: Aircall V2 was not creating tickets, affecting customers using the integration. It started at 2026-10-07 08:57 UTC and was resolved at 2026-10-08 12:27 UTC, lasting 27 h 29 min. Aircall, which manages the integration, applied a fix; Gorgias monitored traffic before confirming resolution.

A major outage prevented creation of new ChatGPT Work threads in desktop app version 26.1002.51308, starting 2026-10-07 05:31 UTC and resolving 2026-10-07 11:53 UTC after 6 h 21 min. Fixed versions were released for Linux, macOS and Windows; affected users should update to the latest version.

A major outage prevented creating new ChatGPT Work threads in desktop app version 26.1002.51308, starting 2026-10-07 05:31 UTC and lasting 6 h 21 min. OpenAI resolved it at 2026-10-07 11:53 UTC with updated apps for Linux, macOS and Windows; affected users should update to the latest version.

Cloudflare reported major network performance issues in Columbus, OH (CMH), starting 2026-10-07 02:48 UTC and resolved at 2026-10-07 11:51 UTC, lasting 9 h 2 min. A fix was implemented and monitoring began at 05:11 UTC; no cause was stated.

Claude Console’s Usage page and Admin API usage report returned errors; Messages API requests were unaffected. The major incident started at 2026-10-07 01:20 UTC and was resolved at 2026-10-07 02:33 UTC (1 h 13 min). Claude reported the actual error window as 00:00 UTC on October 7 to 01:40 UTC on October 7.

Anthropic reported major errors loading platform.claude.com Usage page and Admin API usage reports; Messages API requests were unaffected. Tracked from 2026-10-07 01:20 UTC until resolution at 2026-10-07 02:33 UTC (1 h 13 min), the incident’s resolution update specified errors from 00:00 UTC on October 7 to 01:40 UTC on October 7.

Cursor reported a major service degradation affecting Cloud Agents, with Grok Bot also listed as an affected component. It started at 2026-10-06 22:48 UTC and was resolved at 2026-10-06 23:04 UTC, lasting 16 min; no cause or fix was stated.

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.