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, January 21
4 incident changes
- 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
2 incident changes
- DegradationMajor incident
- DegradationMajor incident
Monday, January 12
11 incident changes
- OutageMajor incident
SurveyMonkeyRespondents cannot progress past a matrix question where 'Number of rows respondents must answer:' is set to 'All'
SurveyMonkey reported a major outage on some surveys: respondents could not progress past matrix questions with 'Number of rows respondents must answer:' set to 'All'. The incident started at 2026-01-12 23:47 UTC and lasted 40 min, resolving at 2026-01-13 00:27 UTC; a fix was implemented at 2026-01-13 00:19 UTC.
- OutageMajor incident
PipedreamPipedream and Pipedream Connect Event Sources and Webhooks are failing
Pipedream reported a major outage affecting Pipedream and Pipedream Connect Event Sources and Webhooks, disrupting HTTP event sources, HTTP workflows, destinations and Connect. It started at 2026-01-12 23:31 UTC and resolved at 2026-01-13 00:51 UTC, lasting 1 h 19 min. Pipedream implemented a fix but did not disclose the cause.
- OutageMajor incident
StatsigSuccess Rate drop for US East Region
Statsig reported a major outage affecting Config Delivery API - US East 1 and Log Event API, US East 1, with elevated errors for initialize and event logging traffic. It started at 2026-01-12 20:30 UTC and was resolved at 2026-01-12 22:24 UTC, lasting 1 h 54 min; no cause or fix was stated.
- OutageMajor incident
JiraDisrupted create and view issue for some customers
Jira reported a major partial service disruption affecting issue creation, viewing, editing, and board viewing for some customers. It started at 2026-01-12 18:23 UTC and was resolved at 2026-01-12 23:45 UTC, lasting 5 h 21 min; Jira confirmed services were operating normally for all impacted customers.
- OutageMajor incident
- OutageMajor incident
New RelicData and UI Irregularities - US and EU regions
New Relic reported a major US and EU incident causing NRDB timeouts/query lag, data ingestion errors, real-time data viewing issues, and delayed or missing alert notifications. It started at 2026-01-12 15:21 UTC and was resolved at 2026-01-12 18:10 UTC; New Relic reported recovery following mitigating actions and resolution of two concurrent ingestion and query service interruptions.
- OutageCritical incident
- OutageMajor incident
- DegradationMajor incident
KlaviyoIssues with Campaign Sending and Scheduling
Klaviyo reported a major campaign scheduling and sending incident starting 2026-01-12 11:12 UTC, lasting 1 h 10 min and resolved at 2026-01-12 12:23 UTC. New campaigns and scheduled RAST campaigns could not send; previously scheduled non-RAST campaigns continued processing. A fix restored service and all delayed campaigns were replayed; no data loss was expected.
- OutageMajor incident
SquarespaceConnectivity issues - 503 errors
Squarespace sites experienced connectivity issues and 503 errors affecting Site Loading, with a major impact level. The incident started at 2026-01-12 11:05 UTC and was resolved at 2026-01-12 11:27 UTC, lasting 22 min; no cause or fix was stated.
- OutageMajor incident
Friday, January 9
8 incident changes
- OutageMajor incident
PendoPendo Chatbot not operational in the Resource CenterEvent
Pendo’s Resource Center Chatbot was not operational in a major-impact incident affecting AU, EU, US1 and US environments. It started at 2026-01-09 20:46 UTC and resolved at 2026-01-09 21:18 UTC, lasting 31 min. Pendo attributed the disruption to Support Bot vendor latency and directed customers to its support request form until normal operation resumed.
- OutageMajor incident
Sigma ComputingChat Support experiencing 3rd party outageEvent
Sigma Computing’s major chat support outage ran from 2026-01-09 20:33 UTC to 2026-01-09 22:23 UTC, lasting 1 h 49 min. Third-party provider Intercom experienced an outage and reported implementing a fix; Sigma confirmed chat support was fully operational at resolution. Customers were directed to submit support tickets for urgent requests and warned of slower responses.
- OutageCritical incident
- OutageCritical incident
BrexExpense service unavailable
Brex’s Expense service was unavailable, affecting Spend Management, with impact rated critical. The incident started at 2026-01-09 19:43 UTC and was resolved at 2026-01-09 20:48 UTC, lasting 1 h 4 min. Brex reported a fix in place at 20:20 UTC but did not state a cause.
- DegradationMajor incident
SemgrepDegraded scan performance in CI and Semgrep Managed Scans
Semgrep reported major scan performance degradation in CI and Semgrep Managed Scans from 2026-01-09 17:02 UTC to 2026-01-09 23:27 UTC, lasting 6 h 25 min. Semgrep implemented several changes and reported recovery; at resolution, the system was stable and scans were executing normally.
- DegradationMajor incident
- OutageCritical incident
Box[Critical] Issues with Logins, Notes and API
Box reported a critical incident affecting Logins, Notes and API, recorded as starting 2026-01-09 07:14 UTC and resolved 2026-01-09 06:00 UTC. The resolution precedes the recorded start, so duration is unknown; Box stated there was no current impact.
- DegradationMajor incident
ConvexIntermittent increased error rates
Convex reported intermittent increased error rates to/from database affecting Free & Starter and Live Traffic - Database Services, with major impact. The incident started at 2026-01-09 00:51 UTC and was resolved at 2026-01-09 01:40 UTC, lasting 48 min; no cause or specific fix was stated.