Everything SaaS vendor changes, page 18

Brex reported a critical incident affecting API requests, starting 2026-08-04 16:01 UTC and resolved at 2026-08-04 20:34 UTC, lasting 4 h 32 min. Brex stated a fix was in place at 08-04 17:50 UTC; no cause was disclosed.

Wasabi reported a major S3 outage in Frankfurt (eu-central-2) from 07:36 UTC to 08:03 UTC on 4 August 2026, caused by a frontend software update; rollback restored service. The record lists start 2026-08-04 14:20 UTC and resolution 2026-08-04 07:30 UTC, conflicting with the update; computed duration is unknown.

Docker reported a major outage: Git pushes to Bitbucket repositories did not trigger automated builds; GitHub repositories were unaffected. The incident ran from 2026-08-04 14:12 UTC to 2026-08-04 16:09 UTC, lasting 1 h 57 min. A fix was deployed at 15:42 UTC, and Bitbucket build triggers were confirmed restored at resolution.

JFrog reported a major incident affecting Artifactory in Azure EU West (Netherlands), with some customers potentially experiencing a brief service interruption. It started and was resolved at 2026-08-04 13:24 UTC, with a computed duration of 0 min; JFrog validated service stability and continued monitoring.

Snyk reported a major incident affecting all Snyk Open Source .NET project workflows, including import, retest, and pull request checks, across AU, EU, GOV, US-01 and US-02 components. It started at 2026-08-04 13:07 UTC and was resolved at 2026-08-04 14:29 UTC, lasting 1 h 21 min; engineers deployed a fix and confirmed recovery.

Socket reported major elevated latency affecting Socket for GitHub, Package Pages, Socket API, Socket Dashboard and Socket Website, starting 2026-08-04 07:42 UTC. A fix was implemented by 2026-08-04 08:33 UTC, and the incident was resolved at 2026-08-04 08:45 UTC after 1 h 3 min.

Lovable reported a critical outage affecting TanStack application previews and published apps; previews could show an internal server error. The incident started at 2026-08-04 00:27 UTC and was resolved at 2026-08-04 01:52 UTC, lasting 1 h 25 min; Lovable reported all systems operating normally.

VoyageAI APIs experienced elevated 5xx errors affecting VoyageAI Embedding and Reranking Models, with major impact, from 2026-08-03 18:47 UTC to 2026-08-03 21:18 UTC (2 h 31 min). A fix was applied at 19:02 UTC, and normal operation was confirmed at resolution.

PandaDoc’s critical live chat outage affected Support chat and US & Global - Support chat, starting 2026-08-03 15:18 UTC and lasting 2 h 36 min. PandaDoc attributed it to an Intercom provider outage and warned support replies could be delayed; live chat was confirmed working and the incident resolved at 2026-08-03 17:55 UTC.

Snowflake’s critical outage affected AWS - US East (Ohio) - Virtual Warehouses, blocking warehouse starts, resumes or management. Reported onset: 13:35 UTC August 03, 2026; tracked start: 2026-08-03 14:11 UTC; resolved: 2026-08-03 20:58 UTC; recorded duration: 6 h 47 min. Snowflake applied an additional fix after a Cloud Services component became unhealthy again.

Netlify reported major elevated build errors affecting the Build Pipeline, with errors beginning at 8:58 UTC and the incident recorded from 2026-08-03 09:31 UTC. A fix was implemented, and the incident was resolved at 2026-08-03 09:55 UTC; the recorded duration was 24 min.

Buildkite reported a major Job Queue degradation starting 2026-08-03 05:11 UTC, resolved at 2026-08-03 05:36 UTC after 25 min. Scheduled builds were delayed, alongside job dispatch, pipeline uploads and incoming webhooks. A fix was fully deployed at 05:29 UTC; Buildkite said affected events would be automatically retried.

Optimizely Analytics (Netspring) experienced a major outage affecting Netspring customers only, starting 2026-08-03 02:30 UTC and resolved at 2026-08-03 16:04 UTC, lasting 13 h 33 min. Optimizely reported identifying the underlying cause without disclosing details and confirmed service was restored to normal operation.

Plaid reported a major disruption affecting new connections to Bank of America, starting 2026-08-02 14:51 UTC and resolved at 2026-08-03 12:53 UTC, lasting 22 h 1 min. Plaid notified Bank of America; no cause or specific fix was stated.

Wix reported a critical outage affecting services including Wix Editor, Sign-In, Checkout, Wix Payments, APIs, Bookings and Dashboard, impacting site management and customer transactions. It started at 2026-08-01 11:27 UTC and was resolved at 2026-08-01 14:44 UTC; no cause or fix was stated.

incident.io reported a major degradation affecting some AI features, with increased error rates starting at 2026-08-01 00:08 UTC. The incident lasted 2 h 37 min and was resolved at 2026-08-01 02:45 UTC, when the vendor reported full recovery.

Temporal Cloud’s Usage API and UI had a critical outage affecting Billing and Global Services - Billing, starting 2026-07-31 22:46 UTC and lasting 2 h 13 min. A fix was implemented at 2026-08-01 00:30 UTC, and the incident was resolved at 2026-08-01 01:00 UTC; no cause was stated.

Canva reported a major incident affecting subscriptions, billing and payments from 2026-07-31 18:55 UTC to 2026-07-31 19:58 UTC, lasting 1 h 3 min. Some users had payment issues; Canva implemented a fix at 19:24 UTC and confirmed resolution at 19:58 UTC.

Optimizely reported a major CMP outage: the Home Page, Plan module, and Requests module failed to load for some customers. It started at 2026-07-31 17:53 UTC and was resolved at 2026-07-31 20:10 UTC, lasting 2 h 17 min. A fix was implemented; no cause was stated.

WorkOS reported a major AuthKit SSO incident causing elevated errors and sign-on redirect loops for a small subset of customers; standalone SSO was unaffected. It started at 2026-07-31 16:12 UTC and resolved at 2026-07-31 18:06 UTC, lasting 1 h 53 min. A fix was deployed at 17:10 UTC.

Some Lovable project builds failed in a major-impact incident starting 2026-07-31 12:24 UTC, lasting 34 min and resolved at 2026-07-31 12:59 UTC. Lovable said its 3rd party provider fixed the issue and that it monitored recovery.

Box reported a major-impact outage affecting Box Shuttle Standalone: users could have trouble accessing, configuring or creating Shuttle job details. It started at 2026-07-31 11:09 UTC and was resolved at 2026-07-31 11:30 UTC, with a computed duration of 20 min. Box reported remediation steps and restored full functionality, without specifying a cause.

ElevenLabs reported a major SIP outage affecting calls to some numbers imported into the Agent Platform, starting 2026-07-31 00:45 UTC and lasting 18 h 15 min. The vendor cited infrastructure resource constraints as a likely contributor; remaining failures affected the US region. Mitigation returned failure rates to baseline, and the incident was resolved at 2026-07-31 19:00 UTC.

Terraform Cloud (HCP) reported a major outage involving degraded performance and inability to load app.terraform.io, starting 2026-07-30 23:06 UTC and resolved 2026-07-31 01:26 UTC, lasting 2 h 20 min. Engineering reported implementing a fix at 07-30 23:47 UTC and monitored until resolution; no cause was stated.

HashiCorp reported a major outage involving degraded performance and inability to load app.terraform.io, starting 2026-07-30 23:06 UTC and lasting 2 h 20 min. Engineering implemented a fix at 07-30 23:47 UTC; the incident was resolved at 2026-07-31 01:26 UTC, with normal operation restored.

Retool Workflows experienced a major degradation: workflows were stuck pending, with increased 429 rate limit responses for start triggers. The incident began at 2026-07-30 20:22 UTC and was resolved at 2026-07-31 05:52 UTC, lasting 9 h 29 min. A fix was deployed at 07-30 21:20 UTC, with workflows still degraded but recovering.

Brex reported a critical degradation starting 2026-07-30 17:04 UTC, with notification delays and possible delays or errors loading the Tasks page or resetting passwords or 2FA. It lasted 1 h 7 min and was resolved at 2026-07-30 18:11 UTC; Brex said all services were operating normally.

Smartsheet reported major slowness and timeouts affecting sheets, premium apps, connectors, and API from 2026-07-30 14:54 UTC to 2026-07-30 17:41 UTC (2 h 47 min). Its postmortem separately described customer impact between approximately 11:00 and 15:57 UTC, attributing failures to a backend service under heavy CPU load during morning traffic ramp-up.

Tinybird reported a major incident affecting replica creation and deletion, including cluster replicas and jobs on-demand (populates and copies). It ran from 2026-07-30 10:40 UTC to 2026-07-30 11:13 UTC, lasting 33 min; Tinybird reported a fix and new replicas being provisioned before confirming resolution.

Aircall reported a major login outage affecting one ISP in GB and one in CH, starting 2026-07-30 08:18 UTC and marked resolved at 2026-07-30 09:52 UTC; the recorded duration was 1 h 33 min. Affected customers were advised to use an alternative network if possible and contact their ISP.

Bolt.new reported a major outage preventing users from saving project files from 2026-07-30 07:29 UTC to 2026-07-30 08:47 UTC, lasting 1 h 18 min. The vendor suggested a possible link to Cloudflare network issues and observed backend improvement coinciding with Cloudflare’s reported resolution before marking the incident resolved.

Docker reported a major Hub degradation starting 2026-07-30 07:19 UTC, resolved 2026-07-31 20:48 UTC after 37 h 29 min. Tags pushed July 29 could be missing from Hub listings but remained pullable; newly added/deleted tags could appear inconsistently, and notifications could repeat during remediation. Docker reported remediation completed and Hub functionality restored.

Claude reported a major incident involving elevated errors across many models, affecting claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork. It started at 2026-07-30 05:57 UTC and was resolved at 2026-07-30 10:48 UTC, lasting 4 h 51 min; partial recovery was followed by renewed errors across all models.

Anthropic reported a major incident with elevated errors across many models affecting claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork. It started at 2026-07-30 05:57 UTC and was resolved at 2026-07-30 10:48 UTC, lasting 4 h 51 min; models partially recovered before errors returned across all models.

Snowflake reported a critical incident preventing some customers in listed AWS and Azure regions from logging in to Snowsight via private endpoints, with HTTP 404 or IP/Token access errors. It started at 2026-07-30 03:00 UTC and was resolved at 2026-07-30 04:56 UTC after reverting a recent configuration change.

Estuary reported a major outage affecting data movement on a single private data plane from 2026-07-29 21:38 UTC to 2026-07-29 22:42 UTC, lasting 1 h 3 min. A Gazette node filled its disk; Estuary added Gazette brokers to spread the load and confirmed affected tasks resumed data movement.

Lambda reported a major network incident in us-east-2 affecting external connectivity to instances, starting 2026-07-29 19:54 UTC and resolved 2026-07-30 18:19 UTC, lasting 22 h 25 min. Engineers reported implementing a fix at 07-29 20:12 UTC and said customer impact should be fixed; networking was confirmed working as expected at resolution.

Claude reported a critical incident involving elevated errors across all models, affecting claude.ai, Claude API (api.anthropic.com), Claude Code, and Claude Cowork. It started at 2026-07-29 19:49 UTC and was resolved at 2026-07-29 22:36 UTC, lasting 2 h 46 min; Claude confirmed recovery in success rates across all models.

Anthropic reported a critical incident involving elevated errors across all models, affecting claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork. The incident started at 2026-07-29 19:49 UTC and was resolved at 2026-07-29 22:36 UTC, lasting 2 h 46 min; Anthropic reported recovery in success rates across all models.

Squarespace reported a major connectivity outage affecting sites and account dashboards, with Accounts & Billing, Acuity Scheduling, Site Editing, and Site Loading listed as affected components. It started at 2026-07-29 18:20 UTC and was resolved at 2026-07-29 19:47 UTC, lasting 1 h 27 min; Squarespace identified the issue and implemented a fix but did not specify the cause.

Grammarly reported a major Go degradation causing delays loading, editing, or saving documents at app.grammarly.com or using Go & agents. It started at 2026-07-29 17:47 UTC and lasted 7 h 22 min, resolving at 2026-07-30 01:09 UTC; a fix was implemented at 07-29 18:04 UTC.

Superhuman Docs experienced a major degradation affecting Docs and Published Docs, with delays loading, editing, or saving documents. It started at 2026-07-29 17:38 UTC and was resolved at 2026-07-29 18:16 UTC; the reported duration was 37 min. A fix was implemented by 07-29 18:05 UTC.

Aiven reported a major Dynamic Disk Sizing (DDS) incident: resize operations could fail for a small subset of newly created nodes. It ran from 2026-07-29 14:29 UTC to 2026-07-29 17:07 UTC, lasting 2 h 37 min. Aiven mitigated all impacted nodes and deployed a fix to prevent recurrence.

Make reported a major EU1 outage: scenarios failed initialization with "Failed to verify account" across all apps, and approximately 200 automatically deactivated scenarios were re-enabled. The incident is marked resolved, but its listed start (2026-07-29 14:23 UTC) is after its resolution (2026-07-22 15:30 UTC); duration is unknown.

Wix reported a major outage affecting Blog Management, View Post, My Sites, Wix Payments, Sign-In, Wix Editor and Wix Studio, starting 2026-07-29 13:31 UTC. A fix was implemented at 13:38 UTC, and the incident was resolved at 2026-07-29 13:47 UTC; the reported duration was 15 min.

HCP Terraform workspace runs failed with IAM errors after an AWS provider upgrade, a major incident from 2026-07-29 12:36 UTC to 2026-07-29 20:44 UTC (8 h 7 min). HashiCorp pulled AWS provider v6.57.0 and published fixed v6.57.1; the interim workaround was pinning to v6.56.0.

HCP Terraform workspace runs failed with IAM errors after an AWS provider upgrade in a major incident starting 2026-07-29 12:36 UTC, lasting 8 h 7 min and resolved at 2026-07-29 20:44 UTC. HashiCorp pulled AWS provider v6.57.0 and published fixed v6.57.1; the interim workaround was pinning to v6.56.0.

Pipedream reported a critical incident affecting Connect API and HTTP event sources and workflows, starting at 2026-07-28 23:40 UTC. A fix was implemented by 2026-07-28 23:53 UTC, and the incident was resolved at 2026-07-28 23:59 UTC; the reported duration was 18 min.

Some Lovable users experienced errors when using chat in an incident rated major. It started at 2026-07-28 07:07 UTC and was resolved at 2026-07-28 07:24 UTC, lasting 17 min; no cause or specific fix was stated.