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.
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
11 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.
- OutageMajor incident
- OutageCritical incident
StatsigStatsig Console Availability
Statsig Console (console.statsig.com) was unavailable starting 2026-02-25 19:11 UTC for 5 min, with vendor-rated critical impact. The incident was resolved at 2026-02-25 19:16 UTC; functionality was fully restored, and the team was investigating the root cause.
- DegradationMajor incident
MailgunIntermittent Email Validation Errors
Mailgun reported intermittent email validation errors with major impact affecting API and Email Validation components from 2026-02-25 19:10 UTC to 2026-02-25 21:45 UTC, lasting 2 h 35 min. A fix was implemented by 02-25 21:36 UTC, and the incident was resolved.
- DegradationCritical incident
Omni AnalyticsSlowness detected in Omni
Omni Analytics reported critical Omni App slowness and occasional errors affecting EastUsa and Ireland, starting 2026-02-25 18:44 UTC and lasting 38 min until resolution at 2026-02-25 19:22 UTC. A recent change caused performance degradation; the team rolled back to a previous deployment, and all systems returned to operational status.
- OutageCritical incident
Codeiumand WindsurfNetworking Issues effecting Tab
Codeium reported critical networking issues affecting Windsurf Tab from 2026-02-25 16:23 UTC to 2026-02-25 17:29 UTC, lasting 1 h 6 min. A fix was implemented by 2026-02-25 17:01 UTC, and the incident was resolved after monitoring.
- OutageMajor incident
Box[Medium] Customers may experience issues with Uploads and Downloads for the UK zone
Box reported a major-impact incident affecting uploads and downloads for Box Zones UK customers, starting 2026-02-25 13:00 UTC and resolving 2026-02-25 14:16 UTC (1 h 16 min). Box reported remediation steps and restored full functionality, but did not specify the underlying cause or fix.
- DegradationMajor incident
RetoolIntermittent failures with Google Sheets, MySQL, and PostgreSQL integrations
Retool reported a major incident involving intermittent failures and elevated error rates in Google Sheets, MySQL, and PostgreSQL integrations, affecting Resource Queries and Workflows, while stating all query operations continued functioning. It lasted 12 h 46 min, from 2026-02-25 05:08 UTC to 2026-02-25 17:54 UTC; Retool confirmed affected resources were operational at resolution.
- OutageMajor incident
ConfluentSome Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates
Confluent reported a major incident involving elevated error rates for some Confluent Cloud customers in GCP us-south1, with single zone clusters in us-south1 Zone-a impacted. It started 2026-02-25 05:01 UTC and was resolved 2026-02-27 18:16 UTC, lasting 2 days 13 h. GCP identified the issue; a fix was implemented and monitored.
Tuesday, February 24
10 incident changes
- DegradationCritical incident
Box[Critical] Issue with Box API
Box reported a critical degradation affecting Box Platform / API - Content API, starting 2026-02-24 23:32 UTC and resolved 2026-02-25 00:15 UTC (43 min). Box said remediation steps improved the API and confirmed full functionality after monitoring; no specific cause or fix was disclosed.
- OutageCritical incident
BrexSevere latency in authz choking up most services
Brex reported a critical incident involving severe authz latency affecting most services, starting at 2026-02-24 20:21 UTC and resolved at 2026-02-24 21:16 UTC; the computed duration was 54 min. A fix was deployed at 20:25 UTC, after which errors appeared to recover.
- DegradationMajor incident
IterableEmail send delays for some US-hosted SparkPost traffic
Iterable reported a major degradation in Global Campaign Sends: US-hosted customers using SparkPost experienced email delays from elevated 5xx errors and Transmissions API latency. It started at 2026-02-24 19:51 UTC and resolved at 2026-02-24 19:52 UTC, lasting 1 minute. EU-hosted traffic and other ESPs were unaffected; SparkPost’s API issue was resolved.
- DegradationMajor incident
- OutageMajor incident
Iterableapp.iterable.com was unavailable in the US region, returning 502 Bad Gateway errors to users.
Iterable reported a major US-region outage of app.iterable.com affecting web and API access with elevated 502, 503, and 504 errors; EU users were unaffected. It started at 2026-02-24 18:18 UTC and was resolved at 2026-02-24 18:30 UTC (computed duration: 11 min), after a fix was implemented and traffic fully restored.
- OutageCritical incident
Box[Critical] Issues with Multiple Box Services
Box reported a critical outage affecting Box Sign, Login/SSO, and Uploads/Downloads, including in the Box Web Application. It started at 2026-02-24 14:59 UTC and was resolved at 2026-02-24 16:07 UTC, lasting 1 h 8 min; Box reported taking remediation steps and restoring full functionality.
- OutageCritical incident
MakeWeb application not loading
Make reported a critical web-access outage across eu1.make.celonis.com, eu1.make.com, eu2.make.com, us1.make.celonis.com, us1.make.com and us2.make.com starting 2026-02-24 10:45 UTC, lasting 28 min until resolution at 2026-02-24 11:13 UTC. Websites were accessible again at 10:49 UTC; scenarios and hooks remained unaffected.
- OutageMajor incident
WorkOS reported a major incident affecting AuthKit and Core Services - AuthKit, with elevated API errors and latency from 2026-02-24 10:11 UTC to 2026-02-24 11:16 UTC, lasting 1 h 5 min. The team identified the issue and implemented a fix; all services returned to normal.
- OutageMajor incident
- OutageMajor incident
QuickBooks OnlineUnable to use multiple features in QuickBooksOnline
QuickBooks Online reported a major outage affecting company settings, product/service tables, tax calculations and transaction saving across APAC, Canada, EMEA, LATAM and United States. It started at 2026-02-24 03:35 UTC and was resolved at 2026-02-24 08:36 UTC, lasting 5 h 1 min; a fix was implemented and all systems returned to normal.
Monday, February 23
3 incident changes
- OutageMajor incident
Pinecone[GCP][us-central1][europe-west4] Errors on some read operations
Pinecone reported a major incident causing errors on some read operations for Serverless Indexes in GCP us-central1 and europe-west4. It started at 2026-02-23 23:14 UTC and was resolved at 2026-02-24 01:52 UTC, lasting 2 h 38 min. Pinecone linked the impact to a Google Cloud Storage incident (Event ID: WDVVRMB) and reported implementing a fix.
- OutageMajor incident
SecureframeSecureframe Agent - UK - syncs are not working
Secureframe Agent syncs in the UK were not working in a major-impact outage that started at 2026-02-23 19:03 UTC and was resolved at 2026-02-23 22:19 UTC, lasting 3 h 15 min. Secureframe reported working on remediation but did not state a cause or specific fix.
- OutageMajor incident
MuxDirect upload failures and playback failures for some customers
Mux reported a major Mux Video - VOD outage affecting direct uploads and causing a low number of playback failures for some customers; URL based ingest was unaffected. It started at 2026-02-23 14:28 UTC and lasted 1 h 29 min, resolving at 2026-02-23 15:57 UTC. Mux reported implementing a fix at 14:47 UTC.
Sunday, February 22
2 incident changes
- OutageCritical incident
- OutageCritical incident
SmartsheetPROD-AU home not loading
Smartsheet’s critical PROD-AU outage made the Australia-region web app inaccessible after login, from 2026-02-22 12:17 UTC to 2026-02-22 14:45 UTC (2 h 27 min). The postmortem attributed it to an incorrect session-cookie validation configuration deployed to address performance; mitigation used a feature flag to reroute traffic.
Saturday, February 21
1 incident change
- DegradationMajor incident
TrelloTrello Slow or down for users
Trello reported a major incident involving intermittently dropping websocket connections, disrupting users’ active sessions. It started and was marked resolved at 2026-02-21 15:32 UTC, with a recorded duration of 0 min; the updates did not state a cause or completed fix.
Friday, February 20
5 incident changes
- OutageCritical incident
AirtableAirtable service interruption
Airtable reported a critical service interruption affecting availability, with some bases unreachable and features broken during recovery. It started at 2026-02-20 18:44 UTC and was resolved at 2026-02-21 01:27 UTC, lasting 6 h 43 min. Airtable implemented a fix and confirmed service was back to normal.
- OutageMajor incident
Bunny.netDisk Failure in Frankfurt
Bunny.net reported a major Edge Storage outage in Frankfurt starting 2026-02-20 16:13 UTC, lasting 2 days 2 h and resolved at 2026-02-22 19:11 UTC. One German storage server was affected, potentially causing isolated Storage API and CDN timeouts where replication was disabled or assets were uncached; Bunny.net confirmed normal service restored.
- OutageMajor incident
PostmanPostman Collections not working in EU region
Postman reported a major outage affecting Collection operations in the EU region, with Europe - Postman API and Postman API listed as affected components. It started at 2026-02-20 12:59 UTC and was resolved at 2026-02-20 13:13 UTC, lasting 13 min; Postman confirmed Collections in EU were fully working again.
- OutageMajor incident
- DegradationMajor incident
Thursday, February 19
3 incident changes
- OutageMajor incident
ConfluenceDisrupted availability of Confluence Cloud in several regions
Confluence Cloud reported a major partial service disruption affecting View Content for some customers in AP South, APSE, APSE2, East, and Central. The incident started at 2026-02-19 15:44 UTC and was resolved at 2026-02-19 17:47 UTC, with a reported duration of 2 h 2 min; service returned to normal for all affected customers.
- OutageMajor incident
Monday.comIssues scrolling down in the item page overview/updates section
Monday.com reported a major incident affecting scrolling in the item page overview/updates section, impacting Communication and EU - Communication. It started at 2026-02-19 10:23 UTC and was resolved at 2026-02-19 12:35 UTC, lasting 2 h 12 min. The vendor said it identified the root cause but did not describe it or the fix.
- DegradationMajor incident
CodecovUpload Processing Queue Slowdown
Codecov reported a major coverage-report processing slowdown starting 2026-02-19 03:00 UTC: a queue backlog delayed results, but uploads remained accepted and no data was lost. It is marked resolved at 2026-02-19 03:00 UTC (computed duration: 0 min); an update stated the issue was identified and patched, with monitoring continuing.