Everything SaaS vendor changes, page 12

WorkOS reported a major AuthKit and Core Services - AuthKit outage affecting static asset delivery to end users with strict network allowlists. It started at 2026-09-02 16:39 UTC and was resolved at 2026-09-02 19:06 UTC, lasting 2 h 26 min. WorkOS mitigated the issue and confirmed delivery rates had recovered.

PlanetScale reported a major incident affecting postgres database management pages and API endpoints, which returned 500 errors. The incident started at 2026-09-02 16:17 UTC and was resolved at 2026-09-02 16:44 UTC, lasting 27 min; PlanetScale deployed a fix.

Some Discord servers were offline or degraded during a major-impact incident starting 2026-09-02 16:12 UTC and resolved at 2026-09-02 18:26 UTC, lasting 2 h 14 min. Discord reported recovery at 18:18 UTC but was still investigating the root cause; no specific fix was stated.

Cursor reported a major service degradation in which Automations, Cloud Agents, and Review Agents failed to start. The incident began at 2026-09-02 14:50 UTC and was resolved at 2026-09-02 16:10 UTC, lasting 1 h 20 min; no cause or fix was stated.

Gorgias reported a major degradation delaying Instagram direct message ingestion from 2026-09-02 14:49 UTC to 2026-09-02 19:11 UTC, lasting 4 h 22 min. Messages were not lost but arrived later than usual. A fix was implemented at 18:03 UTC, and the incident was resolved.

Buildkite reported a major Hosted Agents job-dispatch degradation affecting Linux (AMD64), Linux (ARM64), and MacOS from 2026-09-02 14:45 UTC to 2026-09-02 15:51 UTC, lasting 1 h 5 min. Self-hosted agents were unaffected; Buildkite worked through the delayed-job backlog and confirmed dispatch delays were resolved.

Xero’s UK Making Tax Digital (MTD) and VAT services had a critical outage starting 2026-09-02 14:05 UTC, lasting 3 h 48 min. HMRC investigated; the incident was marked resolved at 2026-09-02 17:53 UTC, although the final update also said services were “not operating as normal.”

Chargebee reported major API degradation affecting some US-region users, with intermittent failures between 12:54 UTC and 12:57 UTC. The incident record started at 2026-09-02 13:28 UTC and was resolved at 2026-09-02 13:35 UTC, lasting 7 min; services had recovered by the initial update and were monitored for stability.

Greenhouse reported a major partial disruption affecting job creation and causing multiple confirmation emails to be sent to candidates on Greenhouse Recruiting - Silo 201 and Silo 201. It started at 2026-09-02 08:06 UTC and lasted 26 min, resolving at 2026-09-02 08:32 UTC after a fix was implemented; all services returned to normal.

Optimizely reported a major SSL trust outage affecting DXP environments in Australia East and East US, preventing affected customers from logging into the CMS management interface or creating/editing content. It lasted 7 h 18 min, from 2026-09-02 08:05 UTC to 2026-09-02 15:23 UTC; Optimizely implemented a fix and confirmed normal service.

Fly.io reported a major API background job queue failure starting 2026-09-02 07:21 UTC: creating apps, assigning IP addresses, and creating/renewing certificates could fail. A fix was implemented by 07:31 UTC; the incident was resolved at 07:44 UTC, lasting 22 min.

Users could not access billing pages in their Buffer accounts during a major-impact incident starting 2026-09-02 06:30 UTC. Buffer deployed a fix at 07:28 UTC, restoring page loading, and resolved the incident at 2026-09-02 07:57 UTC; the incident lasted 1 h 27 min.

Optimizely reported a critical CMP and DAM outage affecting all users, starting 2026-09-02 05:00 UTC and resolved at 2026-09-02 07:49 UTC, lasting 2 h 48 min. A fix was implemented by 06:44 UTC, when both products were reported accessible; sustained stability was confirmed at closure. The root cause was identified but not disclosed.

QuickBooks Online reported a major incident affecting some users’ logins and causing errors within application features across APAC, Canada, EMEA and the United States. The recorded start was 2026-09-02 04:16 UTC; it lasted 3 min and was resolved at 2026-09-02 04:19 UTC after a fix, with recovery confirmed across all regions.

Elastic Cloud reported a major incident with elevated error rates for Anthropic Claude Haiku 4.5, OpenAI GPT-5.6, and Google Gemini 2.5 Flash on Elastic Inference Service in EU regions, citing 21:50–23:42 UTC. It was resolved; recorded start and resolution were both 2026-09-02 00:04 UTC (computed duration: 0 min).

Vercel reported a major incident causing some deployments using IAD1 Function regions or Routing Middleware to fail. It started at 2026-09-01 19:59 UTC and lasted 59 min, resolving at 2026-09-01 20:58 UTC after a fix was deployed and Builds recovered.

v0 reported a major incident causing some deployments using IAD1 Function regions or Routing Middleware to fail. It lasted 59 min, from 2026-09-01 19:59 UTC to 2026-09-01 20:58 UTC; a fix was deployed and Builds recovered.

Brex’s Trust Portal (trust-portal.brex.com) was unavailable in a major-impact incident starting 2026-09-01 17:48 UTC. Brex reported the site restored at 09-01 19:20 UTC and marked the incident resolved at 2026-09-02 01:56 UTC; the recorded incident duration was 8 h 7 min.

Anaconda reported a critical network interruption affecting the anaconda.org front-end and conda.anaconda.org repository services, with elevated 503 errors on anaconda.org. It started at 2026-09-01 17:46 UTC and was resolved at 2026-09-01 19:05 UTC, lasting 1 h 18 min. A fix was rolled out at 18:53 UTC; no cause was stated.

Gorgias reported a major Voice degradation starting 2026-09-01 17:05 UTC due to a Twilio incident, causing failed or delayed calls and inaccurate call test results for some customers. SMS, email, chat and helpdesk were unaffected. Resolved at 2026-09-01 18:00 UTC after 54 min, Voice functionality and call test results returned to normal.

Matillion reported a major Hub login outage starting 2026-09-01 17:03 UTC, resolved at 2026-09-01 17:55 UTC after 52 min; the support portal was also affected. New tokens could not be issued after hitting the global token limit; Matillion attributed widespread permission-check failures to an out-of-memory event triggered by a Permission Service deployment.

Apollo reported a major outage from 2026-09-01 15:41 UTC to 2026-09-01 20:18 UTC (4 h 37 min), attributed to GCP issues in part of us-central1-b. New schemas could not be published; AWS Uplink remained available, allowing default multi-cloud GraphOS Routers and Gateways to start and fetch configuration. All Apollo products recovered.

Sourcegraph reported a major incident affecting account sign-in and authentication, starting 2026-09-01 15:41 UTC and resolved 2026-09-02 09:39 UTC, lasting 17 h 58 min. Sourcegraph attributed the errors to a Google Cloud networking incident; sign-in had recovered by 2026-09-01 16:48 UTC, with monitoring continuing afterward.

CockroachDB Basic/Standard experienced major latency, delays, and connection issues affecting us-central-1, asia-east-1 (later listed as us-central1, asia-east1), europe-west4-b, and us-central1-b from 2026-09-01 15:36 UTC to 2026-09-01 19:45 UTC (4 h 8 min). CockroachDB attributed the disruption to Google Cloud networking outages; network-level mitigation restored infrastructure, and all services were confirmed restored.

A critical outage prevented GCP-hosted organizations in us-central1 from reliably accessing Sigma. The recorded incident ran from 2026-09-01 15:34 UTC to 2026-09-01 16:55 UTC (1 h 20 min), though Sigma reported an approximate start of 2:46 PM UTC. The postmortem attributed the disruption to a Google Cloud networking incident; services returned to normal.

Dialpad reported a major partial service disruption affecting Telephony Infrastructure: Inbound Calls, starting 2026-09-01 15:25 UTC and resolved at 2026-09-01 20:02 UTC, lasting 4 h 36 min. Dialpad stated that a fix was implemented but did not specify the cause or fix details.

Gorgias reported a major cloud service provider network incident potentially affecting a subset of customers, with Live Chat, REST API and Google Cloud Networking listed as affected components. It started at 2026-09-01 15:19 UTC and was resolved at 2026-09-01 18:59 UTC, lasting 3 h 39 min.

Fullstory reported a critical NA1 outage affecting data capture (web and native mobile), the Fullstory web application, API and other services. It ran from 2026-09-01 15:19 UTC to 2026-09-01 20:36 UTC (5 h 17 min). Fullstory linked the issue to Google Cloud Platform; services were restored, with backlogged data still processing.

A major outage impacted Elastic Cloud Hosted and Serverless projects in GCP us-central1 and the Docker Registry service. It started at 2026-09-01 15:18 UTC and was resolved at 2026-09-01 20:05 UTC, lasting 4 h 47 min; Elastic attributed the disruption to an upstream CSP issue.

Drata reported a critical outage affecting Trust Center Pages, Trust Center Admin Page, AIQA, and Compliance Monitoring (AI Summary), caused by upstream provider network service degradation. It started at 2026-09-01 15:14 UTC and was resolved at 2026-09-01 19:29 UTC, lasting 4 h 14 min; all impacted services were operational at resolution.

Pinecone reported a major incident causing 5xx errors on some control plane operations, affecting Console, Index management, Assistant management, and APIs at api.pinecone.io. It started at 2026-09-01 15:04 UTC and was resolved at 2026-09-01 19:40 UTC, lasting 4 h 36 min. Pinecone said it was likely related to ongoing GCP issues.

RevenueCat reported a major Apple Receipt Server degradation from 2026-09-01 13:17 UTC to 2026-09-01 13:43 UTC (26 min), with intermittent HTTP 522 responses from its receipts endpoint. Mitigations meant no purchases were being blocked; Apple reported resolution, error rates normalized, and RevenueCat said it was ensuring affected purchases were reprocessed.

Tailscale reported a major Funnel incident involving connection errors for some users, starting 2026-09-01 12:47 UTC and resolved at 2026-09-01 16:19 UTC, lasting 3 h 31 min. A fix was deployed at 09-01 14:11 UTC; no cause was stated.

Snowflake reported a major incident in which customers in the listed AWS, Azure and GCP regions could be unable to sign in to Snowflake Cowork. It started at 2026-09-01 09:58 UTC and was resolved at 2026-09-01 13:50 UTC. All other Snowflake features were unaffected; Snowflake identified the source but did not specify the cause or fix.

A critical Supabase Dashboard outage prevented login, logged existing users out, and made Dashboard actions unavailable from 2026-09-01 08:45 UTC to 2026-09-01 10:34 UTC (1 h 49 min). Supabase reverted a recent change that affected login; the incident was resolved, and projects and non-Dashboard traffic remained unaffected.

Elastic Cloud Hosted reported major degradation from 2026-09-01 08:16 UTC to 2026-09-30 20:44 UTC (29 days 12 h). In Elasticsearch 9.5.0, 9.5.1 and 9.5.2, bulk indexing could cause replica divergence, high disk usage and long-running recoveries. Elastic fixed the bug in 9.5.3 and advised affected customers to upgrade and follow workaround steps.

Sentry reported a major outage affecting API, Dashboard, and Integration Pipeline, with requests timing out or returning 504s. It started at 2026-09-01 08:01 UTC and was resolved at 2026-09-01 11:21 UTC, lasting 3 h 20 min. Sentry identified the issue and rolled out a configuration change.

Discord reported a major outage that left some users unable to connect to some servers and affected voice calls and activities. It started at 2026-08-31 22:54 UTC and was resolved at 2026-09-01 00:49 UTC, lasting 1 h 55 min; Discord reported remediation steps but gave no specific cause or fix.

Rippling reported a major outage preventing some saved payroll reports from loading when certain payroll fields were included. It started at 2026-08-31 22:37 UTC and lasted 5 h 43 min, resolving at 2026-09-01 04:20 UTC; United States access was restored before European Union access.

Jira reported a major outage fetching mail from Microsoft accounts, disrupting email-based creation and updates of work items and potentially returning 500 errors. It started at 2026-08-31 18:28 UTC and was resolved at 2026-09-01 05:18 UTC, lasting 10 h 49 min; Atlassian reported full recovery across impacted services.

Ashby reported a major degradation affecting All-in-One document uploads and signing through Dropbox Sign, starting 2026-08-31 17:44 UTC and resolved at 2026-08-31 18:11 UTC (27 min). Ashby attributed the disruption to an upstream Dropbox Sign incident and said the provider resolved the issue.

Snowflake reported a critical outage in AWS - US East (N. Virginia) affecting sign-in, queries and data operations from 2026-08-31 17:20 UTC to 2026-08-31 19:44 UTC (2 h 24 min). It reverted a problematic change and fixed residual Snowsight access and Snowpipe Streaming impact; an RCA is available on Snowflake Community.

Render reported a major degradation in Singapore affecting deploys and inbound traffic, with unexpected web service restarts or intermittent availability; Free service spin-ups from idle were temporarily disabled. The incident started at 2026-08-31 15:47 UTC and was resolved at 2026-08-31 18:09 UTC, lasting 2 h 21 min. Render implemented a fix but did not specify its details.

Asana reported a major full outage for some users (25% outage), affecting API, App and Mobile, including US components, from 2026-08-31 15:14 UTC to 2026-08-31 17:18 UTC (2 h 4 min). The postmortem attributed it to infrastructure changes and peak traffic exceeding cache scaling limits; user-facing symptoms recovered after configuration changes and a fix.

ChatGPT Work had a major incident with elevated errors and latency, preventing users across multiple subscription plans from starting or continuing tasks; Plus users were particularly impacted, with Work mode unavailable. It started at 2026-08-31 15:04 UTC and resolved at 2026-08-31 20:28 UTC, lasting 5 h 23 min. A mitigation was applied, and services fully recovered.

ChatGPT Work had a major incident starting 2026-08-31 15:04 UTC, lasting 5 h 23 min and resolving at 2026-08-31 20:28 UTC. Elevated errors and latency prevented users across multiple subscription plans from starting or continuing tasks; Plus users were particularly impacted, with Work mode unavailable. OpenAI applied a mitigation and reported full recovery.

Miro reported a major incident causing intermittent registration and login errors for a small percentage of users, starting 2026-08-31 14:31 UTC and resolved at 2026-08-31 15:57 UTC, lasting 1 h 25 min. Miro implemented a fix and confirmed full recovery; users encountering registration errors were advised to refresh and retry.