RewindexChanges
What vendors changed
Every change Rewindex detected on vendor pricing, trust and legal pages and on status pages, newest first. Open one for the full diff.
Struck in red is what the vendor removed, blue is what they added.
Status pages are checked every 10 minutes, pricing, trust and legal pages once or twice a day. Times are shown in UTC.
Follow every change in a feed reader: Atom feed.
Wednesday, March 4
3 incident changes
- OutageMajor incident
CodeiumNetworking issues effecting tab
Codeium reported networking issues affecting Windsurf Tab with major impact, starting at 2026-03-04 13:49 UTC and resolved at 2026-03-04 17:22 UTC. The incident lasted 3 h 32 min; no cause or specific fix was stated.
- OutageMajor incident
- OutageCritical incident
Tuesday, March 3
11 incident changes
- OutageCritical incident
Brex reported a critical Dashboard partial outage starting 2026-03-03 22:14 UTC, lasting 2 h 20 min and resolved at 2026-03-04 00:35 UTC. A fix was in place by 03-03 23:19 UTC; no cause was stated.
- DegradationMajor incident
- OutageCritical incident
SemgrepSemgrep AppSec Platform login page is not working
Semgrep reported a critical AppSec Platform login-page outage affecting Login/SSO; existing sessions remained operative. It started at 2026-03-03 19:23 UTC and was resolved at 2026-03-03 20:05 UTC, lasting 41 min. A fix restored page loading at 19:42 UTC; login and other platform functions were normal at resolution.
- OutageMajor incident
SmartsheetForm Submissions issue
Smartsheet reported a major outage affecting form submissions reaching sheets and some API requests, starting 2026-03-03 17:16 UTC and resolved 2026-03-04 23:42 UTC (30 h 25 min). The vendor cited a code regression, rolled back deployment, and scaled queues; customers were told not to resubmit failed forms because manual replay was planned.
- OutageMajor incident
Codeiumand WindsurfWe are investigating reports of completions/Tab not working
Codeium reported a major outage affecting Windsurf Tab completions, starting at 2026-03-03 17:08 UTC and resolved at 2026-03-03 19:47 UTC, lasting 2 h 38 min. A fix was implemented by 03-03 19:20 UTC; no cause was stated.
- OutageMajor incident
- OutageMajor incident
- DegradationMajor incident
- DegradationMajor incident
- OutageMajor incident
RenderOhio Services with Disks, Data Persistence failing
Render reported a major outage affecting Ohio application services and data services with persistence due to disk errors. It lasted 19 min, from 2026-03-03 00:41 UTC to 2026-03-03 01:00 UTC; all affected services were migrated to new hosts and were running when resolved.
- DegradationMajor incident
New Relic reported a major degradation starting 2026-03-03 00:19 UTC, resolved at 2026-03-03 02:59 UTC. Some customers in the US and EU regions experienced delayed data in queries, charts, and dashboards, plus delayed or missing alert notifications; later updates identified continuing impact in the US region.
Monday, March 2
10 incident changes
- OutageMajor incident
- OutageMajor incident
- OutageMajor incident
MongoDB AtlasMongoDB Atlas: Email notifications may be failing
MongoDB Atlas reported a major-impact MongoDB Cloud incident in which some users may not have received email notifications. It started at 2026-03-02 15:50 UTC and was resolved at 2026-03-02 16:28 UTC, lasting 38 min; MongoDB confirmed email notifications were being sent successfully.
- OutageMajor incident
Jupyter (Anaconda)Increased error rate on anaconda.org
Anaconda.org’s front-end web service experienced increased errors with major impact, starting 2026-03-02 15:46 UTC and lasting 41 min. A fix was implemented by 2026-03-02 16:18 UTC, and the incident was resolved at 2026-03-02 16:28 UTC.
- DegradationMajor incident
- OutageCritical incident
- OutageMajor incident
ConfluentElevated error rates in AWS me-south-1 and me-central-1 regions
Confluent Cloud’s major incident affected AWS me-south-1 and me-central-1, including a complete outage in me-central-1 caused by AWS regional infrastructure failure. Errors began approximately 05:00 AM UTC on March 2; the recorded start was 2026-03-02 07:19 UTC. me-south-1 was mitigated, and the incident resolved 2026-03-20 00:55 UTC after 17 days 17 h.
- OutageCritical incident
- OutageMajor incident
- OutageCritical incident
Sunday, March 1
8 incident changes
- OutageMajor incident
WizAWS service disruptions affecting the me-central-1 region, affected DCs: prod-me1
Wiz reported a major outage affecting Authentication, Ingestion, Portal, Sensor, Wiz CLI, Wiz Code and Wiz Defend in me-central-1 (prod-me1), starting 2026-03-01 20:42 UTC and lasting 36 h 32 min. Marked resolved at 2026-03-03 09:15 UTC, the final update nevertheless said full resolution depended on AWS restoring affected regional services.
- OutageMajor incident
MongoDB AtlasImpaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)
Major MongoDB Atlas disruption began 2026-03-01 19:30 UTC in AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain): impaired cluster operations, unavailable Bahrain workloads, and blocked migration, backup and restore. AWS power/connectivity issues and regional damage were reported; after 185 days 21 h, MongoDB marked it resolved on 2026-09-03 16:47 UTC while stating disruption remained ongoing.
- OutageMajor incident
ConfluentElevated Error Rates in AWS me-central-1 region
Confluent Cloud experienced elevated errors in AWS me-central-1 due to disruption in AWS availability zone mec1-az2, with major impact. Errors began approximately 12:51 PM UTC; the incident was recorded from 2026-03-01 18:08 UTC to 2026-03-01 22:05 UTC (3 h 57 min). Confluent applied mitigation and reported all regional services healthy.
- OutageCritical incident
SnowflakeAWS - Middle East (UAE): INC0152681
Snowflake reported a critical outage in AWS - Middle East (UAE), starting 2026-03-01 13:33 UTC and resolved 2026-05-15 15:10 UTC. Customers could be unable to sign in, execute queries, or manage data. Snowflake cited a power outage at a primary data center and relayed the cloud provider’s advice to migrate workloads and traffic to alternate regions.
- OutageCritical incident
- OutageCritical incident
- OutageMajor incident
- OutageMajor incident
SquarespaceConnectivity Issues
Squarespace reported a major Site Loading outage affecting sites loading, starting at 2026-03-01 09:03 UTC and resolved at 2026-03-01 11:13 UTC, lasting 2 h 9 min. A fix was implemented at 03-01 09:25 UTC; no cause was stated.
Saturday, February 28
2 incident changes
- DegradationMajor incident
DiscordContinued issues with presence and DM delivery
Discord reported major Gateway degradation affecting presence and DM delivery from 2026-02-28 21:54 UTC to 2026-02-28 22:54 UTC, lasting 59 min. Existing sessions could miss new DMs; restarting sessions was suggested as a workaround. Discord said an earlier incident had been marked resolved in error, implemented a fix, and confirmed resolution.
- OutageMajor incident
MongoDB AtlasMongoDB App Services: Connectivity issues
MongoDB Atlas reported a major incident affecting deprecated Atlas App Services Device Sync: affected users could see SSL validation errors. It started at 2026-02-28 19:53 UTC and lasted 31 h 11 min, resolving at 2026-03-02 03:05 UTC; a fix was implemented and monitored.
Friday, February 27
3 incident changes
- DegradationMajor incident
SmartsheetBrandfolder Monthly Reports Delayed
Brandfolder’s major reporting degradation caused stale or missing Insights dashboard data, subscription page metrics, and Insights Data Connector data; February reports were paused. The incident ran from 2026-02-27 21:55 UTC to 2026-03-24 17:57 UTC (24 days 20 h). Smartsheet attributed it to an out-of-sync database-to-analytics replication pipeline and reported implementing a fix.
- OutageMajor incident
Box[Medium] Increased FTP 530 Captcha errors
Box reported a major-impact incident affecting FTP and SFTP logins with increased FTP 530 Captcha errors, starting 2026-02-27 20:02 UTC and lasting 3 h 49 min. A fix was implemented at 2026-02-27 21:58 UTC, and full functionality was restored by resolution at 2026-02-27 23:51 UTC.
- OutageMajor incident
Thursday, February 26
9 incident changes
- DegradationMajor incident
CodecovUpload Processing Queue Slowdown
Codecov reported a major upload processing queue slowdown affecting Codecov Backend, delaying upload processing. The incident started at 2026-02-26 21:20 UTC and was resolved at 2026-02-27 07:56 UTC, lasting 10 h 36 min. A fix was implemented at 02-27 00:39 UTC; no cause was stated.
- OutageCritical incident
- OutageMajor incident
ConfluentAll new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing
Confluent reported a major Confluent Cloud outage affecting all new dedicated Kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2. It lasted 6 h 1 min, from 2026-02-26 19:56 UTC to 2026-02-27 01:57 UTC; the issue was identified, a fix was being implemented, and the incident was subsequently resolved.
- OutageMajor incident
LaunchDarklyInvestigating Issues with LaunchDarkly Application and Authentication
LaunchDarkly reported a major outage affecting some customers’ web app access and authentication from 2026-02-26 15:43 UTC to 2026-02-26 17:06 UTC (1 h 22 min). Some customers also saw low flag-evaluation error counts, but the Flag Delivery Network was generally functional. A fix was implemented, and performance remained stable following mitigation.
- DegradationMajor incident
ConfluentNetwork provisioning service in Azure East US region is degraded
Confluent Cloud experienced a major network provisioning degradation in Azure East US: provisioning new networks could fail. It started at 2026-02-26 13:59 UTC and was resolved at 2026-02-26 22:24 UTC, lasting 8 h 24 min. Confluent reported implementing a fix at 02-26 22:23 UTC but did not state a cause.
- DegradationMajor incident
Help Scout reported a major degradation causing slow page loads and timeouts in the web app, with Email Processing and mailbox counts, folders, reports, and search results listed as affected. It started at 2026-02-26 12:21 UTC and was resolved at 2026-02-26 12:29 UTC (reported duration: 7 min); performance was stable, with continued monitoring planned.
- OutageMajor incident
WixRESOLVED: Issue affecting multiple services
Wix reported a major outage affecting some website owners across My Sites, Side Menu, Sign-In, Site Dashboard, Wix Editor, Wix Studio and Studio Workspace. It started at 2026-02-26 10:51 UTC and was resolved at 2026-02-26 11:28 UTC, lasting 36 min. Wix reported implementing a fix but did not state a cause.
- OutageCritical incident
StatuspageIssues displaying system metrics
Statuspage reported a critical incident affecting system metrics display, including Custom, Datadog, New Relic and Pingdom integrations. It started 2026-02-26 06:18 UTC and was resolved 2026-03-13 18:27 UTC, lasting 15 days 12 h. A fix was reported complete for all customers on 02-27 07:50 UTC, before formal resolution.
- OutageCritical incident
Census reported a critical outage affecting the Census Sync Management UI from 2026-02-26 00:28 UTC to 2026-02-26 00:32 UTC, lasting 4 min. The vendor attributed the issue to a configuration change and resolved it by reverting that change.
Wednesday, February 25
3 incident changes
- OutageCritical incident
Hex projects were not loading on the Main site during a critical incident from 2026-02-25 22:49 UTC to 2026-02-25 23:44 UTC, lasting 55 min. A fix was implemented by 2026-02-25 23:27 UTC, with systems recovering before resolution.
- DegradationMajor incident
RunwayWe've identified a problem and are working on a fix
Runway reported a major degradation affecting App, Backend, and Public API, with increased queue wait times and generation submission issues. It started at 2026-02-25 19:43 UTC and was resolved at 2026-02-25 20:16 UTC, lasting 32 min. Runway released a fix; delayed requests were expected to resume processing, and failed submissions could be retried.
- OutageMajor incident
AssemblyAINegative Balance Error
AssemblyAI reported a major billing incident: a small number of accounts received negative balances via the API, preventing transcription requests from completing. It ran from 2026-02-25 19:39 UTC to 2026-02-25 21:34 UTC (1 h 55 min). AssemblyAI attributed it to an unintentional error during its ongoing billing system migration, rolled out a fix, and confirmed resolution.