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.
Tuesday, March 24
7 incident changes
- DegradationMajor incident
RipplingData features degraded
Rippling reported major degradation affecting Reports, Transformations, and AI assistant deep data answers, starting at 2026-03-24 23:18 UTC. The team identified the issue and implemented a fix; services were reported recovered at 2026-03-25 00:33 UTC, and the incident was resolved at 2026-03-25 00:42 UTC, with a computed duration of 1 h 23 min.
- OutageMajor incident
CloudinaryManagement of API credentials is currently experiencing issues
Cloudinary reported a major incident affecting displaying/creating API secrets in the Management Console from 16:23 UTC (logged 2026-03-24 16:51 UTC); API credential usage remained functional. A fix was deployed at 18:18 UTC, and resolution was confirmed at 2026-03-24 19:35 UTC; the recorded duration was 2 h 43 min.
- OutageMajor incident
AshbyAI Notetaker Unavailable Due to Upstream Provider
Ashby's AI Notetaker had a major outage: the Meeting Bot failed to join interviews. The incident started at 2026-03-24 15:43 UTC and was resolved at 2026-03-24 18:51 UTC, lasting 3 h 7 min; the title attributed the outage to an upstream provider, but no specific fix was stated.
- OutageCritical incident
GrainFailure to start recordings
Grain Recorder had a critical outage affecting new bot recordings and local capture, starting 2026-03-24 15:32 UTC and resolved at 2026-03-24 19:58 UTC after 4 h 25 min. Grain attributed failures to an upstream provider outage and switched regions; instability ended, but cleanup of captured, unprocessed recordings was still underway.
- OutageMajor incident
SmartsheetUser & Group Management
Smartsheet reported a major outage causing blank results or infinite loading on Admin Center User & Group Management pages. The recorded incident ran from 2026-03-24 15:16 UTC to 2026-03-24 18:30 UTC (3 h 13 min); the postmortem cited a shared-interface loading-indicator update as the cause. A fix restored stability; browser refresh or cache clearing might be necessary.
- DegradationMajor incident
AshbyCandidates Scheduled with Unavailable Interviewers
A bug displayed incorrect interviewer availability for some organizations using Google Workspace, allowing candidates to book already-busy interviewers. Ashby rated the degradation major; the record starts and resolves at 2026-03-24 15:00 UTC (computed duration: 0 min), although updates describe affected periods on March 24 and March 25–27.
- DegradationMajor incident
LightdashIntermittent API errors across US
Lightdash Cloud (US) experienced intermittent API request failures with major impact from 2026-03-24 10:35 UTC to 2026-03-24 12:19 UTC, lasting 1 h 43 min. Outbound connections exceeded cloud networking capacity, dropping requests; Lightdash restructured its internal network architecture to reduce outbound connection load and reported all services healthy after deploying the fix.
Monday, March 23
4 incident changes
- OutageMajor incident
GreenhouseHarvest API Issues on Silo 101
Some customers on Silo 101 were unable to connect to the Greenhouse Harvest API in a major-impact incident starting 2026-03-23 19:38 UTC and lasting 1 h 56 min. Greenhouse implemented a fix at 2026-03-23 19:42 UTC and resolved the incident at 2026-03-23 21:35 UTC.
- OutageMajor incident
KeeperResolved: KeeperPAM Connection Errors in US Data Center
KeeperPAM connection errors in the US Data Center caused a major incident starting 2026-03-23 17:07 UTC, lasting 4 h 37 min and resolving at 2026-03-23 21:45 UTC. Keeper implemented a fix; its postmortem identified a low-level concurrency bug in the Keeper EPM service causing request failures under high simultaneous load and instability in ECS services.
- OutageMajor incident
StitchStitch API calls to Meta for data are interrupted
Stitch reported a major outage interrupting API calls to Meta for data, affecting api.stitchdata.com and app.stitchdata.com. It started at 2026-03-23 08:30 UTC and was resolved at 2026-03-23 12:16 UTC, lasting 3 h 45 min. Stitch reported a fix at 08:56 UTC and monitored results before resolution.
- OutageMajor incident
Sunday, March 22
3 incident changes
- OutageCritical incident
CanvaSome users may encounter issues loading Canva.
Some users had trouble loading Canva, and opening designs could return a 503 error; Canva rated the impact critical. The incident ran from 2026-03-22 21:57 UTC to 2026-03-22 23:09 UTC, lasting 1 h 11 min. Canva reported applying a fix at 22:44 UTC and later confirmed resolution.
- DegradationMajor incident
CodecovCoverage notifications delayed
Codecov reported delayed coverage notifications with major impact, starting 2026-03-22 14:07 UTC and resolved at 2026-03-23 07:03 UTC after 16 h 55 min. A fix was implemented and monitored; no cause was stated.
- OutageMajor incident
SanityElevated error rates on the Asset CDN
Sanity reported a major Asset CDN (cdn.sanity.io) incident causing elevated image-request 5xx errors for some customers from 12:47 UTC. The incident was logged at 2026-03-22 13:58 UTC and resolved at 2026-03-22 16:42 UTC, with a recorded duration of 2 h 43 min. A fix was implemented at 14:48 UTC.
Saturday, March 21
1 incident change
- OutageCritical incident
SnowflakeAWS - US West (Oregon): INC0154019
Snowflake reported a critical outage in AWS - US West (Oregon), potentially preventing sign-ins, queries, and data management. The vendor reported onset at 05:31 UTC March 21, 2026; the archived duration was 34 min, with resolution at 2026-03-21 07:12 UTC after Snowflake implemented a fix and confirmed service restoration.
Friday, March 20
6 incident changes
- OutageMajor incident
Google Workspace**Summary** We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser. **Description** The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific. **Customer Symptoms** Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. **Workaround** Users are able to use Google Keep via the Android or iOS mobile app.
- DegradationMajor incident
AmplitudeExperiment Management API Degradation
Amplitude’s Experiment Flags Management API (/api/1/flags) returned incomplete or empty flag listings; UI flags and /api/1/experiments were unaffected. The major incident started 2026-03-20 17:31 UTC, with symptoms reported since 16:00 UTC; it lasted 2 h 28 min and resolved at 2026-03-20 20:00 UTC after a verified fix.
- DegradationMajor incident
GorgiasAI Agent and Automation analytics are delayed
Gorgias reported a major incident delaying AI Agent and Automation analytics, affecting AI Agent and Automate - AI Agent. It started at 2026-03-20 15:55 UTC and was resolved at 2026-03-20 19:22 UTC, lasting 3 h 26 min; no cause or fix was stated.
- OutageMajor incident
- OutageMajor incident
Box[Medium] Issues with Logins, Folder and File Preview, and Shared Links
Box reported a major incident affecting Login/SSO, folder and file preview, and shared links; customers could encounter blank pages. It ran from 2026-03-20 03:37 UTC to 2026-03-20 05:08 UTC, lasting 1 h 31 min. Box implemented a fix and confirmed all affected services were restored.
- OutageMajor incident
DiscordFailure to start new voice calls
Discord reported a major incident preventing new voice calls from being created, from 2026-03-20 02:47 UTC to 2026-03-20 05:56 UTC, lasting 3 h 9 min. A fix was implemented by 2026-03-20 05:43 UTC, and the incident was resolved.
Thursday, March 19
7 incident changes
- OutageMajor incident
MailgunElevated 401 errors in US Region
Mailgun reported a major incident affecting API and Email Services - API in the US region, where some requests incorrectly failed with 401 errors. It started at 2026-03-19 18:43 UTC and lasted 10 min, resolving at 2026-03-19 18:53 UTC after a fix was deployed and systems returned to normal.
- OutageMajor incident
MongoDB AtlasIssue querying Azure blob storage containers in Atlas Data Federation
MongoDB Atlas reported a major incident affecting Atlas Data Federation reads from customer Azure blob storage containers, starting 2026-03-19 18:11 UTC. A fix was implemented at 19:01 UTC, and the incident was resolved at 2026-03-19 19:19 UTC after 1 h 8 min.
- OutageMajor incident
LaunchDarklyServer-side streaming rejected new connections across all commercial regions
LaunchDarkly reported a major incident affecting new server-side SDK streaming connections across all commercial regions, causing 500/503 errors. Start and resolution were both recorded as 2026-03-19 16:58 UTC, with a computed duration of 0 min. The vendor reported deploying mitigation.
- OutageMajor incident
CloudinaryErrors with Account Creation
Cloudinary reported a major Management Console incident affecting account sign-ups from 2026-03-19 16:48 UTC to 2026-03-19 18:38 UTC, lasting 1 h 50 min. A fix was deployed by 03-19 17:13 UTC; Cloudinary confirmed resolution and normal service at the end of the incident.
- OutageMajor incident
MongoDB AtlasMongoDB Atlas: Clusters page failing to load
MongoDB Atlas reported a major incident where affected users could see a blank Clusters page; cluster health was unaffected. It started at 2026-03-19 14:42 UTC and was resolved at 2026-03-19 15:28 UTC, lasting 45 min. A fix was implemented at 2026-03-19 15:17 UTC.
- OutageMajor incident
- DegradationMajor incident
DatadogIntermittent "No Data" Status for Monitors
Datadog reported a major incident where some metric monitors intermittently showed "No Data," primarily affecting distribution-metric monitors and making alerting potentially unreliable. It started at 2026-03-19 00:54 UTC and lasted 1 h 59 min, resolving at 2026-03-19 02:53 UTC; a fix was implemented.
Wednesday, March 18
12 incident changes
- OutageMajor incident
StatsigRegional Issue for Statsig Console
Statsig reported a major regional incident limiting Console access for some customers and affecting Console API, starting 2026-03-18 21:25 UTC and resolved at 2026-03-18 22:05 UTC (40 min). The Console was repaired before Console API finished recovering. SDK and API usage remained unaffected; values, exposures, and events continued processing.
- DegradationMajor incident
- OutageCritical incident
HoneycombHoneycomb UI displaying an error
Honeycomb reported a critical incident affecting ui.honeycomb.io - US1 App Interface, with the UI displaying an error. It started at 2026-03-18 18:07 UTC and was resolved at 2026-03-18 18:18 UTC, lasting 11 min; Honeycomb said it identified the issue and shipped a fix.
- OutageMajor incident
Box[Medium] Customers may experience issues previewing files
Box reported a major-impact incident affecting file previews for some users, starting at 2026-03-18 18:00 UTC and marked resolved at the same time (computed duration: 0 min). Box stated that no further impact was observed.
- OutageMajor incident
SquarespaceSite Loading Issues
Squarespace reported a major Site Loading outage: errors and delays prevented sites from loading properly from 2026-03-18 15:38 UTC to 2026-03-18 16:56 UTC, lasting 1 h 18 min. A fix was implemented at 03-18 16:28 UTC, and the incident was subsequently resolved.
- OutageMajor incident
CockroachDBCloud Console Social Login Auth Unavailable
CockroachDB reported a major Cloud Console outage affecting social login for customers using personal/non-SSO Microsoft accounts. It started at 2026-03-18 15:23 UTC and was resolved at 2026-03-18 16:02 UTC, lasting 39 min; Microsoft social login was restored.
- OutageMajor incident
GreenhouseInterview Scheduling Errors
Greenhouse reported a major incident causing interview scheduling errors for some users, starting 2026-03-18 15:19 UTC and resolved 2026-03-18 17:04 UTC; the reported duration was 1 h 44 min. A fix was applied at 03-18 15:44 UTC, followed by monitoring; no cause was stated.
- OutageMajor incident
HootsuiteBluesky authorization issues
Hootsuite reported a major incident in its Web Application: users could encounter generic "500" errors when adding or reconnecting Bluesky accounts. It started at 2026-03-18 14:12 UTC and was resolved at 2026-03-18 15:12 UTC, lasting 1 h 0 min; Hootsuite confirmed success rates returned to normal.
- DegradationMajor incident
- OutageCritical incident
Brex’s Dashboard was down in a critical-impact incident that started at 2026-03-18 12:24 UTC and was resolved at 2026-03-18 13:40 UTC, lasting 1 h 15 min. Customers could not access the Dashboard; Brex reported resolution but provided no cause or fix details.
- DegradationCritical incident
JiraAutomations aren't triggering on work item creation, field updates, or comment additions
Jira reported critical delays in event-triggered automations for some Cloud customers starting 2026-03-18 11:29 UTC, lasting 16 h 38 min until resolution at 2026-03-19 04:08 UTC. Scheduled, manual, and incoming-webhook triggers operated normally; historical-event replays remained underway for some high-volume customers at resolution. The postmortem attributed the incident to an internal configuration change.
- DegradationMajor incident
StatsigClient SDK Success Rate in Southeast Asia
Statsig reported a major degradation in client SDK initialization success rates affecting Asia Southeast 1 and Config Delivery API - Asia Southeast 1. It started at 2026-03-18 01:50 UTC and was resolved at 2026-03-18 02:53 UTC, lasting 1 h 3 min; the vendor said it identified the root cause but did not disclose it.
Tuesday, March 17
7 incident changes
- OutageMajor incident
Braze reported a major US05 Dashboard outage affecting users’ ability to reach the dashboard, starting 2026-03-17 20:49 UTC and resolved at 2026-03-17 21:04 UTC (15 min). Engineers implemented a fix; messaging sending and other services were not impacted.
- DegradationMajor incident
- OutageMajor incident
WorkOS reported a major incident involving elevated API errors and latency affecting AuthKit, Core Services - AuthKit, Core Services - SSO, and SSO. It started at 2026-03-17 14:12 UTC and was resolved at 2026-03-17 14:30 UTC, lasting 18 min; services were reported back to normal at 14:27 UTC.
- OutageMajor incident
- OutageMajor incident
- OutageMajor incident
- OutageMajor incident
Monday, March 16
3 incident changes
- OutageMajor incident
KeeperResolved: KeeperPAM Connection Errors in US Data Center
KeeperPAM customers with connections and tunnels enabled experienced sporadic errors after login in the US Data Center; vault login was unaffected. Keeper rated the incident major, starting 2026-03-16 18:25 UTC and resolving 2026-03-16 18:52 UTC (26 min). The stated cause was a communication issue with the KeeperPAM router endpoint.
- DegradationMajor incident
- OutageMajor incident
Drata reported a major Guest Admin Access outage affecting Guest Admins’ ability to view clients within "Business Accounts". It started at 2026-03-16 16:55 UTC and was resolved at 2026-03-16 19:16 UTC, lasting 2 h 20 min. Drata released an update and stated that Guest Admins should now be able to view clients as expected.