Everything SaaS vendor changes, page 6

The Astro Cloud UI Deployments view was unavailable in a major-impact outage starting 2026-09-24 14:52 UTC, lasting 41 min and resolved at 2026-09-24 15:34 UTC; task execution was unaffected. Astronomer rolled back an identified breaking change and advised customers still experiencing issues to refresh the page, then open a support ticket if needed.

Fly.io reported a major incident affecting Private Networking (6PN), starting at 2026-09-24 14:51 UTC and resolved at 2026-09-24 15:37 UTC, lasting 46 min. A fix was implemented by 2026-09-24 15:01 UTC, with private networking error rates returning to normal.

SurveyMonkey’s Audience Preview Page was not responding in a major incident that started at 2026-09-24 12:16 UTC and was resolved at 2026-09-24 15:32 UTC, lasting 3 h 16 min. The vendor reported that Engineering was investigating, but stated no cause or specific fix.

A critical Supabase Dashboard incident caused permission errors during administrative actions, preventing some users from managing projects. It started at 2026-09-24 10:37 UTC and was resolved at 2026-09-24 11:49 UTC, lasting 1 h 12 min. Supabase applied a fix by 09-24 11:08 UTC and reported administrative operations completing as expected.

Baseten reported a major Dedicated Inference outage with elevated inference 500s affecting a subset of models in 1 US-East cluster. It started at 2026-09-24 07:23 UTC and was resolved at 2026-09-24 08:06 UTC, lasting 42 min; a fix was implemented at 07:48 UTC.

Discord reported a major Android degradation involving mismatched age group statuses across devices: “unconfirmed” on an older mobile app but “adult” on web/desktop. It started at 2026-09-24 02:08 UTC and was resolved at 2026-09-24 03:32 UTC, lasting 1 h 23 min. Discord implemented a fix and instructed users to close and refresh the app.

BigCommerce reported a major Storefront incident in which products incorrectly appeared as "out of stock" on category pages, potentially misleading shoppers about availability. It started at 2026-09-23 20:16 UTC and was resolved at 2026-09-23 23:14 UTC, lasting 2 h 57 min; no cause or fix was stated.

FullStory reported a major incident affecting asset loading and session playback in the EU1 Data Center, recorded as starting and resolving at 2026-09-23 19:00 UTC (computed duration: 0 min). The vendor attributed broken playback to a captured-asset URL resolution change and said a rollback at 9:45am UTC fixed it.

Fly.io reported a major partial Sprites outage with intermittent API failures near SJC, later extending to other regions and affecting creating, connecting to, or managing Sprites. It ran from 2026-09-23 18:44 UTC to 2026-09-24 02:12 UTC (7 h 28 min) and was resolved after mitigations and potential fixes were deployed.

HCP Terraform returned 404s and experienced degraded performance in a critical incident starting 2026-09-23 17:43 UTC. A fix was implemented at 09-23 18:06 UTC, and the incident was resolved at 2026-09-23 20:02 UTC after 2 h 18 min; the vendor reported systems operating normally.

HCP Terraform returned 404s and experienced degraded performance in a critical-impact outage starting 2026-09-23 17:43 UTC, lasting 2 h 18 min and resolved at 2026-09-23 20:02 UTC. Engineering implemented a fix at 09-23 18:06 UTC; HashiCorp reported normal operation at resolution but did not disclose the cause.

Fly.io reported a major incident involving elevated private networking errors between machines in some regions, starting at 2026-09-23 14:47 UTC and lasting 35 min. A fix was implemented by 2026-09-23 14:56 UTC, and the incident was resolved at 2026-09-23 15:23 UTC.

Elastic Cloud reported major provisioning delays affecting new deployments, scaling, and maintenance-related instance relocations due to an external container image provider’s slowness; existing running deployments were unaffected. It started at 2026-09-23 14:04 UTC and resolved at 2026-09-23 16:03 UTC, lasting 1 h 58 min. Customers could retry failed plan changes as mitigation.

A major Upstash outage started 2026-09-23 12:42 UTC and resolved 2026-09-24 07:22 UTC (18 h 39 min). Redis connection timeouts affected databases hosted in fra or gig and clients routed through either region, including databases elsewhere. Replicas failed to finish draining during a planned rolling upgrade and remained out of service; a fix was implemented.

Confluent reported a major incident degrading Cloud Console in all regions and multiple services in AWS us-west-2, including degraded Flink jobs and failed new job submissions. It started at 2026-09-23 11:47 UTC and was resolved at 2026-09-23 23:17 UTC, lasting 11 h 29 min. All affected services recovered; no customer action was required.

Sanity’s Content Agent failed to deliver responses to users in a major-impact incident starting 2026-09-23 10:54 UTC and lasting 59 min, until resolution at 2026-09-23 11:53 UTC. Sanity implemented a fix at 09-23 11:23 UTC and monitored the results before resolving the incident.

Buffer reported a major incident preventing Threads connections and refreshes, starting 2026-09-23 10:52 UTC and resolved at 2026-09-23 14:54 UTC, lasting 4 h 1 min. Buffer linked the issue to Threads authentication and said the Threads team deployed a fix, restoring normal channel connections.

Amplitude reported a major degradation preventing delivery of automated exports that filter events across all export destinations, beginning 2026-09-22 23:50 UTC. The tracked incident lasted 6 h 5 min, from 2026-09-23 08:02 UTC to 2026-09-23 14:07 UTC. A fix restored all affected jobs; Amplitude expected no data loss and required no customer action.

Fly.io reported a major IPv6 connectivity incident affecting a subset of hosts in DFW, starting 2026-09-23 06:18 UTC and resolved at 2026-09-23 12:15 UTC, lasting 5 h 57 min. Machines on affected hosts could experience inbound/outbound IPv6 issues; IPv4 was unaffected. Fly.io identified regional maintenance by an upstream internet transit provider.

Pinecone reported a major incident affecting a small percentage of Serverless read requests in AWS eu-west-1 with 5xx errors. It started at 2026-09-22 23:34 UTC and was resolved at 2026-09-23 00:32 UTC, lasting 57 min. Pinecone reported mitigating the errors at 2026-09-23 00:05 UTC.

OneSignal’s Subscription API had a major outage preventing all customers from creating new subscriptions from 2026-09-22 21:05 UTC to 2026-09-22 21:30 UTC, lasting 25 min. A mitigation was applied at 21:19 UTC, and OneSignal confirmed all impacted systems were operating normally at resolution.

Buildkite reported a major incident affecting webhook ingestion, GraphQL queries and some web requests, starting at 2026-09-22 20:07 UTC and resolved at 2026-09-22 20:50 UTC (42 min). The postmortem places customer impact between 19:09 and 19:32 UTC: 2.0% of webhook ingestion requests and 20.3% of external GraphQL requests returned HTTP 500 errors.

Semgrep reported a major outage preventing Managed Scans and CI scans from completing because findings could not upload, alongside web UI access issues. It started at 2026-09-22 19:24 UTC and resolved at 2026-09-22 19:37 UTC, lasting 12 min. Engineering initiated a rollback and confirmed all products operational.

Amplitude’s major Snowflake Data Share delivery outage began at 17:00 UTC (recorded start: 2026-09-22 18:49 UTC) and resolved at 2026-09-23 00:53 UTC; recorded duration: 6 h 4 min. Amplitude fixed an authentication issue; exports resumed normally, with no data loss expected or customer action needed, while existing shared data, ingestion and analytics remained unaffected.

A major Confluent Cloud incident caused elevated errors and intermittent connectivity for some clusters in Azure Germany West Central, associated with an Azure disruption. Issues began approximately 13:00 UTC on 22 Sep 2026; recorded start: 2026-09-22 15:09 UTC. Mitigation: 18:00 UTC; resolved: 2026-09-22 19:58 UTC; tracked duration: 4 h 49 min.

Grafana Cloud reported a major IRM incident starting 2026-09-22 14:57 UTC, causing access issues and undelivered pages for a small group of users; most users were unaffected. A fix was rolled out progressively, and the incident was marked resolved at 2026-09-23 11:07 UTC after 20 h 10 min.

Buffer reported a critical availability disruption starting at 2026-09-22 14:49 UTC, resolved at 2026-09-22 15:45 UTC after 55 min. Buffer was loading normally again by 15:14 UTC and was monitored for stability; no cause was stated.

Chat at go.superhuman.com failed to load for some users, affecting Superhuman Go & Agents in a major-impact outage. It started at 2026-09-22 13:46 UTC and was resolved at 2026-09-22 14:50 UTC, lasting 1 h 3 min. A fix was implemented by 09-22 14:44 UTC.

Deepgram reported a major incident affecting its TTS API: some Aura-2 TTS requests for English voices returned elevated 503 Service Unavailable errors. It started at 2026-09-22 12:10 UTC and was resolved at 2026-09-22 12:50 UTC, with a computed duration of 39 min; no cause or fix was stated.

Lovable reported a major incident affecting enabling Lovable Cloud in all regions; existing Lovable Cloud projects were not impacted. It started at 2026-09-22 07:53 UTC and was resolved at 2026-09-22 08:07 UTC, lasting 14 min; Lovable reported full recovery and normal operational levels.

Anthropic reported a major outage with elevated request errors affecting Claude Mythos 5 and 5.1, Claude Fable 5 and 5.1, and Claude Opus 5. The incident started 2026-09-22 00:57 UTC and resolved at 2026-09-22 02:35 UTC (1 h 37 min); Anthropic stated actual impact occurred from 00:50 UTC to 02:10 UTC.

Claude reported major elevated request errors affecting Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5. The incident started at 2026-09-22 00:57 UTC and resolved at 2026-09-22 02:35 UTC, lasting 1 h 37 min; the final update reported customer impact from 00:50 UTC to 02:10 UTC.

Aiven reported a major outage starting 2026-09-22 00:55 UTC, resolved at 2026-09-22 08:05 UTC (7 h 10 min). A certificate problem caused sign-in failures and service-operation errors across the Console, API, CLI, Terraform provider and API-based integrations. A corrected certificate was deployed across all API nodes by 02:05 UTC, with no further errors observed during monitoring.

Smartsheet’s major login incident caused intermittent blank pages or “upstream request timeout” errors, affecting Australia, Europe and the United States. It started at 2026-09-21 22:21 UTC and was resolved at 2026-09-22 03:43 UTC, lasting 5 h 21 min. Smartsheet attributed the issue to scheduled security maintenance on egress firewalls and confirmed login functionality was fully restored.

Expo reported a major incident affecting iOS submissions through EAS Submit, with logs pointing to App Store Connect API 502 errors. It started at 2026-09-21 21:18 UTC and was resolved at 2026-09-22 06:42 UTC, lasting 9 h 23 min; Expo reported submissions looked healthy at 09-21 21:32 UTC.

Pendo reported a critical guide-targeting disruption affecting a subset of visitors in the US environment (app.pendo.io), starting at 2026-09-21 20:54 UTC. Pendo deployed a fix, reported targeting restored at 21:16 UTC, and resolved the incident at 21:28 UTC; the recorded duration was 34 min.

Expo reported a major incident affecting iOS submissions through EAS Submit, with elevated failures and logs pointing to App Store Connect API 502 responses. It started at 2026-09-21 20:26 UTC and was resolved at 2026-09-21 20:41 UTC (computed duration: 14 min); Expo reported the third-party API was healthy again before resolution.

Baseten reported a major Dedicated Inference incident causing elevated inference 500s for a subset of models deployed in GCP central1. It started at 2026-09-21 18:34 UTC and was resolved at 2026-09-21 18:41 UTC, with a computed duration of 6 min; a fix was implemented by 18:38 UTC.

Brex reported a major incident involving unexpectedly invalidated Developer API tokens affecting Authentication and Partner API. It was marked resolved, starting and ending at 2026-09-21 17:54 UTC (computed duration: 0 min), although the update said investigation was ongoing. Affected customers must generate new tokens in developer settings because invalidated tokens cannot be reused.

MyGreenhouse job search was unavailable to job seekers in a major-impact outage starting 2026-09-21 16:37 UTC. The incident lasted 38 min and was resolved at 2026-09-21 17:15 UTC; Greenhouse reported identifying the issue and implementing a fix but gave no cause.

Confluent recorded a major incident starting 2026-09-21 16:15 UTC: Kafka, Connect, and Flink requests failed or slowed in AWS us-west-2, while Cloud Console degradation affected cluster visibility across regions. Resolved at 2026-09-22 01:31 UTC after 9 h 16 min; all affected services recovered, and no customer action was required.

Netlify reported a major outage affecting access to Netlify-hosted sites on the High-Performance Edge Network and Standard Edge Network; customers could also experience issues accessing the Netlify application and its features. It started at 2026-09-21 15:12 UTC and was resolved at 2026-09-21 16:37 UTC, lasting 1 h 24 min. Netlify reported implementing a fix.

Aiven reported a major Console outage starting 2026-09-21 04:57 UTC, preventing login and support ticket creation through the portal. A fix restored functionality at 09-21 06:01 UTC; the incident was resolved at 2026-09-21 08:25 UTC after 3 h 27 min. Customers needing urgent assistance were directed to support@aiven.io.

Webflow’s critical incident disrupted form submission notification emails for some customers, starting 2026-09-21 00:45 UTC and resolving 2026-09-22 17:05 UTC (40 h 19 min). Webflow attributed the issue to an upstream provider; notification delivery was restored, while form submissions continued to be saved and webhook delivery was unaffected.

RunPod reported a critical network connectivity outage in US-IL-1 starting at 2026-09-20 20:04 UTC. It lasted 14 min and was resolved at 2026-09-20 20:18 UTC, when RunPod confirmed the US-IL-1 DC network was operating normally.

Optimizely reported a major CMP outage affecting a subset of GCP-stack customers: data failed to load in Plan, Resources, Library, and other modules. The incident started at 2026-09-20 11:24 UTC and was resolved at 2026-09-20 13:08 UTC, lasting 1 h 43 min. A fix was implemented at 11:51 UTC; no cause was stated.

Baseten reported a major Kimi K3 Model API outage starting 2026-09-20 07:19 UTC, lasting 54 min and resolving at 2026-09-20 08:13 UTC. About 20% of calls returned errors, with calls to the US-hosted endpoint specifically affected; a fix was implemented at 08:04 UTC.

Brevo reported a critical outage affecting Contacts and Imports services, disrupting usage for some customers starting 2026-09-19 12:51 UTC. The incident lasted 38 min and was resolved at 2026-09-19 13:30 UTC; Brevo reported mitigating the impact and reducing errors but did not disclose the cause or specific fix.

Some ElevenAgents calls failed to start during a major outage from 2026-09-18 23:32 UTC to 2026-09-19 02:08 UTC, lasting 2 h 36 min. ElevenLabs released another fix that reduced the error rate, then confirmed full resolution.

Major outage: Fusion Stable scheduled jobs and Studio IDE encountered “No schema found for get columns in relation call” errors from 2026-09-18 23:31 UTC to 2026-09-19 14:30 UTC (14 h 58 min). A fix reached Latest and Stable release tracks; customers no longer needed the temporary Fusion Extended workaround.