Everything SaaS vendor changes, page 10

Postman reported a major outage affecting API Builder flows for US customers, starting 2026-09-10 18:01 UTC and resolved at 2026-09-10 18:26 UTC after 25 min. The team identified a database issue, applied a fix for database resources, and confirmed all scenarios had recovered.

Some customers experienced increased errors from Connect and Passport in a major-impact incident starting 2026-09-10 17:42 UTC and resolved at 2026-09-10 19:16 UTC, lasting 1 h 33 min. v0 reported implementing a fix and confirmed both services fully recovered; no cause was stated.

Vercel reported a major incident causing increased errors for some Connect and Passport customers from 2026-09-10 17:42 UTC to 2026-09-10 19:16 UTC, lasting 1 h 33 min. Vercel identified the issue, implemented a fix, and reported full recovery; no cause was stated.

Claude Cowork on Windows could not run local commands after a September 8 Windows update blocked workspace access to the computer’s drive; chat and file reading/editing still worked for most users. Anthropic rated the incident major, from 2026-09-10 15:54 UTC to 2026-09-14 19:14 UTC (4 days 3 h). Microsoft’s September 14 Windows update fixed it.

Claude Cowork on Windows could not run local commands after a September 8 Windows update blocked workspace access to the computer’s drive; chat and file reading/editing mostly worked. The major incident ran from 2026-09-10 15:54 UTC to 2026-09-14 19:14 UTC (4 days 3 h), resolved by Microsoft’s September 14 Windows update.

Sentry reported a major incident with elevated 500 errors affecting the API, Dashboard and listed US ingestion components from 2026-09-10 15:25 UTC to 2026-09-10 16:26 UTC, lasting 1 h 1 min. Errors appeared during migration to a new control silo region; Sentry rolled back the migration, applied fixes and confirmed full resolution.

Some customers could not log in to the Segment app via SSO, affecting Web Interface (US). Segment marked the incident major; it ran from 2026-09-10 14:28 UTC to 2026-09-10 15:39 UTC, lasting 1 h 11 min. Segment reported mitigation and fully restored SSO login but did not disclose the root cause.

HashiCorp reported a major Linux package verification issue during GPG key rotation: the published fingerprint was outdated and might not match the active signing key. The incident ran from 2026-09-10 13:24 UTC to 2026-09-10 20:40 UTC (7 h 16 min). HashiCorp updated apt/rpm repository keys and documentation, worked on re-signing older-key packages, and reported resolution.

HashiCorp reported a major Linux package-signing degradation: the published GPG fingerprint was outdated and could mismatch the active key, affecting package verification. The incident ran from 2026-09-10 13:24 UTC to 2026-09-10 20:40 UTC (7 h 16 min). HashiCorp updated apt/rpm repository keys and documentation, worked to re-sign older-key packages, and reported resolution.

Brevo reported a critical outage affecting SSO and SAML login, disrupting access for some customers. It started at 2026-09-10 10:29 UTC and was resolved at 2026-09-10 10:50 UTC, lasting 21 min; Brevo confirmed all affected services were functioning normally.

Lambda reported a major incident preventing users from viewing and creating Cloud Service API keys, starting 2026-09-10 07:09 UTC and resolved at 2026-09-10 16:03 UTC, lasting 8 h 54 min. A fix was deployed at 08:36 UTC; existing API keys were unaffected, and no customer action was required.

A major outage blocked Kibana access on Hosted deployments for UI-assigned Organization Owners with Cloud Console, Elasticsearch, and Kibana access. It started at 2026-09-10 01:30 UTC and lasted 21 h 0 min, resolving at 2026-09-10 22:31 UTC. Elastic identified a permissions management UI bug and restored access through a production fix and affected-account data correction.

dbt Labs reported a major degradation in state usage data ingestion across all warehouses, leaving displayed metrics potentially out of date. It started at 2026-09-10 01:19 UTC and was resolved at 2026-09-10 09:14 UTC, lasting 7 h 55 min. A fix was deployed, ingestion fully recovered, and affected data caught up.

Snowflake reported a critical outage in AWS - US East (N. Virginia), starting at 21:26 UTC September 09, 2026, potentially preventing sign-ins, queries, and data management. Snowflake implemented a fix and confirmed restoration at 2026-09-09 23:51 UTC; the recorded duration was 1 h 58 min.

Some Dropbox customers could not access certain Website routes and features during a major-impact outage starting 2026-09-09 21:36 UTC. It lasted 59 min and was resolved at 2026-09-09 22:35 UTC; Dropbox did not state a cause or specific fix.

WorkOS reported a major AuthKit incident affecting form POSTs for roughly 2% of organizations using hosted Authkit custom domains, disrupting sign-in. It started at 2026-09-09 21:00 UTC and was resolved at 2026-09-09 23:02 UTC (reported duration: 2 h 1 min). WorkOS reverted the configuration change responsible and later reported shipping lasting fixes.

RunPod reported a critical network connectivity issue in CA-MTL-4 starting at 2026-09-09 20:56 UTC. It was resolved at 2026-09-09 21:24 UTC after 28 min, with the vendor confirming the data center network was operating normally.

A major incident caused Elastic Agents using Fleet's remote Elasticsearch output to crash-loop or fail enrollment/check-in after configuration updates on Fleet Server 9.5.3 and 9.4.6. It ran from 2026-09-09 20:44 UTC to 2026-09-17 10:30 UTC (7 days 13 h). Corrected releases 9.5.4 / 9.4.6 fixed the issue; all known affected deployments recovered.

1Password reported a major Device Trust disruption affecting the USA/Global Device Trust Authentication Service, with possible device posture check delays or authentication failures. It started at 2026-09-09 20:43 UTC and was resolved at 2026-09-09 21:11 UTC, lasting 27 min. The vendor identified and rolled back the triggering change.

Vanta reported a major incident with GCP Firestore sync operations: syncs for GCP Firebase projects and databases failed, leaving some resource data stale in the Vanta app. It started at 2026-09-09 19:56 UTC and was resolved at 2026-09-10 21:36 UTC, lasting 25 h 39 min; Vanta worked with the GCP team but stated no cause or specific fix.

Buildkite’s major disruption affected Web UI, REST API, Agent API and job queues, causing failed requests, delayed scheduling and artifact-upload issues. Started 2026-09-09 19:07 UTC; resolved 2026-09-10 01:54 UTC (6 h 46 min), with full customer recovery reported since 20:28 UTC. An autoscaling feedback loop overwhelmed the Redis cluster with connections.

Zapier reported a major outage affecting Zap History from 2026-09-09 17:51 UTC to 2026-09-09 19:41 UTC, lasting 1 h 49 min. Recent Zap runs could not be accessed or reviewed, but executions continued normally. Zapier implemented a fix and confirmed runs should be available in Zap History again.

Census reported a critical outage affecting the Census Sync Management UI from 2026-09-09 16:41 UTC to 2026-09-09 17:33 UTC (52 min). A backend change prevented Activation workspaces from loading; rolling it back restored access. Only UI components were impacted; sync runs were unaffected.

Make reported a major degradation in EU1 (eu1.make.com), causing possible instability in scenario executions, webhook processing, and platform access. It started at 2026-09-09 16:11 UTC and was resolved at 2026-09-10 10:29 UTC, lasting 18 h 17 min; operational metrics had returned to healthy levels by 09-09 16:59 UTC.

Some Acuity Scheduling customers saw a "SORRY" error when accessing their Client Scheduling Page; Squarespace rated the incident major. It was marked resolved, with a recorded start of 2026-09-09 15:26 UTC and resolution of 2026-09-08 15:28 UTC; the timestamps conflict, and duration is unknown.

Census reported a major Sync Management UI degradation from 2026-09-08 20:04 UTC to 2026-09-08 22:06 UTC, lasting 2 h 1 min. A recent change blocked some UI jobs, delaying notifications and preventing dataset previews, sync configuration fields, and connection tests from loading for some organizations. A fix was implemented, and the incident was resolved.

Confluent Cloud reported a major connectivity disruption affecting Kafka clusters in AWS us-east-1, starting 2026-09-08 20:01 UTC and resolved 2026-09-09 13:01 UTC (reported duration: 16 h 59 min). A fix was implemented at 09-08 20:30 UTC; connectivity was reported fully operational at resolution.

Miro reported a major outage of username-and-password sign-in starting 2026-09-08 19:21 UTC, lasting 19 h 2 min and resolved at 2026-09-09 14:24 UTC by removing password login. Miro directed customers to passwordless sign-in; SSO and social login were unaffected.

dbt Platform users were logged out of active sessions and temporarily unable to log in during a major incident starting 2026-09-08 18:30 UTC. The incident lasted 4 h 46 min and was resolved at 2026-09-08 23:16 UTC after a fix was deployed to prevent sessions from terminating.

Attio reported intermittent platform availability issues with major impact, starting at 2026-09-08 17:05 UTC and resolved at 2026-09-08 18:42 UTC; the reported duration was 1 h 36 min. The team deployed a fix and monitored the system, but did not state a root cause.

Astronomer reported a major Astro degradation: tasks remained queued on some worker queues because autoscaling resource names exceeding Kubernetes’ 63-character limit were rejected, preventing worker scaling for a very small number of customers. It started at 2026-09-08 12:33 UTC and resolved at 2026-09-08 20:09 UTC, lasting 7 h 35 min; a fix was implemented.

Aircall reported a major incident causing no audio on inbound or outbound calls for some Singapore customers, starting 2026-09-08 05:50 UTC and resolved at 2026-09-08 08:51 UTC; the computed duration was 3 h 0 min. Aircall attributed the issue to a partner and implemented a routing change before confirming resolution.

Otter.ai reported a major incident affecting Otter joining Microsoft Teams meetings for some customers, starting 2026-09-07 22:51 UTC and resolved 2026-09-08 16:55 UTC, lasting 18 h 4 min. Otter deployed a fix and confirmed successful joining was restored.

Cursor reported a major Grok Bot outage from 2026-09-07 20:32 UTC to 2026-09-07 21:37 UTC, lasting 1 h 5 min. Some users could not reach their Grok Bot computers, and Recover or Reset could fail; data was not affected. A fix was implemented, and the incident was resolved.

Ably reported a major outage affecting access to documentation at ably.com/docs from 2026-09-07 11:25 UTC to 2026-09-07 11:32 UTC, lasting 7 min. Realtime services were unaffected; a fix was implemented at 11:28 UTC, and the incident was resolved.

Xero reported a major AU Xero Tax outage from 2026-09-07 01:49 UTC to 2026-09-07 04:16 UTC, lasting 2 h 26 min. An ATO services outage prevented customers from filing tax returns or STP filings, though tax return creation remained available. ATO implemented a fix, and Xero confirmed resolution.

PlanetScale reported a major connectivity outage affecting Vitess databases in GCP from 2026-09-05 18:39 UTC to 2026-09-05 18:53 UTC, lasting 14 min. The vendor identified a networking issue and deployed mitigation, restoring connectivity; it also stated it was making improvements to address root causes and detection.

Lovable reported a major partial outage affecting the Editor for some users, starting at 2026-09-05 18:31 UTC and lasting 27 min. It was resolved at 2026-09-05 18:58 UTC; Lovable stated that the upstream issue was resolved.

Monday.com reported critical connectivity issues affecting AUS - Platform, EU - Platform, Platform, and US - Platform, starting 2026-09-05 08:31 UTC. A fix was implemented at 09-05 09:45 UTC; the incident was resolved at 2026-09-05 10:39 UTC, with a reported duration of 2 h 7 min.

Socket’s public API experienced elevated latency and error rates in a major-impact incident from 2026-09-05 07:21 UTC to 2026-09-05 09:04 UTC, lasting 1 h 43 min. Socket reported implementing a fix at 07:41 UTC and subsequently resolved the incident; no cause was stated.

Perplexity reported a major incident affecting some connectors from 2026-09-05 04:50 UTC to 2026-09-05 07:09 UTC, lasting 2 h 19 min. The issue was mitigated at 06:52 UTC, with impacted connectors monitored for recovery before resolution; no specific cause or fix was stated.

Semgrep reported a major outage starting 2026-09-04 23:13 UTC: an incomplete 1.176.1 patch release prevented PyPI installations from using Pro Engine. It recommended installing 1.175.1 or 1.176.0 temporarily. Resolved at 2026-09-04 23:38 UTC after 24 min, Pro Engine could again be installed and used normally with Semgrep 1.176.1 via PyPI.

GitHub reported a major Copilot code review outage: affected reviews failed to complete or post comments. Tracked from 2026-09-04 20:39 UTC to 2026-09-04 22:26 UTC (1 h 47 min), the final report places failures from 20:04 UTC. An authentication-permissions change blocked review submissions to the GitHub API; reverting it restored service.

GitHub’s major Copilot code review incident ran from 2026-09-04 20:39 UTC to 2026-09-04 22:26 UTC (1 h 47 min). Affected pull request reviews failed to complete or post comments because an authentication-permissions change blocked submissions to the GitHub API; reverting the change restored normal operation.