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.
Thursday, March 5
5 incident changes
- DegradationMajor incident
- OutageMajor incident
Codeiumand WindsurfWe are investigating reports of completions/Tab not working
Codeium reported a major outage affecting Windsurf Tab completions starting 2026-03-05 16:23 UTC, lasting 1 h 22 min. A fix was implemented by 03-05 16:51 UTC, and the incident was resolved at 2026-03-05 17:46 UTC.
- OutageMajor incident
Sigma ComputingIssue with Burst email exports are resolved
Sigma Computing reported a major outage of Burst email exports starting 2026-03-05 10:10 UTC, lasting 4 days 7 h until resolution at 2026-03-09 17:31 UTC; standard exports remained operational. Engineers deployed a fix and re-enabled Burst Email Exports at 03-07 01:27 UTC, with no recurring problems observed during subsequent monitoring.
- OutageMajor incident
ConfluentMetrics API was experiencing failures from 03:23 UTC to 03:58 UTC
Confluent reported a major Confluent Cloud Metrics API outage, with unavailability from 2026-03-05 03:23 UTC to 2026-03-05 03:58 UTC. The incident record ran from 2026-03-05 04:40 UTC to resolution at 2026-03-05 07:22 UTC (2 h 42 min). Confluent reported mitigation and confirmed normal operation at resolution.
- OutageMajor incident
Some Discord guilds were unavailable in a major-impact incident that started at 2026-03-05 01:37 UTC and was resolved at 2026-03-05 01:58 UTC, lasting 20 min. Discord identified the issue and reported implementing a fix, but did not state a cause.
Wednesday, March 4
12 incident changes
- OutageMajor incident
Pinecone[Serverless][GCP][us-central1] 5xx errors on some read operations for some indexes
Pinecone reported a major incident causing 5xx errors on some read operations for some Serverless indexes in GCP us-central1. It started at 2026-03-04 21:06 UTC and was resolved at 2026-03-04 22:16 UTC, lasting 1 h 10 min. A fix was implemented; affected customers could encounter failed reads during the incident.
- DegradationMajor incident
- OutageMajor incident
Codeiumand WindsurfWe are investigating reports of completions/Tab not working
Codeium reported a major incident affecting Windsurf Tab completions, starting at 2026-03-04 20:16 UTC and resolved at 2026-03-04 20:54 UTC after 38 min. A fix was implemented at 20:17 UTC; no cause was stated.
- DegradationMajor incident
AshbyDelays in generating meeting transcripts
Ashby's AI Notetaker meeting transcript generation was delayed in a major-impact incident starting 2026-03-04 19:59 UTC and resolved at 2026-03-04 20:44 UTC, lasting 44 min. A fix was implemented at 20:31 UTC; no cause was stated.
- OutageMajor incident
- OutageCritical incident
BrexDashboard and mobile app are not loading
Brex’s dashboard and mobile app were not loading during a critical outage that started at 2026-03-04 19:38 UTC and was resolved at 2026-03-04 19:48 UTC, with a reported duration of 9 min. Brex said it identified the issue and applied a fix; no cause was stated.
- OutageMajor incident
UnbounceUnable to Connect Custom Domains
Unbounce reported a major outage preventing custom domain registration, attributed to a Cloudflare outage. It started at 2026-03-04 18:33 UTC and was resolved at 2026-03-05 00:32 UTC, lasting 5 h 59 min; Unbounce said a fix restored registration functionality.
- OutageCritical incident
Convexhigh error rates on customer backends
Convex reported a critical incident causing high backend error rates and downtime for some customers, affecting Free & Starter and Live Traffic database, function and Node.js runtimes. It started 2026-03-04 17:28 UTC and lasted 1 h 0 min. Convex remediated the issue and attributed it to a load spike triggering load-shedding and a caching-library panic.
- DegradationMajor incident
- OutageMajor incident
Windsurfand CodeiumNetworking issues effecting tab
Windsurf Tab experienced networking issues with major impact starting 2026-03-04 13:49 UTC. The incident lasted 3 h 32 min and was resolved at 2026-03-04 17:22 UTC; 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
9 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
- 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
1 incident change
- 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.