Major incidents SaaS vendor changes, page 15

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.

Buffer reported a major login disruption from 2026-08-09 22:00 UTC to 2026-08-10 04:52 UTC, lasting 6 h 52 min. Customers were unexpectedly logged out, and publishing may have been impacted. Buffer implemented a fix, confirmed publishing success rates returned to normal, and advised retrying posts that failed to publish.

Discord reported a critical API outage starting 2026-08-07 22:21 UTC that prevented users and bots from sending messages, then expanded to all Discord interactions. Service recovered at 22:42 UTC, and the incident was fully resolved at 2026-08-07 23:02 UTC; the reported duration was 40 min.

Sentry reported critical ingestion delays for spans, crons, and logs in the US region, starting 2026-08-07 16:21 UTC and resolved at 2026-08-07 17:08 UTC (47 min). A fix was in place by 16:30 UTC, and ingestion latency returned to normal by 16:48 UTC.

Expo reported a major incident involving increased Android error rates on EAS Submit, starting at 2026-08-07 15:32 UTC and lasting 22 min. A fix was implemented by 2026-08-07 15:50 UTC, and the incident was resolved at 2026-08-07 15:54 UTC.

Typeform reported a major outage starting 2026-08-07 13:37 UTC: some customers could not access Admin, and published forms failed to load or displayed errors. A fix restored service by 08-07 14:43 UTC; the incident was resolved at 2026-08-07 18:37 UTC, with a recorded duration of 4 h 59 min.

Expo reported a major degradation causing increased error rates and processing times for EAS Build and EAS Submit on Android. It started at 2026-08-07 12:39 UTC and was resolved at 2026-08-07 13:13 UTC, lasting 33 min. Expo implemented a fix and monitored the results; no cause was stated.

Apollo.io reported a critical incident causing slow page loads and searches across the app, with no data affected. It started at 2026-08-07 12:33 UTC and was resolved at 2026-08-07 12:51 UTC, lasting 18 min. Apollo attributed the slowdown to a CDN provider issue that was resolved, restoring normal performance.

Jira recorded a critical service-access incident affecting some Central European users, starting 2026-08-07 11:30 UTC and resolved 2026-08-07 12:52 UTC (1 h 21 min). The vendor separately reported user impact between 10:27 UTC and 11:49 UTC, applied a fix, and confirmed normal service for all customers.

Typeform reported a critical platform outage affecting account access, account settings, form creation and opening/loading forms, starting 2026-08-07 11:21 UTC and lasting 51 min. The vendor described a traffic interruption and confirmed a fix was implemented, resolving the incident at 2026-08-07 12:12 UTC; the cause remained under investigation.

Typeform reported a critical platform outage affecting account access, with Account Settings, Back-End and Open/Load forms listed as affected components. It started at 2026-08-07 08:43 UTC and was resolved at 2026-08-07 09:22 UTC, lasting 38 min. Typeform described a traffic interruption and implemented a fix; the cause remained under investigation.

Box reported a major incident affecting authentication, Login/SSO, uploads/downloads, Content API, Box AI and Box Sign, with possible errors or failures. It started 2026-08-07 02:37 UTC and resolved at 2026-08-07 05:16 UTC (2 h 39 min). Box reported no ongoing impact by 04:06 UTC and said remediation restored full functionality.

Lovable reported a major incident preventing some users from connecting ChatGPT to Lovable, with authorization attempts failing. It started at 2026-08-06 22:54 UTC and lasted 7 h 17 min, resolving at 2026-08-07 06:11 UTC after a fix restored normal connections; users still seeing errors were advised to reconnect.

Rippling reported major data-sync delays affecting third-party integrations including Ramp and Box; admins could see disconnected accounts, but existing employee access was unaffected. Recorded start and resolution were both 2026-08-06 18:29 UTC (computed duration: 0 min). Rippling reverted a rollout-related change and retriggered syncs, recovering impacted integrations.

Elastic Cloud reported major Elasticsearch connectivity latency in GCP asia-south1 (Mumbai), with possible customer impact on 2026-08-06 between 0900 - 1200 UTC. The incident record started and resolved at 2026-08-06 17:41 UTC (computed duration: 0 min); the vendor said the cause was identified and mitigated but provided no details.

MessageBird (Bird) reported a major outage affecting Connectors and CRM - Connectors for some customers in Asia (India), Europe and US (West). It started at 2026-08-06 17:05 UTC and was resolved at 2026-08-06 22:08 UTC, lasting 5 h 3 min. A fix was implemented, but the root cause was not disclosed.

RevenueCat reported a critical Rico outage affecting AI features and Dashboard - AI features, with all service requests failing due to an upstream AI inference provider outage. The incident started at 2026-08-06 17:04 UTC and was resolved at 2026-08-06 18:14 UTC, lasting 1 h 10 min; the provider had recovered and Rico was operating normally by 17:16 UTC.

GitHub Actions had critical degraded availability starting 2026-08-06 15:22 UTC, resolved at 2026-08-07 02:04 UTC; recorded duration was 10 h 41 min. Workflows failed or remained queued on GitHub-hosted and self-hosted runners, with infrastructure failures affecting 71% of runs at peak. Recovery instructions for stuck Actions Runner Controller pods were deletion or application redeployment.

GitHub Actions experienced critical degraded availability from 2026-08-06 15:22 UTC to 2026-08-07 02:04 UTC (10 h 41 min), causing failed or queued workflows on GitHub-hosted and self-hosted runners. At peak, 71% of runs experienced infrastructure failures. Users with stuck Actions Runner Controller pods could delete them or redeploy the controller to create replacement runners.

RunPod reported a critical Network Storage issue in EUR-NO-1, affecting storage availability in that data center. The incident ran from 2026-08-06 13:47 UTC to 2026-08-06 15:38 UTC, lasting 1 h 51 min; RunPod confirmed network storage was resolved and operating normally, without stating a cause or specific fix.

Coralogix reported a major RUM outage affecting some customers’ ability to view RUM data or access RUM-related features. It began at 2026-08-06 09:37 UTC and was resolved at 2026-08-06 10:15 UTC; the computed duration was 37 min. A fix was implemented, but no cause was stated.

Sentry reported a major delay in US Error Ingestion from 2026-08-06 08:59 UTC to 2026-08-06 11:21 UTC, lasting 2 h 21 min. A fix was applied, new events returned to real-time processing, and all backlogged events were processed by resolution.

Notion reported a major outage affecting access to notion.com and Notion Sites, with possible issues loading or using Notion clients. The incident started at 2026-08-06 00:29 UTC and was resolved at 2026-08-06 00:37 UTC (8 min tracked duration; the update reported 14 minutes of inaccessibility). Notion reverted the change that inadvertently triggered the outage.

Elastic Cloud reported a major Elasticsearch 9.5.0 defect: boolean queries combining must, filter, or should with must_not on unindexed fields could return false positives and inflated counts. It lasted from 2026-08-05 22:59 UTC to 2026-08-12 08:59 UTC (6 days 10 h); Elasticsearch 9.5.1 fixed it, and customers running 9.5.0 were advised to upgrade.

HashiCorp reported stuck Infragraph snapshots and degraded performance, with major impact, starting at 2026-08-05 20:09 UTC. The incident lasted 1 h 58 min and was resolved at 2026-08-05 22:08 UTC; engineering said systems should be operating normally, but provided no cause or specific fix.

Terraform Cloud (HCP) reported stuck Infragraph snapshots and degraded performance, with major impact, starting 2026-08-05 20:09 UTC. The incident lasted 1 h 58 min and was resolved at 2026-08-05 22:08 UTC; engineering said systems should be operating normally, but provided no cause or specific fix.

Cohere reported a major partial outage of its documentation site: some pages failed to load correctly due to an issue with upstream documentation provider Fern. The incident started at 2026-08-05 19:36 UTC and was resolved at 2026-08-05 20:35 UTC, lasting 58 min; Cohere confirmed service was back to normal.

Descript reported a critical Rooms outage starting at 2026-08-05 19:29 UTC, lasting 28 min and resolved at 2026-08-05 19:57 UTC. Functionality was fully restored at 19:32 UTC, followed by monitoring; no cause was stated.

Terraform Cloud (HCP) reported a critical outage of the Infragraph Service and UI starting 2026-08-05 15:11 UTC. Engineering implemented a fix and confirmed normal operation at 2026-08-05 15:39 UTC; the reported duration was 27 min.

HashiCorp reported a critical outage of the Infragraph Service and UI starting 2026-08-05 15:11 UTC, with degraded performance reported. Engineering implemented a fix at 2026-08-05 15:28 UTC and marked the incident resolved at 2026-08-05 15:39 UTC; the computed duration was 27 min.

Dremio Cloud US experienced a major outage affecting application loading and login; Dremio Cloud Europe operated normally. The incident started at 2026-08-05 14:47 UTC and was resolved at 2026-08-05 18:49 UTC, lasting 4 h 2 min; Dremio reported service recovery and healthy services while monitoring.

ActiveCampaign reported a critical outage affecting segmented campaign sending in the EU Data Center, starting 2026-08-05 10:59 UTC and resolved 2026-08-06 11:40 UTC, lasting 24 h 41 min. A fix was implemented at 08-05 13:12 UTC; no cause was stated.

Apollo GraphQL’s Embedded Explorer and Embedded Sandbox were down in a major-impact incident from 2026-08-05 09:43 UTC to 2026-08-05 10:08 UTC, lasting 25 min. Apollo identified the issue, deployed a fix, and confirmed resolution; no cause was stated.

Coralogix reported a major incident causing log query failures in Explore → Logs (v2 and Legacy), including errors accessing archived log data. It started at 2026-08-05 08:46 UTC and was resolved at 2026-08-05 09:01 UTC, lasting 15 min. Although initially reporting EU1 and US1 impact, Coralogix confirmed only EU1 was affected; all services were restored.

MongoDB Atlas reported a major incident affecting some customers’ deployments due to GCP capacity constraints across North America, Europe, and Asia Pacific/Australia, including M50 and S70L instance types. It started at 2026-08-05 05:17 UTC and was resolved at 2026-08-05 12:14 UTC, lasting 6 h 56 min; MongoDB said symptoms had largely subsided and Atlas was fully operational.

New Claude-to-Notion MCP authorizations failed with “Invalid authorization request,” blocking new connections. Notion rated the incident major and reported failures starting approximately 01:25 UTC on August 5, 2026; the incident was logged at 2026-08-05 03:34 UTC and resolved at 2026-08-05 04:33 UTC (computed duration: 58 min).

Greenhouse reported a major partial disruption in Greenhouse Recruiting - Silo 1, affecting user searches, candidate unhire actions, emails, availability requests, referrals, offer letters, scorecards, candidate notes and interview-plan editing. It started 2026-08-05 02:18 UTC and resolved 2026-08-05 13:29 UTC (11 h 10 min); a fix was implemented at 08-05 03:56 UTC.

Convex reported a major incident causing actions that call createFunctionHandle to fail on business deployments; Free, Starter and Professional users were unaffected. It started at 2026-08-05 01:42 UTC and was resolved at 2026-08-05 01:57 UTC, lasting 14 min. Convex reported implementing and deploying a fix before confirming resolution.

HCP Terraform had a major UI outage causing blank white screens from 2026-08-05 00:05 UTC to 2026-08-05 01:59 UTC, lasting 1 h 54 min. API calls, CI integrations, and CLI usage were not expected to be affected. Engineering implemented a fix at 00:44 UTC and confirmed resolution at 01:59 UTC.

HCP Terraform’s UI showed a blank white screen in a major outage from 2026-08-05 00:05 UTC to 2026-08-05 01:59 UTC, lasting 1 h 54 min. API calls, CI integrations, and CLI usage were not expected to be affected. Engineering implemented a fix at 00:44 UTC and confirmed resolution at 01:59 UTC.

CockroachDB reported a major outage preventing some Basic and Standard clusters in eu-west1 from connecting or executing queries. It ran from 2026-08-04 23:46 UTC to 2026-08-05 19:50 UTC (20 h 3 min). Immediate impact was mitigated by 2026-08-05 03:55 UTC; resolution followed monitoring confirming stability, with no root cause stated.

Anthropic reported a major incident affecting claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork: some users had login issues, including OAuth, and model request errors. It started at 2026-08-04 20:48 UTC and was resolved at 2026-08-04 21:59 UTC, lasting 1 h 11 min; no specific cause or fix was stated.

Claude reported a major incident affecting claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork: some users had login issues, including via oAuth, and model request errors. It started at 2026-08-04 20:48 UTC and was resolved at 2026-08-04 21:59 UTC, lasting 1 h 11 min; success rates had recovered by 21:04 UTC.

Box reported major impact to uploads and downloads across its API and web application, with errors and slowness affecting customers. The incident ran from 2026-08-04 20:23 UTC to 2026-08-04 20:44 UTC (21 min). Box attributed upload failures and delays to frontend load-balancer routing and restored service by rerouting upload traffic and provisioning additional capacity.

Some Grafana instances in GCP US Central (prod-us-central-0, prod-us-central-3, prod-us-central-4) were unavailable during a critical incident from 2026-08-04 19:11 UTC to 2026-08-05 01:32 UTC (6 h 20 min). Grafana reported cloud-provider compute capacity exhaustion, moved affected workloads to alternative capacity, and rolled out a change to restore service.

Fly.io reported a major outage in GRU: new MPG clusters could fail to create due to insufficient capacity. It started at 2026-08-04 19:03 UTC and was resolved at 2026-08-05 03:22 UTC, lasting 8 h 19 min; Fly.io tweaked hosts to allow more machine allocation.

Discord reported a critical API outage affecting direct messages, interactions, shop, and SDK integrations from 2026-08-04 18:49 UTC to 2026-08-04 20:17 UTC, lasting 1 h 27 min. A fix was in place by 19:53 UTC, with nearly all users recovered by 19:59 UTC; the incident was resolved at 20:17 UTC.

OneSignal reported a major incident causing about 3% of Apple push notifications to fail, from 2026-08-04 17:20 UTC to 2026-08-04 19:24 UTC (2 h 4 min). The vendor attributed it to a slight change in how Apple's push notification connections work, applied a mitigation, and confirmed normal operation.