Notable SaaS vendor changes, page 12

Box reported a major-impact incident affecting access to Box Hubs through shared links, starting 2026-08-28 08:20 UTC and resolved at 2026-08-28 10:00 UTC (1 h 40 min). Box said it identified the underlying cause and restored full functionality, but the evidence does not specify the cause or fix.

Mailgun reported a critical EU datacenter messaging outage affecting API, SMTP, inbound processing, outbound delivery, events and logs, analytics, and the control panel. It started at 2026-08-27 20:38 UTC and resolved at 2026-08-27 21:16 UTC, lasting 37 min. Mailgun implemented a fix but did not specify the cause.

Cursor reported a critical sign-in service degradation affecting cursor.com and IDE from 2026-08-27 19:31 UTC to 2026-08-27 19:38 UTC, lasting 7 min. A fix was implemented at 19:35 UTC, and Cursor confirmed sign-in had returned to normal at resolution.

Snowflake reported a major outage affecting private connectivity, including PrivateLink, in Azure - Australia East (New South Wales), Azure - Central India (Pune), and Azure - Central US (Iowa), causing connection errors or timeouts. It ran from 2026-08-27 19:05 UTC to 2026-08-27 20:26 UTC (1 h 20 min); Snowflake implemented a fix and confirmed service restoration.

Some Serverless customers’ .apm endpoints were unavailable after a Managed Inputs change removed internal DNS rules. The major incident was recorded from 2026-08-27 17:11 UTC to 2026-08-27 18:33 UTC (1 h 22 min), resolved. The update instead described disruption within a 9 hour window on August 26, with service restored around 9AM UTC that day.

Gorgias reported a major incident causing ticket, order and product searches to show outdated results in the Helpdesk Web App and us-east1-c94b. It started at 2026-08-27 16:22 UTC and was resolved at 2026-08-27 17:02 UTC, with a computed duration of 39 min; a fix was implemented at 16:43 UTC.

Omni Analytics reported a critical incident affecting Ireland: server timeouts caused 500 errors on EU instances. It started at 2026-08-27 14:52 UTC and was resolved at 2026-08-27 15:47 UTC, lasting 55 min; the vendor reported that one model service spiked and began recovering.

Smartsheet reported a critical outage affecting login, sheet access, Control Center, Dynamic View and other premium apps, disrupting access to customer work. It started at 2026-08-27 13:33 UTC and resolved at 2026-08-27 15:53 UTC, lasting 2 h 19 min; a fix was implemented at 08-27 13:52 UTC.

Opsgenie reported a major Microsoft Teams notification outage for standalone customers, starting 2026-08-27 10:26 UTC and resolved 2026-09-03 06:06 UTC (6 days 19 h); Jira Service Management Operations was unaffected. An external partner’s operational error caused the issue; partner corrective measures restored service, though customers still affected were directed to restore their integration.

GitHub reported a critical degradation affecting Kimi K3 in Copilot products and IDE surfaces, with elevated error rates; no other models were impacted. The incident record started at 2026-08-27 10:04 UTC and resolved at 2026-08-27 12:12 UTC, lasting 2 h 8 min. GitHub attributed it to an upstream provider issue, resolved through the provider’s mitigation.

GitHub reported a critical degradation affecting Kimi K3 in Copilot products and IDE surfaces, with elevated error rates; no other models were impacted. The incident started at 2026-08-27 10:04 UTC and was resolved at 2026-08-27 12:12 UTC, lasting 2 h 8 min. GitHub attributed it to an upstream provider issue, resolved through the provider’s mitigation.

Sentry reported a major outage affecting product and API availability, with the Dashboard and US ingestion components listed as affected. It started at 2026-08-27 09:24 UTC and was resolved at 2026-08-27 15:41 UTC, lasting 6 h 17 min; latency returned to normal.

A critical outage made Confluence, Jira Cloud and Jira Service Management unavailable to affected users in Western Europe and Southeast APAC. The incident ran from 2026-08-27 04:22 UTC to 2026-08-27 05:16 UTC (53 min); Atlassian rolled out a fix and confirmed recovery. The postmortem attributed the disruption to a defective routing-layer code change in a proxy fleet.

A critical outage made Jira Cloud, Jira Service Management and Confluence unavailable to affected users in Western Europe and Southeast APAC. The incident ran from 2026-08-27 04:22 UTC to 2026-08-27 05:16 UTC (53 min); Atlassian rolled out a fix, and its postmortem attributed the disruption to a defective proxy routing-layer code change.

Klaviyo reported a major degradation starting 2026-08-27 00:09 UTC: some profiles stalled at flow time delays, affecting email, text messaging, push, and WhatsApp sending. Campaigns and flows without time delays were unaffected. A fix was deployed and affected-message processing completed; the incident resolved at 2026-08-27 03:42 UTC after 3 h 33 min.

Some Buffer customers could not log in because email verification codes failed to arrive or were rejected. The vendor-rated major outage started at 2026-08-26 23:29 UTC and was resolved at 2026-08-27 03:48 UTC, lasting 4 h 18 min. Buffer applied a fix restoring verification email delivery and working codes.

Apollo GraphQL reported a major incident starting 2026-08-26 22:12 UTC: user invites, user permission changes and OAuth changes intermittently failed because rate limits were incorrectly applied. It lasted 1 h 24 min and was resolved at 2026-08-26 23:36 UTC after a fix was deployed to ensure rate limits work as expected.

Mixpanel reported a major Query API degradation causing HTTP 500 errors and report-loading failures for US Data Residency projects; EU and IN projects were unaffected. It started at 2026-08-26 21:39 UTC and resolved at 2026-08-26 22:45 UTC, lasting 1 h 6 min; a fix was implemented, and no customer data was lost.

Dremio Cloud (US) reported a major outage preventing some classic engines from starting or scaling, from 2026-08-26 21:25 UTC to 2026-08-26 21:55 UTC (30 min). A provisioning artifact was inadvertently removed during a compliance-related infrastructure change; running engines were unaffected. A fix was applied and normal operations confirmed.

Critical Actions and Pages degradation lasted 2 h 49 min, from 2026-08-26 15:11 UTC to 2026-08-26 18:01 UTC. Actions jobs failed to start, then experienced delays exceeding five minutes; Pages performance degraded. Saturated database-primary writes triggered the disruption; failover did not fully restore service. Queues recovered, but 3.7% of early larger-runner jobs remained stuck pending cancellation.

GitHub reported critical Actions and Pages degradation from 2026-08-26 15:11 UTC to 2026-08-26 18:01 UTC (2 h 49 min). Actions jobs failed to start or were delayed; Pages performance degraded. Workflow-trigger database write saturation caused the impact; failover did not fully restore service. At recovery, 3.7% of early larger-runner jobs remained stuck, awaiting cancellation.

Otter.ai reported a major incident delaying Summary and Speaker tagging and also impacting Otter Chat. It started at 2026-08-26 13:46 UTC and lasted 31 h 38 min, resolving at 2026-08-27 21:24 UTC when Otter said its systems were fully restored.

Drata’s major US Public API degradation caused request failures and potentially incorrect framework/control readiness data from 2026-08-26 13:32 UTC to 2026-08-28 23:58 UTC (2 days 10 h). No data was lost; EU and APAC were initially unaffected. Drata deployed fixes and reported normal operation at resolution, with no customer action required.

Smartsheet reported a critical US incident affecting sheet loading, Reports, Dashboards, and premium apps including Dynamic View, WorkApps, Resource Management, and Control Center. It started at 2026-08-26 13:28 UTC and resolved at 2026-08-26 18:23 UTC, lasting 4 h 55 min. Smartsheet implemented a fix and monitored recovery.

Facebook (Meta) syncs failed with “API access disrupted” in a major incident affecting Census Sync Management UI and Sync Engine from 2026-08-26 13:09 UTC to 2026-08-26 14:11 UTC (1 h 2 min). Census identified an Activations Meta app issue and implemented a fix; all affected syncs will recover on their next triggered or scheduled run.

Figma reported a major MCP disruption preventing some Codex and ChatGPT users from seeing tools such as use_figma. The incident started at 2026-08-26 12:08 UTC and resolved at 2026-08-26 16:19 UTC (computed duration: 4 h 10 min); Figma stated impact began at 10:14 UTC and recovery began at 14:03 UTC.

Vercel CLI login (vc login) experienced errors in a major-impact incident from 2026-08-26 03:06 UTC to 2026-08-26 04:28 UTC, lasting 1 h 22 min. The vendor reported identifying the source and testing a fix before marking the incident resolved; affected customers had trouble logging in through the CLI.

Vercel reported a major incident causing login errors with Vercel CLI (`vc login`), preventing affected customers from signing in. It started at 2026-08-26 03:06 UTC and was resolved at 2026-08-26 04:28 UTC, lasting 1 h 22 min. The team reported identifying the source and testing a fix but did not specify the cause.

Buildkite reported a major site-wide outage starting 2026-08-25 22:55 UTC, resolved 2026-08-26 00:18 UTC (1 h 22 min). Internal DNS failure blocked new builds and delayed job dispatch; web, APIs and notifications were affected. Mitigations restored service; no build requests were lost. The postmortem places customer disruption at 22:47 UTC to 23:16 UTC.

Semgrep reported a critical incident affecting Dashboard and Scans and CI/CD, starting 2026-08-25 19:21 UTC and lasting 2 h 40 min. A bad release caused widespread platform failures; rollback restored stability, and a successful release fully resolved the issue at 2026-08-25 22:01 UTC.

WorkOS reported a major Dashboard sign-in outage that could prevent users from authenticating, starting 2026-08-25 17:35 UTC and resolved at 2026-08-25 18:41 UTC, with a computed duration of 1 h 5 min. A fix was applied at 17:41 UTC and confirmed to have resolved elevated sign-in errors at 17:54 UTC.

Anaconda reported a major backend outage affecting APIs, authentication, repositories, EduBlocks and Pyscript, involving an inability to spawn new compute nodes. The recorded start was 2026-08-25 17:10 UTC, though reported impacts began at 15:45 UTC. A fix was implemented; resolution was recorded at 2026-08-25 18:52 UTC, with a computed duration of 1 h 41 min.

Cloudsmith reported a major incident affecting metadata requests and package downloads, starting 2026-08-25 16:38 UTC and lasting 1 h 30 min. Customers experienced latency and timeouts between 16:04 and 17:13 UTC, with a recurrence between 18:48 and 19:08 UTC; Cloudsmith confirmed normal operations at 08-26 07:55 UTC.

Pinecone reported a major incident affecting Serverless Indexes in GCP us-central1, with 5xx errors on some read and write requests. It started at 2026-08-25 15:50 UTC and was resolved at 2026-08-25 16:11 UTC, lasting 21 min; Pinecone stated that a fix was implemented.

Confluence reported a major incident delaying email, mobile and slack notifications for Jira, JSM and Confluence, starting 2026-08-25 08:42 UTC and resolved at 2026-08-25 14:33 UTC, lasting 5 h 51 min. Teams applied corrective measures in one impacted region; the vendor confirmed normal service for all customers without specifying a cause.

Jira reported a major degradation delaying email, mobile and slack notifications for Jira, JSM and Confluence from 2026-08-25 08:42 UTC to 2026-08-25 14:33 UTC, lasting 5 h 51 min. Teams applied corrective measures in an impacted region; the vendor confirmed resolution and normal service for all customers.

BigCommerce reported a major Control Panel incident affecting Microsoft Azure AD Single Sign-On login for a subset of stores. It started at 2026-08-25 06:56 UTC and was resolved at 2026-08-25 07:25 UTC, lasting 29 min; BigCommerce identified the issue and reported implementing a fix before resolution.

Box reported a critical download issue affecting Box Zones users in the Asian region, who may have been unable to download files. It started at 2026-08-25 06:53 UTC and was resolved at 2026-08-25 07:37 UTC, lasting 44 min; Box reported improvement after remediation steps, and its postmortem also noted ZIP downloads were affected.

Confluent reported a major Confluent Cloud degradation in Azure Southeast Asia, with elevated errors, latency and intermittent connectivity affecting produce/consume availability. Recorded from 2026-08-25 04:17 UTC to 2026-08-25 07:29 UTC (3 h 11 min), it reportedly began around 03:13 UTC and was associated with a Microsoft Azure disruption; services returned to normal.

Snowflake reported a critical outage in Azure - Southeast Asia (Singapore), where infrastructure connectivity issues may have prevented customers from accessing services. It started at 2026-08-25 03:53 UTC and was resolved at 2026-08-25 04:35 UTC, lasting 41 min; Snowflake implemented a fix and confirmed restoration through monitoring. Other regions were unaffected.

Box reported a major-impact upload incident starting 2026-08-24 21:21 UTC, resolved at 2026-08-24 22:03 UTC (41 min). Users could encounter upload errors or slowness across the Box web application and API; the postmortem also noted affected write operations. Box reported remediation and improvement but did not specify the cause or fix in the available evidence.

Descript reported a major Share Page outage with a recorded start of 2026-08-24 18:56 UTC and resolution of 2026-08-24 17:15 UTC; duration is unknown. The vendor said a fix had been implemented and the issue was resolved.

DigitalOcean reported a critical Cloud Control Panel/Public API outage starting 2026-08-24 17:14 UTC, resolved 2026-08-25 19:04 UTC (25 h 49 min). Customers faced API errors and panel access failures; mitigation restored access. The postmortem reports 3.5 hours of active degradation, peaking at 25% errors; running Droplets, network routing and Volumes remained functional.