Notable SaaS vendor changes, page 13

Snowflake reported a major Snowsight authentication outage in AWS - US West (Oregon), causing immediate logout after successful authentication. The vendor stated a start of 15:00 UTC August 24, 2026; recorded duration was 1 h 41 min, resolved at 2026-08-24 18:03 UTC. Snowflake attributed the issue to a system configuration and implemented a fix.

Paddle reported a major Retain outage, recorded from 2026-08-24 08:35 UTC to 2026-08-24 09:22 UTC (47 min), though its initial update said the issue began around 7:56 UTC. A fix was deployed at 09:11 UTC, and all services were operating normally at resolution.

GitHub reported a major degradation affecting Claude Fable 5 in Copilot products and IDE surfaces, with elevated errors and requests failing mid-response; no other models were impacted. The incident started at 2026-08-24 07:12 UTC and was resolved at 2026-08-24 07:58 UTC, lasting 46 min. GitHub attributed it to an upstream provider issue, resolved through the provider’s mitigation.

GitHub Copilot reported a major degradation affecting Claude Fable 5, with elevated errors and requests failing mid-response; no other models were impacted. The incident started at 2026-08-24 07:12 UTC and was resolved at 2026-08-24 07:58 UTC, lasting 46 min. An upstream provider issue caused the disruption, and the provider applied a mitigation.

Claude reported a major incident involving elevated errors across claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork, affecting Claude Mythos 5, Claude Fable 5, Claude Opus 5 and Claude Opus 4.8. It started 2026-08-24 05:06 UTC and was resolved 2026-08-24 08:30 UTC, lasting 3 h 24 min.

Anthropic reported a major incident involving elevated errors on claude.ai, Claude API (api.anthropic.com), Claude Code, and Claude Cowork. Started: 2026-08-24 05:06 UTC; resolved: 2026-08-24 08:30 UTC; duration: 3 h 24 min. The final update reported user errors from 04:50 UTC through 07:36 UTC, including requests to Claude Opus 5 and Fable 5.

Fly.io reported a major network incident in the Los Angeles (LAX) region, where apps could experience higher latency or be unreachable. It started at 2026-08-23 01:28 UTC and was resolved at 2026-08-23 02:10 UTC, lasting 41 min. Fly.io stated that upstream networking issues had resolved.

A critical incident caused 500 errors when accessing Lever, affecting Global Data Center - LeverTRM - Hire and Hire. It started at 2026-08-21 20:12 UTC and was resolved at 2026-08-24 14:16 UTC, lasting 2 days 18 h. Lever implemented a fix at 08-21 20:29 UTC and promised an RCA within 7-10 business days.

Cloudsmith reported a major global package-caching outage affecting Package Downloaded webhooks; package pulls remained unaffected. Recorded from 2026-08-21 18:15 UTC to 2026-08-21 18:54 UTC (39 min), impact reportedly began approximately 17:00 UTC. Caching resumed after a fix; packages pulled between 17:00 and 18:45 UTC were missing from repositories and will be cached on subsequent pulls.

Lattice reported a major incident affecting the admin Compensation Cycle Recommendations table, which showed a "Something Went Wrong" error, starting 2026-08-21 16:30 UTC. It was resolved at 2026-08-21 18:24 UTC, lasting 1 h 53 min. A fix was deployed; admins were instructed to refresh the page to see data successfully.

Drata reported critical SafeBase request failures: some requests errored or timed out because edge traffic filtering rules blocked legitimate traffic. Recorded start and resolution were both 2026-08-21 01:00 UTC (computed duration: 0 min), although the vendor described approximately six minutes of failures on August 20.

Socket reported a major Socket API incident in which the Events collection system incorrectly rejected Firewall Events. It started at 2026-08-20 23:05 UTC and was resolved at 2026-08-21 01:06 UTC, lasting 2 h 1 min; customers’ Firewall Events could be rejected or dropped during that period.

Claude reported a major incident involving elevated errors on requests to multiple models, affecting claude.ai, Claude API (api.anthropic.com), Claude Code, and Claude Cowork. It started at 2026-08-20 19:16 UTC and was resolved at 2026-08-20 19:42 UTC, lasting 26 min; no cause or fix details were stated.

Anthropic reported a major incident involving elevated errors on requests to some Claude models, affecting claude.ai, Claude API (api.anthropic.com), Claude Code, and Claude Cowork. It started at 2026-08-20 19:16 UTC and was resolved at 2026-08-20 19:42 UTC, lasting 26 min; no cause or specific fix was stated.

Ably reported a major incident with elevated errors in ap-southeast-1, affecting Ably Pub/Sub - Asia-Pacific (Singapore) and Asia-Pacific (Singapore). It started at 2026-08-20 19:07 UTC and was resolved at 2026-08-20 19:10 UTC; the computed duration was 2 min. No cause or fix was stated.

v0 reported a major Functions incident: newly deployed container functions could return 5XX errors starting at 2026-08-20 17:46 UTC. Customers could temporarily use a previously working deployment; a fix was deployed at 2026-08-20 18:23 UTC. The incident was resolved at 2026-08-20 18:34 UTC, lasting 47 min.

Vercel reported a major Functions outage: newly deployed container functions could return 5XX errors from 2026-08-20 17:46 UTC until resolution at 2026-08-20 18:34 UTC (47 min). Customers could temporarily use a previously working deployment; Vercel reported deploying a fix at 18:23 UTC, restoring newly deployed container functions.

Retool reported a major React App Builder incident: downstream dependency issues could prevent sandbox installation and connection on Cloud and Self-Hosted instances. It ran from 2026-08-20 17:26 UTC to 2026-08-20 23:20 UTC (5 h 54 min); Cloud recovered at 17:30 UTC, and self-hosted fixes shipped in 4.0.12-stable and 4.43.0-edge.

Confluent Cloud reported a major incident affecting Kafka clusters in GCP us-west1, with elevated latency, request timeouts, and increased error rates. It started at 2026-08-20 17:10 UTC and was resolved at 2026-08-20 20:18 UTC, lasting 3 h 7 min. Confluent said the GCP issues were mitigated and monitoring showed no remaining impact.

PandaDoc reported a major incident affecting document creation and viewing, with creating/editing, sending and uploading components listed for US & Global. It started at 2026-08-20 17:03 UTC and was resolved at 2026-08-20 21:42 UTC, lasting 4 h 38 min. PandaDoc reported mitigation at 17:20 UTC with no further degradation; no root cause was stated.

Render reported a major Builds and Deploys outage across Frankfurt, Ohio, Oregon, Singapore and Virginia, starting 2026-08-20 15:47 UTC and resolved at 2026-08-20 19:40 UTC (3 h 53 min). Render identified an upstream Google Cloud issue; Free Web Services builds, deploys and spin-up were temporarily disabled, then re-enabled during recovery.

GitHub Copilot reported a critical incident starting 2026-08-20 14:43 UTC, resolved 2026-08-21 00:37 UTC (9 h 54 min). Some Copilot Cloud Agent users saw task status/results delayed up to 60–90 minutes, while tasks continued running and completing. GitHub cited a regional third-party cloud database outage and deployed a fix.

GitHub’s critical Copilot Cloud Agent incident started at 2026-08-20 14:43 UTC and resolved at 2026-08-21 00:37 UTC, lasting 9 h 54 min. Task status and results were delayed by up to 60 to 90 minutes; tasks continued running and completing. GitHub cited a regional third-party cloud database outage and deployed a fix.

Snowflake reported a major outage in Azure - East US 2 (Virginia): customers may have been unable to connect through private connectivity solutions such as PrivateLink. It started at 2026-08-20 13:47 UTC and was resolved at 2026-08-20 15:43 UTC, lasting 1 h 56 min. The third-party cloud platform implemented mitigation; Snowflake verified service restoration.

Elastic Cloud reported a major incident affecting new Serverless project initialization in Azure eastus, causing longer creation times due to an upstream Azure storage component issue. It started at 2026-08-20 12:48 UTC and lasted 3 h 34 min, resolving at 2026-08-20 16:22 UTC after Azure's storage issues were resolved and creation times returned to normal.

v0 reported a major outage preventing runtime log queries in the Dashboard from 2026-08-20 11:14 UTC to 2026-08-20 11:25 UTC, lasting 11 min. Log ingestion and build-log queries were unaffected. A fix restored runtime-log queries at 11:21 UTC, with full recovery confirmed at 11:25 UTC.

Vercel reported a major outage preventing runtime log queries in the Dashboard from 2026-08-20 11:14 UTC to 2026-08-20 11:25 UTC, lasting 11 min. Log ingestion and build-log queries were unaffected; Vercel implemented a fix and confirmed full recovery.

Fly.io reported a major partial outage of MPG (v1) in ORD from 2026-08-20 07:25 UTC to 2026-08-20 07:57 UTC, lasting 32 min. An issue with the ord-0 Fly Kubernetes cluster left many MPG clusters unable to restart; a fix was implemented at 07:32 UTC, and the incident was resolved.

Tailscale reported a major coordination service incident with elevated error rates, starting 2026-08-20 00:58 UTC and resolved at 2026-08-20 03:22 UTC, lasting 2 h 24 min. A fix was deployed by 02:38 UTC; no cause was stated.

Box reported a major-impact incident causing errors or slowness accessing Microsoft Office via Box and using Box Edit, from 2026-08-20 00:31 UTC to 2026-08-20 01:44 UTC (1 h 13 min). Box took remediation steps and confirmed full functionality was restored; no specific cause or fix was stated.

Mixpanel reported a major incident affecting event-property population in dropdown menus across EU, IN and US application availability. It started at 2026-08-19 23:20 UTC and was resolved at 2026-08-20 03:05 UTC, lasting 3 h 44 min. A fix was implemented before resolution; no cause was stated.

Box reported a major-impact incident affecting Login, All Files, Uploads, Downloads and Box API. The archived start and resolution are both 2026-08-19 22:00 UTC (computed duration: 0 min). Box said no further impact was observed and marked the issue resolved; a preliminary postmortem was later posted.

RunPod reported a critical network connectivity outage in EUR-NO-2 starting at 2026-08-19 19:06 UTC. It lasted 48 min and was resolved at 2026-08-19 19:54 UTC, when RunPod confirmed the data center network was operating normally.

SurveyMonkey’s Multi-Survey Analysis displayed a blank page in a major-impact incident starting at 2026-08-19 17:23 UTC. A fix was implemented, and the incident was resolved at 2026-08-19 17:37 UTC after 14 min.

QuickBooks Online reported a major latency incident affecting some customers in Canada, EMEA and the United States, starting 2026-08-19 14:30 UTC and resolved at 2026-08-19 16:54 UTC (2 h 23 min). Engineering implemented a fix, and the final update confirmed all services were restored; no specific cause was disclosed.

AssemblyAI reported a major Universal 3.5 Pro Realtime outage: EU endpoint users could not create streaming sessions and received code 3005 during 13:00–13:12 UTC; US users were unaffected. The incident started at 2026-08-19 13:17 UTC and resolved at 2026-08-19 13:24 UTC (7 min), after a fix restored session creation.

DigitalOcean reported a critical MKC1 outage starting 2026-08-19 11:10 UTC, disrupting GPU workloads and Serverless Inference, with DOKS worker nodes entering NotReady states. It was marked resolved at 2026-08-19 19:34 UTC after 8 h 24 min; the regional control plane and other listed services were healthy, but GPU Droplets remained impacted while restoration continued.

Zapier Functions had a major outage starting 2026-08-18 23:50 UTC, resolved at 2026-08-18 23:58 UTC after 8 min. Users could not create, edit, or run Functions, and migrations could be disrupted; Zaps and other Zapier services were unaffected, and no data loss occurred.

Grafana Cloud reported a critical Cloud Logs read outage in eu-west-2 on loki-prod-012, affecting Explore, dashboards and alert evaluation querying Logs. The recorded start was 2026-08-18 22:53 UTC and resolution 2026-08-18 22:00 UTC, while the vendor described impact between approximately 22h15 and 22h23 UTC; duration is unknown.

Netlify recorded a critical incident starting at 2026-08-18 20:00 UTC, with a computed duration of 0 min and status resolved. Its update reports error pages for some Netlify-hosted site visitors and dashboard users between 20:02 and 20:08 UTC, with normal service restored at 20:08 UTC.

Astronomer reported a major degradation from 2026-08-18 18:51 UTC to 2026-09-10 22:19 UTC, lasting 23 days 3 h. A metrics reporting bug falsely flagged missed scheduler heartbeats, affecting Astro UI dashboard and monitoring visibility; task execution, scheduling, and workflow processing were unaffected. Astronomer reported rolling out a fix and later marked the issue resolved.

Segment reported a major incident causing intermittent login errors for a subset of customers, affecting Web Interface (EU) and Web Interface (US). It started at 2026-08-18 17:49 UTC and was resolved at 2026-08-18 22:02 UTC, lasting 4 h 13 min; login was reported operating normally at 18:38 UTC.

Snowflake reported a major outage affecting Cortex Code in Snowsight in AWS - US East (N. Virginia), from 2026-08-18 12:58 UTC to 2026-08-18 14:51 UTC (1 h 53 min). Customers could encounter internal server errors; Snowflake identified container scheduling issues in its compute infrastructure and implemented a fix.

Lovable reported a major Shopify integration outage: creating new Lovable apps with Shopify was not working. It started at 2026-08-18 09:49 UTC and was resolved at 2026-08-18 10:22 UTC, lasting 32 min; Lovable confirmed the integration was restored.

GitHub reported a major Actions outage starting 2026-08-18 09:36 UTC, resolved at 2026-08-18 10:23 UTC (46 min). Customers could not run jobs on Actions Larger Runners or view/manage Actions Runners and Runner Groups through the GitHub UI and API; GitHub attributed the failures to backend requests resolving essential metadata.