Notable SaaS vendor changes, page 20
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 |
|---|---|---|---|
| Render | Critical incident: Render Dashboard Unavailable Render Dashboard was unavailable in a critical-impact incident starting 2026-07-15 00:22 UTC, resolved at 2026-07-15 00:54 UTC after 31 min. Render reported identifying the root cause and making a change that restored the dashboard, but did not specify the cause or fix. | Major incident | |
| Elastic Cloud | Major incident: Cloud Console Deployment Errors Elastic Cloud reported a major Cloud Console incident affecting access to create, update, delete and view Elastic Cloud Hosted deployments. It started at 2026-07-15 00:15 UTC; management access was restored at 00:31 UTC, and the incident was resolved at 2026-07-15 01:12 UTC, with a reported duration of 56 min. | Major incident | |
| GitLab | Major incident: Elevated Errors Affecting AI Gateway Health Checks | Major incident | |
| SurveyMonkey | Major incident: Customers are unable to contact support through our Help Center chatbot SurveyMonkey reported a major Help Center chatbot outage preventing customers from reaching a live agent or submitting an email support case. It started at 2026-07-14 19:07 UTC and was resolved at 2026-07-14 20:06 UTC, lasting 58 min. A fix was implemented at 07-14 20:00 UTC; no cause was stated. | Major incident | |
| Mux | Major incident: Video Playback Issues Mux reported a major incident affecting Mux Video - Live and Mux Video - VOD, with playback errors or timeouts for some customers. It started at 2026-07-14 17:09 UTC and lasted 2 h 52 min, resolving at 2026-07-14 20:01 UTC; a fix was implemented at 2026-07-14 18:03 UTC. | Major incident | |
| Bitrise | Major incident: ORD data center network outage Bitrise reported a major ORD data center outage affecting Builds (CI), with possible failures or delays, starting 2026-07-14 16:40 UTC and resolved after 25 h 33 min. Dropped packets between nodes caused failed health checks and cluster-wide disruption; mitigation restored job scheduling, and network configuration changes were applied across all data centers. | Major incident | |
| Lever | Critical incident: Offer Letter Generation Failures Lever reported a critical outage affecting offer-letter generation and delivery in Global Data Center - LeverTRM - Hire, Hire +, starting 2026-07-14 14:47 UTC and resolved 2026-07-14 23:50 UTC (9 h 2 min). The postmortem reported intermittent document/resume preview failures caused by a failed conversion step; no data loss occurred. | Major incident | |
| Sentry | Critical incident: Error ingestion degraded in DE region Sentry reported critical error-ingestion degradation in the DE region starting 2026-07-14 14:44 UTC and resolved at 2026-07-14 19:32 UTC, lasting 4 h 47 min. Error processing returned to real time and backlogs cleared; a fix was deployed to unblock feedback ingestion, which also returned to real time with its backlog processed. | Major incident | |
| Help Scout | Major incident: Docs Errors Help Scout reported a major incident affecting Docs Sites and Web App: Docs sites failed to load, with intermittent loading issues continuing after an initial recovery. The incident started at 2026-07-14 12:17 UTC and was resolved at 2026-07-14 19:00 UTC, lasting 6 h 43 min; Help Scout confirmed Docs was fully operational. | Major incident | |
| Cloudsmith | Major incident: Intermittent failures when syncing Docker images. Cloudsmith reported a major incident causing intermittent Docker image sync failures from 2026-07-14 08:23 UTC to 2026-07-14 16:07 UTC, lasting 7 h 43 min. Security scan results were delayed, and some customers experienced SBOM generation failures during mitigation. Services were fully restored and the impacted SBOM backfill completed. | Major incident | |
| Canva | Major incident: Some users may have issues using Canva Canva reported a major Billing and subscriptions incident in which users were shown the wrong subscription status. It started at 2026-07-13 22:57 UTC and was resolved at 2026-07-13 23:17 UTC, lasting 19 min. | Major incident | |
| Amplitude | Critical incident: Amplitude UI and MCP is down Amplitude reported a critical outage affecting its UI, MCP and REST APIs, starting 2026-07-13 21:31 UTC and resolved at 2026-07-13 23:07 UTC (1 h 36 min). A fix was implemented; Amplitude expected no data loss, said the EU data center should be unaffected, and required no customer action. | Major incident | |
| Amplitude | Major incident: AI features degraded Amplitude reported a major degradation affecting Agents and Chat: some users could not load or use AI-powered features. The incident started at 2026-07-13 18:51 UTC and was resolved at 2026-07-13 23:17 UTC, lasting 4 h 25 min; no cause or fix was stated. | Major incident | |
| Mailgun | Critical incident: US Email Validation 500's and Mailgun Control Panel Unavailable Mailgun reported a critical incident involving US Email Validation 500 errors and an unavailable Control Panel, starting 2026-07-13 18:23 UTC and resolved at 2026-07-13 19:56 UTC (1 h 32 min). A fix was implemented and monitored; no cause was stated. | Major incident | |
| Monday.com | Major incident: Issues with platform latency Monday.com reported major platform latency and loading failures affecting Boards, Dashboards, Docs, Automations, AI features and other services, with Platform and Dashboards components listed across AUS, EU and US. The incident started at 2026-07-13 14:37 UTC and lasted 2 h 57 min, resolving at 2026-07-13 17:34 UTC; a fix was implemented at 17:04 UTC. | Major incident | |
| Amplitude | Major incident: Custom Metrics – Metric Details Page Unavailable Amplitude reported a major outage affecting the Custom Metrics metric details page, which could fail to load or display an error. The incident started at 2026-07-13 11:41 UTC and was resolved at 2026-07-13 14:59 UTC, lasting 3 h 17 min. A deployed fix restored normal loading; no data was lost. | Major incident | |
| Buffer | Major incident: Issue with Threads comments Buffer reported a major delay in new Threads comments caused by a Meta API issue, from 2026-07-13 08:48 UTC to 2026-07-19 10:20 UTC, lasting 6 days 1 h. Normal delivery was restored, and a backup mechanism recovered recent delayed comments; manual sync was also available through the Threads channel page in Community or Sync now. | Major incident | |
| Amplitude | Major incident: Slow Loading for Web App Features in the EU Region Amplitude reported major elevated latency in the EU affecting Analytics - Web Application, Audiences - Web Application, Experiment - Web Application, Guides & Surveys, Session Replay and Web Application. The incident ran from 2026-07-13 06:15 UTC to 2026-07-13 08:39 UTC (2 h 23 min); a rollback restored performance. | Major incident | |
| Sentry | Critical incident: Ingestion delayed for spans, logs, crons in US region Sentry reported critical ingestion delays for spans, logs and crons in the US region, affecting monitoring and alerting. The incident ran from 2026-07-13 00:58 UTC to 2026-07-13 02:56 UTC (1 h 58 min); Sentry implemented a fix and confirmed ingestion had caught up and alerts were restored. | Major incident | |
| Baseten | Major incident: Partial Outage on Model APIs Baseten reported a major partial outage of Model APIs affecting Kimi-K2.6 and GLM-5.2, starting 2026-07-13 00:04 UTC and lasting 2 h 6 min until resolution at 2026-07-13 02:10 UTC. Baseten identified an infiniband outage at one provider; GLM-5.2 recovered first, followed by Kimi-K2.6. | Major incident | |
| CockroachDB | Major incident: Cluster Creation Failure CockroachDB reported a major cluster creation failure affecting CockroachDB Basic/Standard starting at 2026-07-12 20:08 UTC. Cluster creation was restored at 2026-07-12 21:24 UTC, resolving the incident after 1 h 16 min. | Major incident | |
| Heap | Major incident: Dashboard and Chart loading issues Heap dashboards and charts experienced loading delays or failures in the App, with impact rated major. The incident started at 2026-07-12 13:54 UTC and was resolved at 2026-07-13 12:49 UTC, lasting 22 h 55 min; no cause or specific fix was stated. | Major incident | |
| SentinelOne | Critical incident: [EU1, NA1] - Multiple Consoles Inaccessible SentinelOne reported a critical outage affecting console access in Germany (EU1) and USA (NA1), starting 2026-07-12 11:36 UTC and resolved at 2026-07-12 16:58 UTC, lasting 5 h 21 min. The vendor identified the underlying issue without disclosing its cause and confirmed all services were fully restored. | Major incident | |
| JFrog | Critical incident: Potential JFrog Xray Service Disruption Across All Regions JFrog reported a critical potential Xray disruption across all regions, with a subset of customers potentially experiencing authentication errors or failures accessing Xray and performing related operations. It started at 2026-07-12 10:45 UTC and was resolved at 2026-07-12 12:45 UTC, lasting 1 h 59 min; no cause or specific fix was stated. | Major incident | |
| Cloudinary | Major incident: Elevated Error Rates for Requests Using g_auto A major Cloudinary incident caused elevated errors for g_auto requests on AP Datacenter - Media Transformation API - AP and Media Transformation API - AP. Errors began approximately 09:00 UTC on July 12; the incident record started 2026-07-12 10:20 UTC and lasted 2 h 24 min. At 2026-07-12 12:44 UTC, services and affected URLs were reported functioning normally. | Major incident | |
| Canva | Major incident: Some users may have issues downloading video designs Some Canva users experienced issues downloading video designs in a major-impact incident affecting Designs - Downloading designs and Downloading designs. It started at 2026-07-12 08:38 UTC and was resolved at 2026-07-12 17:29 UTC, lasting 8 h 51 min; no cause or specific fix was stated. | Major incident | |
| Brex | Major incident: Maintenance is complete, Dashboard and External APIs are available. Brex’s Dashboard and External APIs were down for temporary maintenance starting 2026-07-12 07:08 UTC. The vendor marked the impact as major; maintenance ended and availability was restored at 2026-07-12 07:17 UTC, after 9 min. | Major incident | |
| Cloudsmith | Major incident: Partial outage impacting normal operations globally Cloudsmith reported a major partial outage with elevated error rates across all regions, starting at 2026-07-11 00:59 UTC and resolved at 2026-07-11 01:26 UTC; the computed duration was 26 min. Engineers reported resolving the issue at 01:07 UTC, but no cause was stated. | Major incident | |
| Sentry | Critical incident: Error ingestion degraded in US region Sentry reported critical degradation of US Error Ingestion and US Errors Alerting, delaying ingested errors from 2026-07-10 22:43 UTC to 2026-07-11 03:34 UTC (4 h 51 min). Sentry confirmed the backlog was processed at resolution; no specific cause was stated. | Major incident | |
| BigCommerce | Major incident: Availability Issues BigCommerce reported a major Storefront availability incident affecting a subset of stores, starting at 2026-07-10 21:11 UTC and resolved at 2026-07-11 00:04 UTC, lasting 2 h 52 min. Engineers investigated, but no cause or specific fix was stated. | Major incident | |
| Mailgun | Major incident: Mailgun Control Panel Unavailable For Some Users Mailgun reported a major incident making the Control Panel unavailable for some users, with Email Validation also listed as affected. It started at 2026-07-10 18:07 UTC and resolved at 2026-07-10 20:11 UTC, lasting 2 h 3 min; Mailgun rolled out a fix to impacted regions. | Major incident | |
| Bitrise | Major incident: Elevated error rates for the Bitrise Workflow Editor Bitrise’s Workflow Editor experienced elevated HTTP errors, page-load failures and timeouts affecting all users in a major (SEV-1) incident from 2026-07-10 17:49 UTC to 2026-07-10 19:50 UTC, lasting 2 h 1 min. Bitrise attributed it to an ongoing LaunchDarkly incident affecting flag delivery evaluations; a workaround restored normal loading before resolution. | Major incident | |
| LaunchDarkly | Critical incident: Web application unavailable and flag delivery evaluations have elevated failure rate LaunchDarkly reported a critical incident from 2026-07-10 17:40 UTC to 2026-07-10 18:19 UTC, when it was resolved: app.launchdarkly.com was unavailable and flag-value retrieval had elevated failure rates. Customers using client-side or server-side SDKs should have continued seeing last known flag values where a local cache existed. | Major incident | |
| Secureframe | Critical incident: Elevated errors with third party vendor Secureframe reported a critical incident affecting API, Trust, and Web Application: elevated API errors with a third-party vendor caused app-wide issues. It started at 2026-07-10 17:25 UTC and was resolved at 2026-07-10 18:57 UTC, lasting 1 h 32 min; the third-party service recovered and all affected services were fully operational. | Major incident | |
| Discord | Major incident: Issues with billing operations Discord reported a major incident affecting billing operations across API and Payments, starting 2026-07-10 16:49 UTC and resolved at 2026-07-10 19:33 UTC, lasting 2 h 43 min. A fix was implemented by 17:11 UTC and monitored before resolution; no cause was stated. | Major incident | |
| Runway | Critical incident: We've identified a problem and are working on a fix Runway reported a critical outage affecting App, Backend, and Public API starting 2026-07-10 16:42 UTC, lasting 1 h 0 min and resolved at 2026-07-10 17:42 UTC. A fix was released at 07-10 16:48 UTC with improvements observed; no specific cause or user-facing failure was stated. | Major incident | |
| Snowflake | Major incident: INC20000082 Snowflake reported a major PrivateLink connectivity outage in Azure - East US 2 (Virginia), potentially causing connection errors or timeouts. It started at 2026-07-10 14:30 UTC and resolved at 2026-07-10 16:28 UTC (1 h 57 min). Telemetry indicated connectivity had recovered around 14:33 UTC, mitigating impact for most customers. | Major incident | |
| Datadog | Major incident: Delayed data streams data Datadog reported a major Data Streams Monitoring degradation in US1 from 2026-07-10 14:09 UTC to 2026-07-10 15:59 UTC, lasting 1 h 50 min. Latency metrics were delayed or not updating for some users, potentially preventing monitor alerts. A fix was implemented; a small percentage of data was still being backfilled before resolution. | Major incident | |
| ActiveCampaign | Critical incident: Customer accounts hosted in APAC region are unavailable. ActiveCampaign reported a critical outage making customer accounts hosted in the APAC region unavailable from 2026-07-10 00:49 UTC to 2026-07-10 02:01 UTC, lasting 1 h 12 min. A fix was implemented by 07-10 01:45 UTC, and the incident was subsequently resolved. | Major incident | |
| Salesforce | Major incident: Cc Carts Unavailable: Omnichannel Inventory | Major incident | |
| Render | Major incident: Some services and datastores in Singapore experiencing brief disruptions Render reported a major incident causing brief disruptions to some Singapore services and datastores, including Background Workers, Cron Jobs, PostgreSQL, Redis, Web Services, and Web Services - Free Tier. It started at 2026-07-09 18:18 UTC and was resolved at 2026-07-09 18:44 UTC, lasting 26 min; Render reported implementing a fix and monitoring results. | Major incident | |
| Matillion | Critical incident: Snowflake Runner Key-pair/Secret Retrieval Failures Matillion reported a critical incident involving Snowflake Runner key-pair/secret retrieval failures affecting Agents in AU, EU and US regions. It started at 2026-07-09 12:23 UTC and was resolved at 2026-07-09 14:44 UTC, lasting 2 h 20 min; Matillion said the issue was identified and a fix was being implemented, but provided no cause or fix details. | Major incident | |
| Pinecone | Major incident: [Serverless][Azure][eastus2] 5xx errors on some requests for some indexes Pinecone reported a major outage causing 5xx errors on some requests for some Serverless indexes in Azure eastus2. It started at 2026-07-09 09:50 UTC and was resolved at 2026-07-09 14:37 UTC, lasting 4 h 47 min; Pinecone reported implementing a fix and monitoring the results. | Major incident | |
| Hootsuite | Major incident: Bluesky service disruption A major Bluesky disruption affected Hootsuite and Talkwalker from 2026-07-09 09:19 UTC to 2026-07-09 11:13 UTC (1 h 54 min), causing publishing and scheduling difficulties and stopping new Bluesky data capture for listening or monitoring. Bluesky confirmed its issue was fixed; Hootsuite marked the incident resolved and reported services recovering. | Major incident | |
| Amplitude | Major incident: Shared Embeds and Public Links Unavailable Amplitude reported a major outage: shared embeds and public dashboard/chart links displayed blank pages between 00:24 UTC Jul 9 and 08:50 UTC. The incident started at 2026-07-09 09:12 UTC and resolved at 2026-07-09 09:45 UTC (33 min). Rolling back the affected service restored rendering; no data was lost and no customer action was needed. | Major incident | |
| Salesforce | Major incident: Marketing Cloud Disruption: Marketing Cloud Core Service | Major incident | |
| Salesforce | Critical incident: Service Disruption: Core Service | Major incident | |
| Statsig | Major incident: Feature Flag Evaluation Errors (Statsig) Statsig’s major V2 Config Delivery API incident was recorded starting 2026-07-09 01:28 UTC and resolved after 1 h 8 min. Launched Feature Gates could return false instead of defaults between 20:56 UTC on July 8 and 01:40 UTC on July 9; V1 was unaffected. A config-spec generation change caused the issue; affected services were rolled back. | Major incident | |
| Salesforce | Major incident: Mule Soft Service Disruption: APIManager, Access Management, Audit Log +2 more | Major incident | |
| Expo | Critical incident: Major outage of EAS backend Expo reported a critical EAS backend outage affecting EAS Build, EAS Hosting, EAS Insights, EAS Submit, EAS Update, EAS Workflows and the Website from 2026-07-08 20:39 UTC to 2026-07-08 21:29 UTC (50 min). Expo implemented a fix at 21:01 UTC and confirmed all services were operational at resolution; no cause was stated. | Major incident |