Major incidents SaaS vendor changes, page 5

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)CompanyChangeKind
CloudsmithMajor incident: Issues Pulling Docker Images
Cloudsmith reported a major incident affecting customers' ability to push and pull Docker images, starting at 2026-09-28 16:55 UTC and resolved at 2026-09-28 17:28 UTC after 33 min. Engineering released a fix and monitored performance before resolution.
Major incident
ActiveCampaignCritical incident: Transactional Email Failures
ActiveCampaign reported a critical outage preventing transactional emails from sending, starting at 2026-09-28 15:05 UTC and resolved at 2026-09-28 18:55 UTC, lasting 3 h 50 min. Backlogged messages began sending at 15:16 UTC, and a fix was implemented at 15:22 UTC.
Major incident
ElevenLabsMajor incident: Agents - EU Residency
ElevenLabs reported a major outage affecting ElevenAgents EU residency, starting 2026-09-28 13:50 UTC and lasting 49 min. The vendor investigated a possible underlying database provider issue and released a fix; it stated resolution time was 14:18 UTC, with the incident marked resolved at 14:39 UTC.
Major incident
SquarespaceMajor incident: Squarespace loading and editing Issues
Squarespace reported a major loading and editing outage affecting Commerce, Email Campaigns, and Site Editing, including access to the Email Campaigns panel and applying or accessing certain premium features. It started at 2026-09-28 13:17 UTC and lasted 48 min; a fix was implemented at 13:50 UTC, and the incident was resolved at 14:06 UTC.
Major incident
BoxMajor incident: [Medium] Issues with Box Notes
Box Notes users could encounter errors or slowness when creating or updating notes. Box marked the impact as major; the incident started at 2026-09-28 10:04 UTC and was resolved at 2026-09-28 10:31 UTC, lasting 27 min. Box confirmed full functionality was restored but stated no cause or specific fix.
Major incident
CloudinaryMajor incident: Increased Error Rates – EU Region
Cloudinary reported a major EU-region incident affecting uploads (eager transformations), transformations, and delivery; errors began approximately 06:15 UTC on 2026-09-28. The recorded incident started at 2026-09-28 09:58 UTC and was resolved at 2026-09-28 14:33 UTC, lasting 4 h 35 min. A fix was implemented at 10:08 UTC.
Major incident
XeroMajor incident: ATO services may be unavailable
Xero reported a major ATO outage preventing customers from filing tax returns or STP filings, affecting AU Payroll and Tax Reporting - BAS, TPAR. It started at 2026-09-28 00:03 UTC and lasted 25 min, resolving at 2026-09-28 00:28 UTC after the ATO implemented a fix.
Major incident
ConfluentMajor incident: Missing Metrics on Confluent Cloud
Confluent reported a major degradation: Cloud Metrics were delayed from 00:33 to 02:15 UTC on Sep 27, potentially leaving recent-metrics queries incomplete or empty. Marked resolved, its timestamps conflict: start 2026-09-27 17:17 UTC, resolution 2026-09-27 02:00 UTC, and update-stated resolution 02:15 UTC; computed duration is unknown.
Major incident
SalesforceMajor incident: Mule Soft Service Disruption: Access ManagementMajor incident
SnowflakeCritical incident: INC20000239
A critical Snowflake outage affected services in AWS - US West (Commercial Gov - Oregon) and AWS - US West (Oregon), starting 2026-09-27 02:15 UTC and resolving 2026-09-27 03:16 UTC (1 h 0 min). Snowflake attributed the impact to its third-party cloud platform and coordinated with that platform to implement a fix and confirm restoration.
Major incident
FigmaCritical incident: Service disruption
Figma reported a critical disruption from 2026-09-27 01:04 UTC to 2026-09-27 02:32 UTC, lasting 1 h 28 min, with services degraded or unavailable due to failures with AWS and other dependencies. Affected components included Figma Design, FigJam, Dev Mode, REST API, and Sign-in & Account Access; Figma reported services operational at 01:18 UTC before confirming resolution.
Major incident
LinearCritical incident: EU sync failure
Linear reported a critical EU sync outage starting 2026-09-27 00:55 UTC; the incident record lasted 4 days 16 h, closing 2026-10-01 17:50 UTC. Linear identified a faulty deployment; a restart restored access and offline syncing by 09-27 11:15 UTC. Linear said user impact ended then and later published a post-mortem.
Major incident
SalesforceMajor incident: Marketing Cloud Disruption: Marketing Cloud Core ServiceMajor incident
Fly.ioCritical incident: Network outage in AMS region
Fly.io reported a critical network outage affecting connectivity to the AMS region, starting at 2026-09-26 19:31 UTC and resolved at 2026-09-26 19:53 UTC (21 min). Fly.io worked with upstream providers to restore connectivity and reported the network recovering at 19:46 UTC.
Major incident
Sigma ComputingMajor incident: Export Failures Incident
Sigma Computing reported a major incident affecting password-authentication logins and scheduled exports across Azure, AWS and GCP, linked to an email-service disruption. Recorded from 2026-09-26 15:25 UTC to 2026-09-26 16:11 UTC (45 min), it was resolved after a fix; updates separately cited an approximate start of September 26, 2026, at 11:24 AM UTC.
Major incident
InngestMajor incident: Delays with function execution
Inngest reported a major incident causing delays with function execution, starting at 2026-09-26 06:01 UTC and resolved at 2026-09-26 06:20 UTC, lasting 18 min. The vendor confirmed the system was fully operational but stated no cause or specific fix.
Major incident
PlaidMajor incident: Service Disruption Impacting Bank of America connections
Plaid reported a major disruption affecting Bank of America connections and API calls through Plaid, starting at 2026-09-26 03:40 UTC and resolved at 2026-09-26 05:15 UTC (1 h 34 min). Plaid stated that Bank of America was experiencing downtime impacting all channels and data recipients.
Major incident
HashiCorpMajor incident: Users unable to access releases.hashicorp.con
A major outage at releases.hashicorp.com caused 504 errors, affecting terraform provider downloads and Vault Radar access. The incident started at 2026-09-26 02:35 UTC and lasted 28 min, resolving at 2026-09-26 03:03 UTC; engineering implemented a fix and confirmed normal operation.
Major incident
Terraform Cloud (HCP)Major incident: Users unable to access releases.hashicorp.con
A major outage prevented access to releases.hashicorp.com, causing 504 errors and affecting terraform provider downloads and Vault Radar access. The recorded incident started at 2026-09-26 02:35 UTC and lasted 28 min, resolving at 2026-09-26 03:03 UTC; engineering reported implementing a fix.
Major incident
SnowflakeCritical incident: INC20000237
Snowflake reported a critical outage in AWS - Europe (Ireland), potentially preventing sign-in, queries, data management and private connectivity. The incident started at 2026-09-25 23:00 UTC and was resolved at 2026-09-26 00:20 UTC, lasting 1 h 20 min. Snowflake implemented a fix and confirmed restoration after monitoring; scheduled and serverless task backlogs cleared by 23:43 UTC.
Major incident
OpenAICritical incident: Issues with Codex HN
Codex experienced a critical outage with elevated errors starting 2026-09-25 22:58 UTC, lasting 55 min and resolving at 2026-09-25 23:54 UTC. OpenAI advised that login via API key would unblock access, then applied a mitigation and confirmed full recovery.
Major incident
ChatGPTCritical incident: Issues with Codex HN
Codex experienced a critical outage with elevated errors from 2026-09-25 22:58 UTC to 2026-09-25 23:54 UTC, lasting 55 min. Login via API key was offered as a workaround; the vendor applied a mitigation and reported full recovery.
Major incident
DynatraceMajor incident: User Session Export Issue for SaaS EnvironmentsMajor incident
New RelicMajor incident: Data Irregularities for US region
New Relic reported a major US-region incident affecting some customers, with delayed data in queries, charts, and dashboards and delayed, missing, or suppressed alert notifications. The incident started at 2026-09-25 19:57 UTC and was resolved at 2026-09-25 22:33 UTC, with impacted services restored to normal operations.
Major incident
GitLabMajor incident: Security Reports not loading for some usersMajor incident
RenderMajor incident: Build and deploy failures in Oregon
Render reported a major incident affecting builds and deploys for a subset of services in Oregon, from 2026-09-25 18:26 UTC to 2026-09-25 18:38 UTC (12 min), now resolved. Services using a prebuilt Docker image and static sites were unaffected.
Major incident
SalesforceMajor incident: Datorama Service Disruption: PlatformMajor incident
BufferMajor incident: Issues with Buffer fully loading
Buffer reported a major incident where the app opened but accounts did not fully load, disrupting normal access. It started at 2026-09-25 14:44 UTC and was resolved at 2026-09-25 16:04 UTC, lasting 1 h 20 min; Buffer said it fixed the core loading issue but did not specify the cause.
Major incident
SalesforceMajor incident: Datorama Service Disruption: PlatformMajor incident
GitLabCritical incident: 503s on GitLab.comHNMajor incident
RunPodCritical incident: EU-SE-1 Network Issue
RunPod reported a critical network connectivity outage in EU-SE-1 starting 2026-09-24 21:12 UTC and resolved at 2026-09-24 21:45 UTC, lasting 33 min. The vendor confirmed the EU-SE-1 DC network was operating normally after resolution.
Major incident
NetlifyMajor incident: Error accessing Netlify-hosted sites
Errors affected access to Netlify-hosted sites across Edge Functions, High-Performance Edge Network, and Standard Edge Network in a major-impact outage starting 2026-09-24 19:01 UTC. Netlify reported normal operation at 2026-09-24 19:10 UTC and resolved the incident at 2026-09-24 19:25 UTC; the recorded duration was 23 min.
Major incident
DrataMajor incident: Cron service degraded
Drata reported major cron service degradation affecting background tasks that flag expired reports, update approval statuses, apply policies, and recalculate control readiness, potentially leaving compliance data stale. It started at 2026-09-24 18:56 UTC and was resolved at 2026-09-25 16:37 UTC, lasting 21 h 40 min; a fix was deployed and monitored.
Major incident
Fly.ioMajor incident: State database issues in GRU
Fly.io reported a major GRU outage starting 2026-09-24 16:31 UTC, lasting 2 h 40 min and resolved at 2026-09-24 19:11 UTC. Apps continued running, but machine creation or updates and connections could fail. Fly.io linked the issues to a distributed state database migration, identified a bug, and implemented a fix.
Major incident
AstronomerMajor incident: Astro UI Deployment view unavailable
The Astro Cloud UI Deployments view was unavailable in a major-impact outage starting 2026-09-24 14:52 UTC, lasting 41 min and resolved at 2026-09-24 15:34 UTC; task execution was unaffected. Astronomer rolled back an identified breaking change and advised customers still experiencing issues to refresh the page, then open a support ticket if needed.
Major incident
Fly.ioMajor incident: Private Networking issues (6PN)
Fly.io reported a major incident affecting Private Networking (6PN), starting at 2026-09-24 14:51 UTC and resolved at 2026-09-24 15:37 UTC, lasting 46 min. A fix was implemented by 2026-09-24 15:01 UTC, with private networking error rates returning to normal.
Major incident
GitLabMajor incident: 500 errors while accessing projectsMajor incident
SurveyMonkeyMajor incident: Audience Preview Page is not responding
SurveyMonkey’s Audience Preview Page was not responding in a major incident that started at 2026-09-24 12:16 UTC and was resolved at 2026-09-24 15:32 UTC, lasting 3 h 16 min. The vendor reported that Engineering was investigating, but stated no cause or specific fix.
Major incident
SupabaseCritical incident: Permission errors in the Supabase Dashboard
A critical Supabase Dashboard incident caused permission errors during administrative actions, preventing some users from managing projects. It started at 2026-09-24 10:37 UTC and was resolved at 2026-09-24 11:49 UTC, lasting 1 h 12 min. Supabase applied a fix by 09-24 11:08 UTC and reported administrative operations completing as expected.
Major incident
BasetenMajor incident: Elevated inference 500s for a subset of models deployed in 1 US-East cluster
Baseten reported a major Dedicated Inference outage with elevated inference 500s affecting a subset of models in 1 US-East cluster. It started at 2026-09-24 07:23 UTC and was resolved at 2026-09-24 08:06 UTC, lasting 42 min; a fix was implemented at 07:48 UTC.
Major incident
DiscordMajor incident: Age group status mismatch across devices
Discord reported a major Android degradation involving mismatched age group statuses across devices: “unconfirmed” on an older mobile app but “adult” on web/desktop. It started at 2026-09-24 02:08 UTC and was resolved at 2026-09-24 03:32 UTC, lasting 1 h 23 min. Discord implemented a fix and instructed users to close and refresh the app.
Major incident
BigCommerceMajor incident: Inaccurate product stock on category pages
BigCommerce reported a major Storefront incident in which products incorrectly appeared as "out of stock" on category pages, potentially misleading shoppers about availability. It started at 2026-09-23 20:16 UTC and was resolved at 2026-09-23 23:14 UTC, lasting 2 h 57 min; no cause or fix was stated.
Major incident
FullStoryMajor incident: Failure to load assets during playback for sessions (EU1 Data Center)
FullStory reported a major incident affecting asset loading and session playback in the EU1 Data Center, recorded as starting and resolving at 2026-09-23 19:00 UTC (computed duration: 0 min). The vendor attributed broken playback to a captured-asset URL resolution change and said a rollback at 9:45am UTC fixed it.
Major incident
Fly.ioMajor incident: Partial Sprites outage
Fly.io reported a major partial Sprites outage with intermittent API failures near SJC, later extending to other regions and affecting creating, connecting to, or managing Sprites. It ran from 2026-09-23 18:44 UTC to 2026-09-24 02:12 UTC (7 h 28 min) and was resolved after mitigations and potential fixes were deployed.
Major incident
Terraform Cloud (HCP)Critical incident: HCP Terraform Returning 404s
HCP Terraform returned 404s and experienced degraded performance in a critical incident starting 2026-09-23 17:43 UTC. A fix was implemented at 09-23 18:06 UTC, and the incident was resolved at 2026-09-23 20:02 UTC after 2 h 18 min; the vendor reported systems operating normally.
Major incident
HashiCorpCritical incident: HCP Terraform Returning 404s
HCP Terraform returned 404s and experienced degraded performance in a critical-impact outage starting 2026-09-23 17:43 UTC, lasting 2 h 18 min and resolved at 2026-09-23 20:02 UTC. Engineering implemented a fix at 09-23 18:06 UTC; HashiCorp reported normal operation at resolution but did not disclose the cause.
Major incident
Fly.ioMajor incident: Elevated private networking errors
Fly.io reported a major incident involving elevated private networking errors between machines in some regions, starting at 2026-09-23 14:47 UTC and lasting 35 min. A fix was implemented by 2026-09-23 14:56 UTC, and the incident was resolved at 2026-09-23 15:23 UTC.
Major incident
Elastic CloudMajor incident: Degraded Performance: Cloud Provisioning Delays
Elastic Cloud reported major provisioning delays affecting new deployments, scaling, and maintenance-related instance relocations due to an external container image provider’s slowness; existing running deployments were unaffected. It started at 2026-09-23 14:04 UTC and resolved at 2026-09-23 16:03 UTC, lasting 1 h 58 min. Customers could retry failed plan changes as mitigation.
Major incident
Fly.ioMajor incident: Upstash unavailability in FRA region
A major Upstash outage started 2026-09-23 12:42 UTC and resolved 2026-09-24 07:22 UTC (18 h 39 min). Redis connection timeouts affected databases hosted in fra or gig and clients routed through either region, including databases elsewhere. Replicas failed to finish draining during a planned rolling upgrade and remained out of service; a fix was implemented.
Major incident
ConfluentMajor incident: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
Confluent reported a major incident degrading Cloud Console in all regions and multiple services in AWS us-west-2, including degraded Flink jobs and failed new job submissions. It started at 2026-09-23 11:47 UTC and was resolved at 2026-09-23 23:17 UTC, lasting 11 h 29 min. All affected services recovered; no customer action was required.
Major incident