Notable SaaS vendor changes, page 15

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.

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.