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.
Monday, January 26
2 incident changes
- OutageMajor incident
- OutageMajor incident
Sunday, January 25
1 incident change
- OutageMajor incident
DiscordFailing message sends on some channels
Discord reported a major incident affecting API and Search, with message sends failing on some channels. It started at 2026-01-25 00:35 UTC and was resolved at 2026-01-25 06:04 UTC, lasting 5 h 29 min; no cause or fix was stated.
Saturday, January 24
1 incident change
- OutageMajor incident
StatsigIssues for Server SDKs in US-EAST and US-WEST
Statsig reported a major incident affecting Server SDK initialization and update syncing in US-EAST and US-WEST, with increased error rates on the Config Delivery API. It started at 2026-01-24 00:00 UTC and was resolved at 2026-01-24 01:23 UTC, lasting 1 h 23 min; no cause or fix was stated.
Friday, January 23
4 incident changes
- OutageCritical incident
Front reported a critical outage affecting the App and API and integrations, starting 2026-01-23 21:51 UTC and lasting 3 h 49 min until resolution at 2026-01-24 01:40 UTC. Application and API access were restored at 01-23 22:28 UTC; Front confirmed a fix was implemented but did not disclose the cause.
- OutageMajor incident
- DegradationCritical incident
MessageBird (Bird)High response times for analytics in US west
MessageBird (Bird) reported a critical degradation affecting Analytics - US (West) and CRM - Analytics - US (West), with high response times and problems viewing contacts and segments. It ran from 2026-01-23 07:08 UTC to 2026-01-23 11:31 UTC, lasting 4 h 23 min. A fix was implemented before resolution; no cause was stated.
- OutageMajor incident
Thursday, January 22
11 incident changes
- DegradationMajor incident
- DegradationMajor incident
BrexEmails to Microsoft inboxes are currently delayed
Brex reported major delays delivering emails to Microsoft-based addresses starting 2026-01-22 22:36 UTC. The incident lasted 17 h 37 min and was resolved at 2026-01-23 16:13 UTC, when Brex said timely delivery should have resumed; its email vendor had been investigating.
- OutageMajor incident
GrammarlyWe're experiencing a service interruption
Grammarly reported a major service interruption affecting Login, Writing Suggestions and other products, starting 2026-01-22 21:50 UTC and resolved 2026-01-24 01:10 UTC (27 h 19 min). A fix was implemented at 2026-01-22 23:03 UTC, but some users still could not access documents at app.grammarly.com during monitoring.
- OutageMajor incident
- OutageMajor incident
FrontMicrosoft Office365 Incident
A major Microsoft Office365 outage prevented affected Front customers from sending or receiving messages starting 2026-01-22 20:49 UTC. The incident lasted 8 h 46 min and was resolved at 2026-01-23 05:36 UTC; all pending messages were delivered, and Microsoft's remaining service degradation was no longer impacting Front.
- OutageCritical incident
DatadogWeb Application Not Loading
Datadog reported a critical web application outage from 2026-01-22 18:51 UTC to 2026-01-22 19:27 UTC, lasting 36 min; some users could encounter errors loading the application. Data processing and alerts were unaffected. A fix was implemented at 19:13 UTC, and the incident was resolved.
- OutageCritical incident
Asana reported a critical webapp outage across Australia, EU, Japan, Middle East and US, starting at 2026-01-22 17:48 UTC and resolved at 2026-01-22 19:00 UTC (1 h 12 min). The postmortem said the App and associated services were unavailable from 17:33 - 17:57 UTC after a code path overloaded a shared metadata database, causing queuing, timeouts and errors.
- OutageMajor incident
- OutageMajor incident
SegmentWe are observing elevated ETIMEDOUT errors from Yahoo DSP destination.
Segment reported a major incident affecting Yahoo DSP Streaming Destinations in EU and US, with elevated ETIMEDOUT and "504 - Gateway Time-out" errors. It started at 2026-01-22 13:33 UTC and resolved at 2026-01-22 17:37 UTC, lasting 4 h 3 min; Segment worked with Yahoo support and reported mitigation before resolution.
- OutageMajor incident
ContentfulManagement API Outage (EU)
Contentful reported a major Management API outage in the EU region, with elevated errors affecting Management API traffic. It started at 2026-01-22 12:41 UTC and was resolved at 2026-01-22 13:21 UTC, lasting 40 min; a fix restored normal operation by 12:57 UTC.
- OutageMajor incident
Wednesday, January 21
5 incident changes
- DegradationMajor incident
LeverAutomation Workflows Not Triggering
Lever reported a major incident affecting automation workflows in Global Data Center - LeverTRM - Hire, Hire: workflows were not triggering, then were confirmed to be processing with delays. The incident started at 2026-01-21 22:08 UTC and was resolved at 2026-01-22 16:04 UTC, lasting 17 h 56 min; no cause or specific fix was stated.
- OutageCritical incident
Windsurfand CodeiumWindsurf Outage (Cascade and Tab)
Windsurf reported a critical outage affecting Cascade and Tab, starting at 2026-01-21 19:30 UTC and resolved at 2026-01-21 19:30 UTC (computed duration: 0 min). The resolution update said Windsurf and Cascade were down for approximately 13 minutes; no cause or fix was stated.
- OutageMajor incident
RunwayIssues with Gemini 3 Pro image generations
Runway reported a major incident affecting Gemini 3 Pro image generations across App, Backend, and Public API. It started at 2026-01-21 15:53 UTC and was resolved at 2026-01-21 18:26 UTC, lasting 2 h 32 min; no cause or specific fix was stated.
- OutageMajor incident
SanityContent Agent and Canvas elevated error rate
Sanity reported a major incident affecting Content Agent and Canvas: elevated error rates caused some requests to fail, though retries sometimes succeeded. It started at 2026-01-21 14:53 UTC and was resolved at 2026-01-21 15:33 UTC, lasting 40 min. The upstream AI provider implemented a fix and recovered, returning error rates to normal.
- OutageMajor incident
GrammarlySupehuman Go and AI Chat experience temporary service interruption
Grammarly reported a major service interruption affecting Supehuman Go and AI Chat, with Generative AI assistance, Grammarly Editor, and Grammarly's Browser Extension listed as affected components. It started at 2026-01-21 00:40 UTC and was resolved at 2026-01-21 01:48 UTC, lasting 1 h 8 min; no cause or specific fix was stated.
Tuesday, January 20
8 incident changes
- OutageCritical incident
GrammarlyUsers encounter an error when creating or opening a document in Docs at https://app.grammarly.com/
Grammarly reported a critical Grammarly Editor outage: users encountered errors creating or opening documents in Docs at https://app.grammarly.com/. It started at 2026-01-20 21:57 UTC and was resolved at 2026-01-20 22:08 UTC, lasting 11 min; Grammarly said it identified the issue and was implementing a fix.
- OutageMajor incident
Coda reported a major site-wide outage affecting access to API, Doc List, Docs, Packs, and Published Docs. It started at 2026-01-20 21:34 UTC and was resolved at 2026-01-20 22:05 UTC, lasting 31 min; no cause or specific fix was stated.
- OutageMajor incident
SecureframeIssues with Google Workspace connections
Secureframe reported a major Web Application incident in which Google Workspace integrations were disconnected, starting 2026-01-20 16:59 UTC and lasting 7 h 1 min. A fix to automatically reconnect affected integrations was implemented and rolled out; the incident was resolved at 2026-01-21 00:00 UTC.
- OutageMajor incident
LeverIntermittent issues impacting candidate pipeline page
Lever reported a major incident causing intermittent 500 errors when accessing the candidate pipeline page in Global Data Center - LeverTRM - Hire, Hire. It started at 2026-01-20 16:52 UTC and was resolved at 2026-01-20 19:51 UTC, lasting 2 h 59 min. A fix was implemented; affected users required no action to restore functionality.
- OutageCritical incident
TypeformTypeform Builder - Can't create or edit typeforms
Typeform reported a critical Builder outage affecting users creating or editing typeforms. The incident started at 2026-01-20 14:57 UTC and was resolved at 2026-01-20 15:07 UTC, lasting 10 min; Typeform said a fix was implemented and a problem investigation would follow.
- OutageMajor incident
- OutageCritical incident
Matillion reported a critical Agent gateway outage affecting Agent Manager in the EU and US regions, causing validation and agent availability issues. It started at 2026-01-20 11:37 UTC and was resolved at 2026-01-20 11:55 UTC, lasting 17 min; no cause or fix was stated.
- OutageCritical incident
Monday, January 19
1 incident change
- OutageMajor incident
Aircall reported a major login outage affecting both Aircall Apps and Dashboard, starting at 2026-01-19 07:48 UTC and resolved at 2026-01-19 08:39 UTC, lasting 50 min. A fix was deployed by 08:07 UTC, and performance remained stable during monitoring.
Sunday, January 18
2 incident changes
- OutageMajor incident
- OutageMajor incident
SmartsheetErrors Accessing Smartsheet
Smartsheet reported a major outage affecting application access, loading and asset changes, including Sheets, Reports, Dashboards and login. The incident started at 2026-01-18 05:09 UTC and was resolved at 2026-01-18 05:36 UTC, with a computed duration of 26 min. Smartsheet said infrastructure changes led to gradual recovery; no cause was stated.
Saturday, January 17
1 incident change
- OutageMajor incident
Friday, January 16
2 incident changes
- OutageMajor incident
- OutageMajor incident
Thursday, January 15
8 incident changes
- OutageMajor incident
Bunny.netSingapore CDN & Storage Network Outage
Bunny.net reported a major Singapore CDN and Edge Storage outage starting 2026-01-15 22:28 UTC, resolved at 2026-01-15 22:58 UTC after 30 min. CDN traffic was re-balancing to other locations, while non-replicated Singapore storage was offline; a fix was implemented at 2026-01-15 22:39 UTC.
- OutageMajor incident
RipplingIssues approving timecards and loading schedules
Rippling reported a major Rippling App incident affecting timecard approvals and schedule loading, starting at 2026-01-15 15:50 UTC and lasting 2 h 23 min. A fix was implemented by 2026-01-15 17:09 UTC, and the incident was resolved at 2026-01-15 18:13 UTC.
- DegradationMajor incident
HoneycombIncreased Latency and Errors for Events Ingest
Honeycomb reported a major incident affecting some event ingest requests in the US, with increased latency and higher-than-normal error rates. It started and was resolved at 2026-01-15 15:46 UTC (recorded duration: 0 min); service stabilized and returned to normal, with monitoring continuing.
- OutageMajor incident
- DegradationMajor incident
SanityElevated API and API CDN errors and latency for some customers
Sanity reported a major incident affecting api.sanity.io and apicdn.sanity.io, with elevated errors, latency, and intermittent timeouts/errors on write operations and document retrieval for some customers. It started at 2026-01-15 12:23 UTC and was resolved at 2026-01-15 13:00 UTC, lasting 37 min; mitigations restored normal error rates.
- OutageMajor incident
Pinecone[Serverless][AWS][us-east-1] 5xx errors on read operations for some indexes
Pinecone reported a major incident causing 5xx errors on read operations for some Serverless indexes in AWS us-east-1. It started at 2026-01-15 12:12 UTC and was resolved at 2026-01-15 15:30 UTC, lasting 3 h 18 min. A fix was implemented by 2026-01-15 14:30 UTC; no cause was stated.
- OutageMajor incident
- OutageMajor incident
Wednesday, January 14
2 incident changes
- DegradationMajor incident
RipplingDegraded performance in Payroll
Rippling reported major degraded performance in its Payroll application starting 2026-01-14 20:54 UTC, lasting 3 h 19 min until resolution at 2026-01-15 00:13 UTC. A fix was implemented and monitoring began at 01-14 23:27 UTC.
- OutageMajor incident
RevenueCat reported a major API Uptime incident involving a spike in database-related errors from 2026-01-14 11:00 UTC to 2026-01-14 11:54 UTC, lasting 54 min. Fortress was enabled to mitigate errors, then disabled when the error rate returned to normal at 11:16 UTC; all Fortress receipts were replayed by resolution.
Tuesday, January 13
1 incident change
- DegradationMajor incident