Notable SaaS vendor changes, page 18

Render reported a critical disruption affecting Oregon Web Services, with some services unreachable or experiencing failed requests. The incident started at 2026-07-24 11:16 UTC and was resolved at 2026-07-24 13:30 UTC, lasting 2 h 14 min. Render observed recovery across all services at 11:27 UTC and said it believed an upstream provider caused the issue.

Matillion reported a major outage involving S3 Load/Unload or Azure Blob Storage Load/Unload COPY failures, affecting Pipeline Execution in AU, EU and US regions. It started at 2026-07-24 08:02 UTC and was resolved at 2026-07-24 15:13 UTC, lasting 7 h 10 min; Matillion reported identifying the issue and implementing a fix.

Xero reported a major global incident affecting Xero Platform and Settings: some customers encountered slowness, errors and unavailable features when accessing or using Xero. It ran from 2026-07-24 01:59 UTC to 2026-07-24 03:02 UTC (1 h 3 min). Xero attributed the issue to a product release and restored service through a rollback.

Cohere reported a major Dashboard login outage: a continuous refresh loop prevented authentication. The incident ran from 2026-07-23 22:56 UTC to 2026-07-23 23:46 UTC (50 min); Cohere implemented a fix and confirmed resolution. API access, model inference, and all other Cohere services were unaffected.

Retool reported a critical Email Server outage from 2026-07-23 22:22 UTC to 2026-07-24 18:34 UTC, lasting 20 h 12 min. Some Retool Emails failed with “Disabled for sending spam” due to an upstream email provider issue; official user invites and password resets were unaffected. Retool restored the sending domain and normal delivery, and added safeguards against recurrence.

Vercel reported major telemetry delivery loss for Drains, recorded as starting and resolving at 2026-07-23 19:00 UTC (computed duration: 0 min). Its update identifies the affected window as 19:12–19:18 UTC: traces and events are unrecoverable, while logs remain accessible and exportable in the Logs UI dashboard. A fix was deployed; additional monitoring is being added.

v0 resolved a major Drains incident, recorded as starting 2026-07-23 19:00 UTC with a computed duration of 0 min. Its update reports unrecoverable traces and events between 19:12 and 19:18 UTC on July 23, 2026; undelivered logs remain accessible and exportable in the Logs UI dashboard. A fix was deployed.

Perplexity reported critical Computer sandbox issues starting at 2026-07-23 17:48 UTC, lasting 25 min and resolved at 2026-07-23 18:14 UTC. The vendor identified the problem and rolled back the impacted services; no specific cause was stated.

MongoDB Atlas reported a major outage affecting some Azure westus clusters: intermittent connection failures, inter-node communication issues, nodes appearing down, and delayed cluster modifications. It started 2026-07-23 16:21 UTC and resolved 2026-07-23 20:28 UTC (4 h 6 min); Azure confirmed networking issues, and recovery completed after Azure rolled out mitigation.

Optimizely reported a major outage in which login returned 429 errors, affecting access to some products through Optimizely Identity. It started at 2026-07-23 15:26 UTC and was resolved at 2026-07-23 18:41 UTC, lasting 3 h 15 min; Optimizely attributed it to a disruption with its identity provider, Okta.

A critical JFrog Cloud Platform outage affected a subset of customers using Artifactory and Security - Xray in Azure US West (California), from 2026-07-23 15:04 UTC to 2026-07-23 20:32 UTC, lasting 5 h 27 min. JFrog reported several Azure backend service outages, implemented a fix, and marked the incident resolved.

Inngest reported major function-processing delays starting 2026-07-23 14:17 UTC, resolved at 2026-07-23 15:24 UTC (1 h 6 min); delays began around 14:03 UTC. An issue publishing to a new Kafka topic delayed function scheduling; the team isolated the topic and scaled consuming services to clear the backlog. No events were dropped.

Box Hubs users were unable to load the Hubs gallery; the vendor recorded major impact. The incident started at 2026-07-23 14:14 UTC and was resolved at 2026-07-23 14:30 UTC, with a computed duration of 15 min. Box reported identifying the underlying cause without specifying it and confirmed full functionality was restored.

Box reported major impact to File Request, with users potentially experiencing delayed metadata updates when uploading files. The incident started 2026-07-23 09:45 UTC and was resolved 2026-07-23 11:42 UTC, lasting 1 h 56 min; Box confirmed full functionality was restored.

Vercel reported a major incident causing Dashboard chart and observability-data loading timeouts for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. It lasted 45 min, from 2026-07-23 07:33 UTC to 2026-07-23 08:18 UTC. Vercel identified the source and implemented a fix, with recovery reported at 07-23 07:55 UTC.

v0 reported a major incident causing Dashboard chart and observability-data timeouts for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. It started at 2026-07-23 07:33 UTC and was resolved at 2026-07-23 08:18 UTC, lasting 45 min. The team identified the source and implemented a fix, but did not specify the cause.

v0 reported a critical incident involving dashboard authentication errors that made the dashboard inaccessible for some users. It started at 2026-07-23 06:47 UTC and lasted 54 min, resolving at 2026-07-23 07:41 UTC; a fix was implemented by 2026-07-23 07:08 UTC.

Vercel reported a critical dashboard authentication incident that made the dashboard inaccessible for some users starting at 2026-07-23 06:47 UTC. A fix was implemented by 2026-07-23 07:08 UTC, and the incident was resolved at 2026-07-23 07:41 UTC after 54 min.

Descript reported a critical incident in which Video Regenerate failed for some users, starting at 2026-07-23 00:20 UTC and resolved at 2026-07-23 02:47 UTC, lasting 2 h 26 min. Functionality was fully restored by 02:39 UTC; no cause or specific fix was stated.

Discord reported a major incident preventing voice connections from 2026-07-22 23:32 UTC to 2026-07-22 23:57 UTC, lasting 25 min. A fix was implemented by 07-22 23:49 UTC, and the incident was resolved.

1Password reported a major SaaS Manager outage in USA/Global starting 2026-07-22 17:55 UTC, resolved at 2026-07-22 19:20 UTC after 1 h 25 min. SaaS Manager could not communicate with Managed Credentials, potentially preventing Better Together customers from changing credential ownership. A fix was deployed.

Codecov Backend upload processing was severely delayed in a major-impact incident starting 2026-07-22 15:02 UTC and resolved at 2026-07-22 21:00 UTC, lasting 5 h 57 min. Codecov implemented a fix and reported the task backlog clearing, with affected users beginning to receive notifications.

Sanity reported a major incident affecting api.sanity.io and Studio, with some users stuck on "Trying to connect" or unable to load Studio. It started at 2026-07-22 12:38 UTC and lasted 5 h 27 min, resolving at 2026-07-22 18:05 UTC; after a recurrence affecting additional services, Sanity implemented a fix.

Gorgias reported a major outage that made some e-commerce data unavailable after a database became temporarily unavailable. The incident started at 2026-07-22 12:35 UTC and was resolved at 2026-07-22 13:13 UTC, lasting 37 min. Gorgias said a transient network issue was resolved, all queued requests were processed, and all services were operational.

CDC ClickPipes became stuck in maintenance during a weekly upgrade, initially in eu-central-1, with services in other regions also affected. ClickHouse Cloud rated the incident major; it ran from 2026-07-22 11:53 UTC to 2026-07-22 14:36 UTC, lasting 2 h 42 min. Services recovered, but the upgrade rollout remained on hold pending confirmation it could avoid the underlying pod networking failure mode.

Dekaf materializations stalled on public AWS us-east-1 and GCP us-central1 data planes in a major incident from 2026-07-22 11:19 UTC to 2026-07-22 18:06 UTC, lasting 6 h 46 min. All other tasks and data planes were unaffected. Estuary deployed a fix and resolved the incident; no customer action was required.

Snyk reported major Open Source and Container degradation on SNYK-US-01 (app.snyk.io), starting 2026-07-22 09:41 UTC and resolved after 21 h 28 min. Customers may have experienced import errors and Project details issues from 09:08 to 09:30 UTC; corrective actions restored operations. No further impact was observed during monitoring; customers should re-import failed imports.

Prefect Cloud (US) experienced a critical incident affecting API requests, UI, and orchestration, with delayed flow run scheduling, automations, and event processing. It started at 2026-07-22 09:31 UTC and was resolved at 2026-07-22 09:58 UTC, lasting 26 min. Prefect reported resolving an underlying database issue; all services, including background processing, returned to normal.

Wix reported a major outage affecting My Sites, Sign-In, Site Dashboard, and site editing through Wix Editor and Wix Studio, disrupting access and editing. It started at 2026-07-22 08:36 UTC and was resolved at 2026-07-22 08:48 UTC; the computed duration was 11 min. Wix implemented a fix but did not state the cause.

Docker Hub experienced intermittent timeouts on hub.docker.com, with major impact, from 2026-07-22 05:34 UTC to 2026-07-22 08:00 UTC, lasting 2 h 26 min. Docker implemented a fix, then investigated incomplete recovery before confirming normal operations.

WorkOS reported a major incident involving SSO failures for AuthKit customers, starting at 2026-07-21 21:21 UTC and resolved at 2026-07-21 21:54 UTC, lasting 32 min. WorkOS said it identified and fixed the issue and AuthKit SSO fully recovered; no cause was stated.

Klaviyo reported a major incident affecting SMS subscriptions, delaying SMS sends, and causing errors creating or scheduling SMS and WhatsApp campaigns. It started at 2026-07-21 20:36 UTC and was resolved at 2026-07-21 21:09 UTC, lasting 32 min. Klaviyo implemented a fix but did not disclose the cause.

Pinecone reported a critical incident causing 5xx errors for some Serverless namespaces in Azure eastus2. It started at 2026-07-21 19:10 UTC and was resolved at 2026-07-21 19:40 UTC, with a reported duration of 29 min; Pinecone identified the issue and implemented a fix but did not specify the cause.

SquadCast recordings intermittently failed in a major-impact incident starting 2026-07-21 19:01 UTC and lasting 39 min, resolved at 2026-07-21 19:40 UTC. Descript reported functionality fully restored at 2026-07-21 19:14 UTC but did not state a cause or specific fix.

OpenAI reported a major outage affecting ChatGPT and API Platform logins and account creation, plus API Platform organization management and dashboard access. It started at 2026-07-21 18:36 UTC and was resolved at 2026-07-21 19:00 UTC, lasting 23 min; the final update confirmed full recovery of affected API Platform functionality.

A major outage affected logins and account creation for ChatGPT and the API Platform, plus API Platform organization management and dashboard access; users already signed in may still have been able to use ChatGPT. It started at 2026-07-21 18:36 UTC and was resolved at 2026-07-21 19:00 UTC (23 min), with all affected API Platform functionality fully recovered.

API image generation requests experienced elevated error rates in a major-impact incident from 2026-07-21 18:10 UTC to 2026-07-21 22:19 UTC, lasting 4 h 9 min. OpenAI applied mitigations and confirmed full recovery, with error rates back to normal.

API image generation requests experienced elevated error rates in a major-impact incident from 2026-07-21 18:10 UTC to 2026-07-21 22:19 UTC, lasting 4 h 9 min. OpenAI applied mitigations and confirmed full recovery, with error rates back to normal.

Attio reported a major workflow-triggering incident starting 2026-07-21 17:35 UTC, resolved after 47 h 53 min. Some workflows failed between 16:33 and 18:01 UTC on July 21, 2026, because an infrastructure configuration change caused encryption errors. Attio reverted the change, corrected the configuration, and notified impacted customers.

Elastic Cloud reported a major Instance Capacity metering issue affecting a small number of Hosted Deployments customers, starting 2026-07-21 14:24 UTC and lasting 32 h 50 min. Resolved at 2026-07-22 23:14 UTC, all metering errors were corrected, and Elastic said it would issue refunds to affected customers.

Elastic Cloud reported major AutoOps degradation: a subset of Elastic Agents could not report metrics across all regions during Jul 18 02:40 UTC–Jul 20 14:00 UTC, leaving monitoring gaps. The issue was corrected and data resumed normally. Posted retroactively, the resolved incident record started 2026-07-21 13:45 UTC, with a computed duration of 35 min.

Matillion reported a critical Hub outage preventing projects from loading within Maia Foundation, starting 2026-07-21 11:39 UTC. The incident lasted 1 h 17 min and was resolved at 2026-07-21 12:56 UTC after a fix was implemented; no cause was stated.

ChatGPT image generation was unavailable with elevated errors in an incident rated major, starting 2026-07-21 10:36 UTC and lasting 6 days 8 h. OpenAI reported applying a mitigation and monitoring recovery; the final resolution at 2026-07-27 19:04 UTC stated that all impacted services had fully recovered.

ChatGPT image generation was unavailable with elevated errors in a major-impact incident starting 2026-07-21 10:36 UTC and resolved at 2026-07-27 19:04 UTC (recorded duration: 6 days 8 h). OpenAI applied a mitigation and reported recovery, followed by renewed errors before final recovery.

Elastic Cloud reported a major incident causing delayed or failed email MFA code delivery for Gmail users, starting 2026-07-21 09:36 UTC and resolved 2026-07-23 16:37 UTC (2 days 7 h). Delays were mitigated on 07-21 23:10 UTC; customers could use registered TOTP/WebAuthn factors or “Log in with Google” as workarounds.

dbt Labs reported a critical outage from 2026-07-21 07:45 UTC to 2026-07-21 12:52 UTC (5 h 7 min). Scheduled, CI, and API-triggered GitHub job runs failed at “Clone git repository” across all regions (multi-tenant and single-tenant) because of upstream GitHub SSH deploy key authentication failures. GitHub resolved the issue; failed runs can be retried.

Heap reported a major Heap Connect incident affecting some US Connect customers with delays in data lake ingestion. It started at 2026-07-21 06:34 UTC and was resolved at 2026-07-21 09:06 UTC, lasting 2 h 31 min; Heap identified the issue and implemented a fix, but did not state a cause.

Sentry reported a critical EU-region incident causing high ingestion latency for errors, attachments, and feedback from 2026-07-20 11:11 UTC to 2026-07-20 16:57 UTC, lasting 5 h 46 min. Sentry implemented an attachment ingestion fix and cleared attachment and error backlogs; latency returned to normal across all event types.