Notable SaaS vendor changes
Every change Rewindex detected on vendor pricing, trust and legal pages and status pages, newest first. Click one to see exactly what changed.
| When (UTC) | Company | Change | Kind |
|---|---|---|---|
| Qdrant | Incident silently edited: Cluster metrics unavailable in AWS us-east-1 Qdrant corrected the incident title from “luster metrics unavailable in AWS us-east-1” to “Cluster metrics unavailable in AWS us-east-1.” This is a wording-only correction; no impact, timing, cause or fix details changed in the supplied diff. | Silent edit | |
| Anthropic | Pricing page changed: feature moved The pricing page removed “Claude Code included” labels from Pro and Max and added “Code” after “Claude” in a feature list. These are presentation changes; the diff does not establish that Claude Code access changed for either plan. | PricingFeature moved between plans | |
| Klaviyo | Major incident: Flow Sending Delays Klaviyo reported a major degradation in flow message sending starting 2026-10-17 17:01 UTC, with some customers’ flow emails delayed; immediate sends remained unaffected. The incident was still open when archived, after 1 h 4 min at the last update. Klaviyo said it had identified the cause and was working on a fix, without specifying either. | Major incident | |
| 1Password | Major incident: High error rate on 1Password.com A major high-error-rate incident on 1Password.com affected USA/Global access to passwords and other items, Admin console, Sign in, and syncing between devices starting 2026-10-16 23:45 UTC. A fix was deployed at 10-17 03:13 UTC; the incident remained open under monitoring when archived, open for 3 h 27 min at the last update. | Major incident | |
| Greenhouse | Major incident: Onboarding UKG Pro Issues Greenhouse reported a major HRIS Link UKG Pro Onboarding Integration incident: some customers’ new hires could fail to sync to UKG. It ran from 2026-10-16 22:44 UTC to 2026-10-17 04:24 UTC (5 h 40 min). Greenhouse implemented a fix and said it was restoring affected connections and would resend pending hires; no customer action was needed. | Major incident | |
| Cloudinary | Major incident: Issues accessing the Cloudinary web UI Cloudinary’s major web UI outage prevented some users from logging in or using the Console and Media Library. It started at 2026-10-16 20:06 UTC and was resolved at 2026-10-16 21:53 UTC, lasting 1 h 46 min; a fix was implemented at 21:08 UTC. Image/video delivery, uploads and API requests using API credentials were unaffected. | Major incident | |
| Fly.io | Major incident: Fly-metrics.net Grafana Dashboard Outage Fly.io reported a major outage of the fly-metrics.net hosted Grafana and log search instance starting 2026-10-16 18:08 UTC, resolved at 2026-10-16 19:24 UTC (1 h 15 min). The vendor attributed unavailability to host maintenance; logs and metrics shipped to other sources via Fly Telemetry or the Fly Log shipper remained available. | Major incident | |
| Cloudflare | Major incident: Cloudflare Fedramp Dashboard and Access Cloudflare reported a major outage affecting logins to the Fedramp Dashboard and applications protected by Fedramp Access from 2026-10-16 17:56 UTC to 2026-10-16 19:09 UTC, lasting 1 h 12 min. Cached CDN files and other Edge security features were unaffected. Cloudflare implemented a fix and resolved the incident. | Major incident | |
| Fly.io | Major incident: Platform Wide Rolling Host Reboots Fly.io’s major fleet-wide host reboots mitigated PwnEscape (Linux Kernel CVE-2026-99999), making Machines, volumes and MPG instances unavailable for 15–20 minutes per host. The incident ran from 2026-10-16 16:22 UTC to 2026-10-17 05:15 UTC (12 h 52 min); it was resolved, though a small number of hosts remained degraded or offline. | Major incident | |
| Zapier | Major incident: Errors publishing Zaps from Guided Templates with app approvals enabled Zapier reported a major outage preventing users with app approvals enabled from publishing Zaps through Guided Templates, though drafts could be created. It started at 2026-10-16 14:10 UTC and was resolved at 2026-10-16 15:23 UTC, lasting 1 h 12 min. A deployed, verified fix restored Request to publish in the Guided Template flow; approval requirements remain unchanged. | Major incident | |
| Expo | Major incident: Elevated iOS submission error rates Expo reported a major incident affecting EAS Submit and Apple Developer APIs, with increased App Store Connect API "500 Internal Server Error" responses causing elevated iOS submission error rates. It started at 2026-10-16 14:07 UTC and was resolved at 2026-10-16 16:44 UTC, lasting 2 h 37 min; no specific fix was stated. | Major incident | |
| Pulumi | Major incident: Bitbucket login is not available Pulumi reported a major Bitbucket login outage affecting API and Console, with failures beginning approximately 2026-10-15 16:51 UTC. The recorded incident ran from 2026-10-16 10:48 UTC to 2026-10-16 13:30 UTC (2 h 42 min); a fix was deployed, and other login methods, Bitbucket repository integrations and deployments were unaffected. | Major incident | |
| Socket | Critical incident: Delayed creation and updates for ticketing integrations Socket reported a critical ticketing integration degradation delaying ticket creation, updates and closure from 2026-10-16 07:28 UTC to 2026-10-16 09:19 UTC, lasting 1 h 50 min. Live functionality was restored, missed events were replayed, and the ticketing service returned to normal operations. | Major incident | |
| Snowflake | Critical incident: INC20000287 Snowflake reported a critical incident in GCP - Middle East (Dammam) affecting query processing and Snowsight, with intermittent delays and query failures. It started at 2026-10-16 01:14 UTC and was resolved at 2026-10-16 01:43 UTC, lasting 29 min. Snowflake attributed the disruption to elevated infrastructure load, which subsided before service restoration was confirmed. | Major incident | |
| Cloudflare | Major incident: Network Performance Issues in Eastern North America Cloudflare reported a major network performance incident affecting Ashburn (IAD) and Newark (EWR), with elevated latency and/or errors for traffic handled there. It started at 2026-10-15 20:48 UTC and was resolved at 2026-10-15 21:38 UTC; the computed duration was 49 min. Cloudflare reported no customer impact by 2026-10-15 21:24 UTC. | Major incident | |
| Rippling | Major incident: Products partially degraded Rippling reported major degradation affecting the Rippling App, with higher-than-usual error rates across products starting 2026-10-15 19:07 UTC. The vendor identified the impacted subsystem and reported mitigation and full recovery at 2026-10-15 20:08 UTC; the incident was resolved at 2026-10-15 20:55 UTC, lasting 1 h 47 min. | Major incident | |
| Cloudflare | Major incident: Network Performance Issues in London Cloudflare reported major network performance issues in London, United Kingdom (LHR), affecting Durable Objects, R2 and RealtimeKit. The incident started at 2026-10-15 17:33 UTC and was resolved at 2026-10-15 17:46 UTC, lasting 13 min; Cloudflare said it identified the issue and was implementing a fix. | Major incident | |
| WorkOS | Major incident: Radar SMS challenge failures for phone numbers in mainland China (+86) WorkOS reported a major Radar SMS challenge outage for mainland China (+86), preventing affected users from receiving codes or completing verification. It started at 2026-10-15 17:17 UTC and was resolved at 2026-10-15 21:51 UTC, lasting 4 h 34 min; WorkOS reported recovery after its upstream provider enabled alternate delivery routes. | Major incident | |
| Grafana Cloud | Major incident: Tempo Write Failures in prod-us-central-0 Grafana Cloud reported a major incident causing intermittent Tempo write failures in GCP US Central - prod-us-central-0 ingestion due to Google Cloud Storage internal errors, affecting trace ingestion. It started at 2026-10-15 16:10 UTC and was resolved at 2026-10-15 21:53 UTC; the recorded duration was 5 h 42 min. | Major incident | |
| OpenAI | Major incident: Widespread feature degradation OpenAI reported major, widespread feature degradation, including login and signup issues in ChatGPT iOS/Android apps, starting 2026-10-15 14:30 UTC and lasting 4 h 26 min. A mitigation was applied at 17:13 UTC, and all impacted services fully recovered by 2026-10-15 18:56 UTC. | Major incident | |
| ChatGPT | Major incident: Widespread feature degradation ChatGPT reported major widespread feature degradation, including login and signup issues in its iOS/Android apps, starting 2026-10-15 14:30 UTC and lasting 4 h 26 min. A mitigation was applied, and all impacted services had fully recovered by 2026-10-15 18:56 UTC; no cause was stated. | Major incident | |
| Axiom | Major incident: Metrics query failures in US region Axiom reported a major outage affecting Metrics (MPL) queries in the US region, causing failed queries or unavailable metric data through the Axiom Console and API. It started at 2026-10-15 12:21 UTC and was resolved at 2026-10-15 13:15 UTC, lasting 54 min; Axiom reported deploying a fix but did not specify the cause. | Major incident | |
| Axiom | Major incident: Metrics ingestion and query disruption Axiom reported a major Metrics ingestion and query disruption starting 2026-10-15 10:59 UTC and lasting 55 min. Following an infrastructure change, /v1/metrics ingestion could fail or be delayed, and queries failed to discover recent metric data. Ingestion was reported restored at 2026-10-15 11:07 UTC; the query issue was confirmed fixed at 2026-10-15 11:54 UTC. | Major incident | |
| Bitbucket | Critical incident: Bitbucket Cloud - Service Disruption Bitbucket Cloud reported a critical disruption affecting API, Pipelines and Website, with connection errors, timeouts and access failures. It started at 2026-10-15 10:07 UTC and resolved at 2026-10-15 12:08 UTC (2 h 0 min); a fix restored core services while Pipelines cleared backlogged builds. | Major incident | |
| Box | Major incident: [Major] Issue with Box Drive Box reported a major incident delaying updates from the Box Web App to Box Drive desktop clients for some users. It started at 2026-10-15 08:30 UTC and was resolved at 2026-10-15 12:41 UTC, lasting 4 h 11 min. Box reported remediation and restoration of full functionality but did not disclose the underlying cause. | Major incident | |
| Estuary | Major incident: Reporting, inferred schemas, and GCP-us-central1 c2 outage Estuary reported a major outage affecting reporting and inferred schema updates system-wide, plus tasks on GCP: us-central1 c2, from 2026-10-15 07:48 UTC to 2026-10-15 09:33 UTC (1 h 45 min). A fix restored tasks and cleared reporting, task stats and inferred schema backlogs; Estuary expected no data loss or duplication. | Major incident | |
| Recurly | Major incident: Snowflake on AWS and Azure shares may be unavailable. Recurly reported a major outage affecting some Snowflake data shares on AWS and Azure: permissions affected following a release could prevent access or queries. It started at 2026-10-15 04:34 UTC and was resolved at 2026-10-15 07:15 UTC, lasting 2 h 40 min. Affected merchants must contact Support for scripting to re-establish shares and all grants. | Major incident | |
| Modal | Critical incident: Kimi K3 shared endpoint downtime Modal’s Kimi K3 shared endpoint returned elevated 5xx errors in a vendor-rated critical outage starting 2026-10-14 22:17 UTC. It lasted 6 min and was resolved at 2026-10-14 22:23 UTC after Modal applied a mitigation; the endpoint was fully operational. | Major incident | |
| Render | Major incident: Builds, deploys, and queued deploys are not starting in all regions Render reported a major outage preventing builds, deploys, and queued deploys from starting in all regions, beginning 2026-10-14 19:32 UTC and resolved at 2026-10-14 22:18 UTC (2 h 45 min). A fix was implemented; deploys and builds for services running on free instances remained paused during monitoring before resolution. | Major incident | |
| Framer | Critical incident: Editor is unavailable Framer’s editor was unavailable during a vendor-rated critical incident from 2026-10-14 15:05 UTC to 2026-10-14 15:29 UTC, lasting 24 min. Framer restored editor availability and said it was monitoring and further investigating; no cause was stated. | Major incident | |
| Salesloft | Major incident: Certain users are unable to access Conversation Intelligence from within Salesloft/Clari Certain users could not access Conversation Intelligence within Salesloft/Clari during a major-impact incident from 2026-10-14 13:51 UTC to 2026-10-14 15:41 UTC, lasting 1 h 50 min. Salesloft identified an access-related issue, confirmed resolution for affected users, and said the platform remained available to the majority of users. | Major incident | |
| Sentry | Major incident: Ingestion Halted for EAP data in EU Sentry reported a major outage halting EAP ingestion in the EU, affecting EU Span Ingestion, EU Spans Alerting and Dashboard. It started at 2026-10-14 05:46 UTC and resolved at 2026-10-14 08:20 UTC, lasting 2 h 33 min. Sentry implemented a fix and waited for ingestion lag to burn down. | Major incident | |
| Xero | Major incident: Global: Xero - Some customers may be experiencing some errors in product and inability to view invoice PDFs. Xero reported a major global incident affecting some customers navigating the product, generating invoices and PDFs, and viewing invoice PDFs. It started at 2026-10-14 04:08 UTC and was resolved at 2026-10-14 04:33 UTC, lasting 25 min. Xero attributed it to a network connectivity issue and said service was restored. | Major incident | |
| dbt Labs | Critical incident: Unable to Access dbt Platform dbt Labs reported a critical outage affecting dbt Platform web application loading, logins, and Admin API access. It started at 2026-10-13 22:04 UTC and was resolved at 2026-10-14 04:33 UTC, lasting 6 h 29 min. A deployed fix restored normal operation. | Major incident | |
| Cursor | Major incident: Grok Bot routines not triggering A major outage prevented many Grok Bot routines triggered by webhooks, Slack, git, email and Linear events from running; missed events won't be retried automatically. Service recovered, but recorded timestamps conflict: started 2026-10-13 21:13 UTC, resolved 2026-10-13 20:29 UTC; duration unknown. | Major incident | |
| Optimizely | Major incident: Elevated GraphQL API errors and delayed data ingestion in ODP – US region Optimizely reported a major ODP US incident between 15:05 and 16:10 UTC on October 13, 2026: elevated GraphQL API errors and delayed ingestion. Most GraphQL requests failed; ingestion lagged up to about 65 minutes, with all accepted delayed data processed by 16:10 UTC. Recorded start/resolution: 2026-10-13 18:10 UTC; computed duration: 0 min. | Major incident | |
| Astronomer | Major incident: Astro UI and API are appearing offline for some users Astro UI and API appeared offline for some users in a major incident starting 2026-10-13 18:02 UTC, resolved at 2026-10-13 19:53 UTC (1 h 51 min). Existing tasks and Dag Runs continued successfully. Restarting a service experiencing higher-than-expected load restored functionality; Astronomer identified a proximate cause but did not disclose it. | Major incident | |
| Cloudsmith | Major incident: Issues with package downloads Cloudsmith reported a major outage causing 404s when downloading 'pre-release' package versions, from 2026-10-13 16:39 UTC to 2026-10-13 17:47 UTC (1 h 8 min). Cloudsmith deployed a fix, worked through backfilling outstanding packages, and confirmed resolution. | Major incident | |
| Cloudflare | Major incident: Cloudflare Service Issues Cloudflare reported a major incident involving network performance in IAD, causing increased errors across its services and possible errors or timeouts reaching its network or services. It started at 2026-10-13 16:39 UTC and was resolved at 2026-10-13 17:07 UTC, lasting 28 min. | Major incident | |
| HashiCorp | Major incident: Terraform Runs Failing Some customers’ Terraform applies failed with a pre-apply run task error: “Unexpected response from broker: Status code: 424, Message: Failed Dependency.” HashiCorp rated the outage major; it started at 2026-10-13 16:01 UTC and lasted 22 min, resolving at 2026-10-13 16:23 UTC. Engineering implemented a fix at 2026-10-13 16:14 UTC; no cause was stated. | Major incident | |
| Terraform Cloud (HCP) | Major incident: Terraform Runs Failing Terraform Cloud (HCP) reported a major incident affecting some customers: Terraform applies failed with a pre-apply run task error, “Unexpected response from broker: Status code: 424, Message: Failed Dependency.” It started at 2026-10-13 16:01 UTC and lasted 22 min, resolving at 2026-10-13 16:23 UTC after Engineering implemented a fix. | Major incident | |
| Aircall | Major incident: Increased Error Rate Aircall reported a major error spike causing sporadic issues across calling, login, apps and Dashboard services, limited to a subset of actions. It started at 2026-10-13 15:38 UTC and was resolved at 2026-10-13 16:19 UTC, lasting 40 min; no cause or specific fix was stated. | Major incident | |
| ElevenLabs | Major incident: Multiple US endpoints experiencing timeouts and latency Multiple ElevenLabs US endpoints, including some Elevenagents endpoints, experienced elevated latency, timeouts and failed requests in a major incident starting 2026-10-13 09:21 UTC. It lasted 4 h 57 min, resolving at 2026-10-13 14:18 UTC after work with its data service provider; stable service was confirmed, with root cause analysis still pending. | Major incident | |
| Contentful | Major incident: [INCIDENT] https://www.contentful.com/developers/docs/ is not working Contentful Docs was unavailable in an incident rated major, with Web App listed as affected. It started at 2026-10-12 18:22 UTC and was marked resolved at 2026-10-12 18:27 UTC; the computed duration was 4 min. No cause or fix was stated, and the resolution update still said investigation was ongoing. | Major incident | |
| Groq | Major incident: Model Performance or Availability Issue Groq reported a major incident affecting minimaxai/minimax-m2.7, with users potentially seeing API failures due to hardware connectivity issues. It started at 2026-10-12 18:17 UTC and was resolved at 2026-10-12 18:36 UTC; the computed duration was 18 min, and Groq confirmed normal model operation. | Major incident | |
| Sigma Computing | Major incident: Service Degradation for writeback functionality on Databricks connections Sigma reported a major degradation affecting CSV uploads to Sample Connection and potentially Databricks writeback functionality, including Input Tables, caused by a Databricks AWS US West 2 service interruption. The incident started at 2026-10-12 15:11 UTC and was resolved at 2026-10-12 18:17 UTC, lasting 3 h 6 min; writeback failures were no longer occurring. | Major incident | |
| v0 | Major incident: Increased build and deployment failures v0 reported a major incident affecting builds and Git integrations from 2026-10-12 13:35 UTC to 2026-10-12 20:11 UTC, lasting 6 h 36 min. Some builds failed or deployments failed to start; v0 cited an upstream GitHub incident affecting GitHub-connected projects. Deployment-status events were also delayed; the backlog was processed and the incident resolved. | Major incident | |
| Vercel | Major incident: Increased build and deployment failures Vercel reported a major incident affecting builds and deployments from 2026-10-12 13:35 UTC to 2026-10-12 20:11 UTC, lasting 6 h 36 min. An upstream GitHub incident caused some GitHub-connected projects’ builds and deployments to fail; deployment-status updates on pull requests were also delayed. The event backlog was processed, and the incident was resolved. | Major incident | |
| Grafana Cloud | Major incident: Elevated Errors Ingesting Metrics in AWS US East (VA) Grafana Cloud reported a major metrics-ingestion incident in AWS US East (VA) - prod-us-east-3, causing failed or delayed writes and potentially affecting Frontend Observability and Synthetic Monitoring data. It started 2026-10-12 09:45 UTC and resolved 2026-10-12 16:42 UTC (6 h 56 min); Grafana isolated suspected contributing infrastructure and reported normal service restored. | Major incident | |
| Aircall | Major incident: Calling Issues Aircall reported a major incident preventing a subset of customers from receiving or making calls, starting at 2026-10-12 09:29 UTC and resolved at 2026-10-12 10:17 UTC (48 min). A fix was implemented by 10:05 UTC, when voice traffic appeared stable; no cause was stated. | Major incident |