Everything SaaS vendor changes, page 16

RunPod’s US-IL-1 datacenter was unavailable due to a power outage, with critical impact, from 2026-08-14 21:30 UTC to 2026-08-15 03:40 UTC, lasting 6 h 10 min. Power was restored to most servers by 08-15 02:59 UTC; the vendor confirmed normal datacenter operation at resolution.

A major degradation affected Claude API (api.anthropic.com), Claude Code, and Claude Cowork. The incident started at 2026-08-14 20:30 UTC and was resolved at 2026-08-14 21:58 UTC (1 h 27 min); Anthropic reported customer impact from 20:14 to 20:38 UTC. A fix was deployed at 20:44 UTC, but no specific cause was disclosed.

Claude reported a major degradation affecting Claude API (api.anthropic.com), Claude Code, and Claude Cowork, starting 2026-08-14 20:30 UTC and resolved at 2026-08-14 21:58 UTC (computed duration: 1 h 27 min). The vendor reported actual impact from 20:14 to 20:38 UTC. A fix was deployed at 20:44 UTC; the cause was not specified.

Fly.io’s major secrets service outage blocked new app creation and secret updates; existing apps continued running. It lasted 1 h 3 min, from 2026-08-14 19:30 UTC to 2026-08-14 20:33 UTC. Fly.io cited a failed deployment and failed over the secrets database to a replica, after which the Machines API appeared healthy.

Snowflake reported a critical Snowsight outage in Azure - East US 2 (Virginia), blocking access/sign-in with “503 Service Unavailable” errors. Recorded from 2026-08-14 17:29 UTC to 2026-08-14 19:35 UTC (2 h 5 min), customer impact reportedly began at 17:05 UTC August 14, 2026. Snowflake implemented a fix for a system configuration issue and confirmed service restoration.

Unbounce reported a major Page Servers outage in Asia Pacific: visitors to live pages could see gateway errors; no other regions were affected. It started at 2026-08-14 15:28 UTC and was resolved at 2026-08-14 17:42 UTC, lasting 2 h 14 min. Unbounce implemented a fix and reported health checks back to 100%.

Grammarly reported a major outage involving login issues across some Grammarly and Superhuman products and preventing some users from accessing Grammarly Editor documents. It lasted 2 h 33 min, from 2026-08-14 15:24 UTC to 2026-08-14 17:57 UTC; a fix was implemented and the incident was resolved.

Snowflake reported a critical Snowsight availability outage affecting Applications in AWS - US East (Ohio), with intermittent authentication failures and "service unavailable" errors. The incident started at 2026-08-14 15:19 UTC and resolved at 2026-08-14 16:28 UTC; recorded duration was 1 h 8 min. Automated recovery restored service; a postmortem links to an RCA on Snowflake Community.

Retool reported a major incident causing errors when calling resources with Per-User authentication in Apps built with the New App Editor. It started at 2026-08-14 15:06 UTC and was resolved at 2026-08-14 19:00 UTC, lasting 3 h 53 min. A fix was implemented by 2026-08-14 16:36 UTC; no cause was stated.

Sanity reported a major incident affecting api.sanity.io and apicdn.sanity.io, with elevated error rates identified from 14:34 UTC until a fix restored normal rates at 14:40 UTC. The incident record started at 2026-08-14 14:46 UTC and was resolved at 2026-08-14 15:32 UTC; its recorded duration was 45 min.

Elastic Cloud reported a major Elasticsearch 9.5.1 issue causing false-positive matches in boolean queries combining multi-value terms in must, filter, or should clauses with must_not on fields with disabled indexing. It ran from 2026-08-14 09:22 UTC to 2026-08-20 17:09 UTC (6 days 7 h); Elasticsearch 9.5.2 fixes it, and customers on 9.5.0 or 9.5.1 should upgrade.

Discord reported a major incident affecting call establishment from 2026-08-14 06:09 UTC to 2026-08-14 06:24 UTC, lasting 14 min. A fix was implemented by 2026-08-14 06:14 UTC, and the incident was resolved.

Sentry reported major ingestion delays for spans and transactions in DE and US, with a US errors backlog also noted. The incident started at 2026-08-13 17:47 UTC and lasted 4 h 39 min, delaying ingestion of affected customer telemetry. Sentry resolved it at 2026-08-13 22:27 UTC after all backlogs were processed.

Grafana Cloud reported a critical K6 Test Outage starting 2026-08-13 15:25 UTC, lasting 1 h 22 min and resolved at 2026-08-13 16:47 UTC. Telemetry push APIs went down at 15:06 UTC, causing tests to lose metrics, logs, traces and browser screenshots; Grafana reported mitigation but did not state a root cause.

Claude reported a major incident involving elevated request errors for Claude Mythos 5, Claude Fable 5, and Claude Sonnet 5, affecting claude.ai, Claude API (api.anthropic.com), Claude Code, and Claude Cowork. It started at 2026-08-13 14:33 UTC and was resolved at 2026-08-13 16:08 UTC, lasting 1 h 34 min; the resolution update named Mythos 5 and Fable 5.

Anthropic reported a major incident with elevated request errors for Claude Mythos 5, Claude Fable 5, and Claude Sonnet 5, affecting claude.ai, Claude API (api.anthropic.com), Claude Code, and Claude Cowork. It started at 2026-08-13 14:33 UTC and was resolved at 2026-08-13 16:08 UTC, lasting 1 h 34 min; no cause or fix was stated.

Contentful reported a major incident causing Content Management API latency and errors for some customers in the EU data residency region. It started at 2026-08-13 09:34 UTC and was resolved at 2026-08-13 11:38 UTC, lasting 2 h 4 min; Contentful said the issue was addressed without specifying a cause or fix.

Elastic Cloud reported a major incident starting 2026-08-13 08:32 UTC, lasting 4 days 3 h, with search embedding failures for microsoft-multilingual-e5-large due to upstream provider issues. Resolved 2026-08-17 11:40 UTC, the model was retired from Elastic Inference Service; requests now return errors, and customers must create custom inference endpoints using their own API keys.

Elastic Cloud reported a major outage delaying or failing Serverless project creation and settings changes through the Cloud UI or API; running projects continued operating normally. It started at 2026-08-13 03:57 UTC and was resolved at 2026-08-13 08:40 UTC, lasting 4 h 42 min. A fix was deployed by 06:04 UTC; no cause was stated.

Perplexity reported a critical API issue starting at 2026-08-13 00:45 UTC, resolved at 2026-08-13 01:49 UTC after 1 h 4 min. The vendor identified a problematic deploy and rolled back the service; the incident affected API service, but specific customer-facing symptoms were not stated.

Acuity Scheduling had a critical service disruption starting 2026-08-12 22:55 UTC; Squarespace said all users and services may be affected. Engineering identified the issue, and the incident was resolved at 2026-08-12 23:12 UTC after 16 min; no specific cause or fix was stated.

Sentry reported a major incident affecting US Error Ingestion and US Errors Alerting from 2026-08-12 21:58 UTC to 2026-08-12 22:52 UTC, lasting 54 min. Error ingestion was delayed; Sentry mitigated the source of latency and processed the backlog before resolving the incident.

GitHub reported a major disruption affecting login pages and Release Asset downloads, starting 2026-08-12 21:39 UTC and resolved at 2026-08-12 22:56 UTC (1 h 17 min). Some logged-out requests received HTTP 5xx errors because an unusual traffic pattern repeatedly overloaded infrastructure serving those requests.

GitHub reported a major disruption affecting login and Release Asset downloads, starting 2026-08-12 21:39 UTC and resolved 2026-08-12 22:56 UTC (1 h 17 min). Some logged-out requests received HTTP 5xx errors; GitHub attributed these to an unusual traffic pattern repeatedly overloading infrastructure serving those requests.

Metabase Store was unavailable from 2026-08-12 19:13 UTC to 2026-08-12 20:52 UTC, a critical outage lasting 1 h 39 min. Metabase reported maintenance on the Store infrastructure and subsequently marked the incident resolved.

Metabase Store was unavailable with critical impact from 2026-08-12 19:13 UTC to 2026-08-12 20:52 UTC, lasting 1 h 39 min. Metabase reported maintenance on the Store infrastructure and initially expected it to be operational within an hour; the incident was subsequently resolved.

Expo reported a major outage causing login errors in Expo Go and Dev Clients, starting 2026-08-12 19:00 UTC and resolved at 2026-08-13 00:00 UTC, lasting 5 h 0 min. Expo confirmed a fix was deployed; no cause was stated.

Semgrep reported a major incident affecting Managed Scans: lockfileless scans failed for certain deployments from 2026-08-12 18:16 UTC until resolution at 2026-08-12 21:03 UTC, lasting 2 h 46 min. A fix was rolled out by 2026-08-12 20:23 UTC, restoring scans; no specific root cause was disclosed.

Lever reported a critical outage causing failed hire.lever.co page loads, platform access failures and elevated API errors. A support-initiated backend data query caused an out-of-memory error; service was restored. Recorded start was 2026-08-12 18:13 UTC and resolution was 2026-08-12 17:31 UTC; these timestamps conflict, and duration is unknown.

Brevo reported a critical Phone Application incident disrupting some customers’ incoming and outgoing calls, starting at 2026-08-12 12:44 UTC and resolved at 2026-08-12 13:11 UTC; the computed duration was 26 min. Brevo said it identified the cause without detailing it, mitigated the impact, and restored normal service.

Sentry reported a major degradation affecting US Error Ingestion and US Errors Alerting, starting 2026-08-12 11:45 UTC and resolved at 2026-08-12 14:48 UTC (3 h 2 min). Error ingestion and alerts were delayed; Sentry applied a fix and confirmed the backlog was processed.

Matillion reported a major incident affecting access to Designer and Maia, listing Designer components in the AU, EU and US regions. It started at 2026-08-12 08:17 UTC and was resolved at 2026-08-12 11:50 UTC, lasting 3 h 32 min. Matillion implemented a fix but did not state a cause.

Drata reported a major incident affecting in-app completion notifications for some report and export downloads, with no evidence that files failed to generate or were lost. It started 2026-08-11 21:06 UTC and was resolved 2026-08-14 19:44 UTC, lasting 2 days 22 h; a fix was deployed and validated.

Smartsheet reported a critical outage from 2026-08-11 19:51 UTC to 2026-08-11 23:20 UTC (3 h 28 min), causing Sheets and Reports loading timeouts/failures and automation failures that disabled some workflows. Smartsheet attributed it to a database query-routing issue sending certain reads to primary write servers; a mitigation was applied before resolution.

Brex reported a critical incident causing intermittent dashboard access issues from 2026-08-11 17:16 UTC to 2026-08-11 19:12 UTC, lasting 1 h 56 min. Brex reported a fix in place at 18:17 UTC and subsequently marked the incident resolved; no cause was stated.

Fireworks AI reported a major cloud service provider outage affecting many serverless and dedicated deployments, starting 2026-08-11 17:15 UTC and lasting 46 h 35 min. The upstream provider recovered but experienced further instability that disrupted some models; all services were operational when the incident resolved at 2026-08-13 15:51 UTC.

Replayed WhatsApp webhooks reopened tickets and created duplicates; Gorgias rated impact major and reported disruption August 10, between 4:30 PM and 8:00 PM UTC. The incident record ran from 2026-08-11 14:31 UTC to 2026-08-12 10:59 UTC (20 h 27 min). Normal processing resumed; incident-generated billable tickets were removed from affected merchants' billing counts.

Close reported major database failures causing intermittent service unavailability, starting 2026-08-11 13:12 UTC and resolved at 2026-08-11 15:15 UTC (2 h 3 min). Close adjusted its scaling strategy and reported healthy recovery; its partial postmortem separately described about 2.5 hours of intermittent unavailability between 08:00 UTC and 17:03 UTC.

Gorgias reported a major incident involving CORS issues during signup, affecting some users. It started at 2026-08-11 11:36 UTC and was resolved at 2026-08-11 13:16 UTC, with a reported duration of 1 h 39 min; no cause or specific fix was stated.

French eSIM numbers were unreachable in a major Aircall outage from 2026-08-11 10:05 UTC to 2026-08-11 12:30 UTC, lasting 2 h 25 min. Aircall said the issue appeared to originate with its Carrier Partner; the partner implemented a fix, and Aircall confirmed full resolution.

Close reported a major database-failure outage affecting the API and Application UI, starting at 2026-08-11 08:26 UTC and resolved at 2026-08-11 09:26 UTC (reported duration: 59 min). Engineering remediated an issue with the production database; users were told normal app use was restored by 09:04 UTC.

Mailgun reported a major denial-of-service attack against click and open tracking servers in US regions, causing some requests to time out or fail. The incident started at 2026-08-11 05:32 UTC and was resolved at 2026-08-11 07:07 UTC, lasting 1 h 35 min; a fix was implemented by 06:54 UTC.

RevenueCat reported a major incident affecting multiple APIs, with elevated error rates and latency starting 2026-08-10 18:37 UTC and lasting 1 h 22 min. A fix was rolled out at 18:56 UTC; error rates and latency returned to normal, and the incident was resolved at 2026-08-10 19:59 UTC.

Lovable reported a major outage affecting some users’ project preview updates and publishing, starting 2026-08-10 16:59 UTC and resolved at 2026-08-10 17:15 UTC (reported duration: 15 min). Both previews and publishing were restored; no cause or specific fix was stated.

ActiveCampaign reported a major login outage affecting a portion of users, with errors or inability to access accounts; listed components included APAC, EU and US platform availability. It started at 2026-08-10 14:14 UTC and resolved at 2026-08-10 16:59 UTC, lasting 2 h 44 min. A fix was implemented at 14:53 UTC; no cause was stated.

Lattice reported a major disruption starting 2026-08-10 13:39 UTC: automated review cycles had not advanced and reminders had not sent since Thursday, August 6th. The incident lasted 4 h 18 min, resolving at 2026-08-10 17:58 UTC after all delayed state updates and notifications were sent; automated schedules were operating on time.

Sumo Logic reported a critical degradation affecting Logs Alerting and Metrics Alerting in Europe 2 (DE), causing latency, slowness, or delays displaying data. It started at 2026-08-10 09:55 UTC and was resolved at 2026-08-10 11:04 UTC, lasting 1 h 8 min; normal operation was restored.