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, March 5, 2025
2 incident changes
- OutageCritical incident
JFrogJFrog Cloud Platform Unavailable (UI only) For Some Customers Due to Login Issues
JFrog reported a critical UI-login outage for some customers in APAC - SouthEast1 (Singapore) - AWS, Europe - West2 (London) - GCP, and US - West (California) - Azure. It started 2025-03-05 13:49 UTC and was resolved at 2025-03-05 14:42 UTC (52 min); JFrog reported implementing a fix.
- DegradationMajor incident
OpsgenieEU OpsGenie API calls having intermittent routing issues
Opsgenie reported a major degradation: some calls to api.opsgenie.com/eu intermittently returned 404 errors ('no Route matched with those values'). It started at 2025-03-05 06:34 UTC and was resolved at 2025-03-05 07:24 UTC, lasting 50 min; api.eu.opsgenie.com and api.opsgenie.com (without /eu) were unaffected.
Monday, March 3, 2025
1 incident change
- DegradationMajor incident
RudderStackData loss of small percentage of warehouse events on free tier
RudderStack reported major-impact loss of a small percentage of free-tier warehouse events from 2025-03-03 09:00 UTC to 2025-03-03 10:00 UTC, lasting 1 h 0 min. The vendor attributed degraded performance, failing health checks and increased service restarts to custom configurations not restored during an internal database migration; it reported implementing a fix and resolved the incident.
Saturday, March 1, 2025
1 incident change
- OutageMajor incident
FrontElevated error rates for [office365] channels
Front reported a major Office 365 channel outage from 2025-03-01 21:14 UTC to 2025-03-01 22:32 UTC, lasting 1 h 17 min. An Office365 outage prevented user login and Front from sending and importing messages; Front later reported that Office appeared to have resolved the issue and was processing an import backlog before marking the incident resolved.
Friday, February 28, 2025
1 incident change
- OutageCritical incident
DremioDremio Cloud (US) is inaccessible
Dremio Cloud (US) was inaccessible during a critical outage from 2025-02-28 00:39 UTC to 2025-02-28 08:49 UTC, lasting 8 h 10 min. Dremio attributed the outage to an infrastructure issue affecting core services; all services were restored, with successful recovery of users’ projects reported.
Thursday, February 27, 2025
2 incident changes
- OutageMajor incident
DagsterDagster UI down for multiple users
Dagster reported a major Dagster Cloud UI outage affecting multiple users, starting 2025-02-27 10:52 UTC and resolved at 2025-02-27 11:29 UTC (37 min). A compute log download fault caused web-server timeouts; a fix restored access, while STDOUT/STDERR tabs remained temporarily disabled before later restoration. Agents, runs, and automations were unaffected.
- OutageCritical incident
Wednesday, February 26, 2025
2 incident changes
- OutageCritical incident
RootlySlack Outage (3rd Party) Impacting Rootly Slack App
A critical Slack outage disrupted Rootly Slack App slash commands, messaging and button interactions from 2025-02-26 16:06 UTC until resolution at 2025-02-26 20:42 UTC (4 h 35 min). Rootly modified retry logic; /rootly recovered, with scattered channel-creation delays remaining. Rootly On-Call and Web Platform were unaffected.
- OutageMajor incident
UnbouncePopups and Sticky Bars Not Loading
Unbounce’s Popups and Sticky Bars failed to appear when triggered during a major outage from 2025-02-26 00:40 UTC to 2025-02-26 02:51 UTC (2 h 10 min). Unbounce recommended pausing dependent campaigns; a fix was implemented and the cache cleared, with no further customer action needed after resolution.
Tuesday, February 25, 2025
1 incident change
- OutageCritical incident
GrammarlyGrammarly suggestions aren't available.
Grammarly suggestions were unavailable in a vendor-rated critical outage affecting the Editor, browser extension, and listed mobile and desktop integrations. It started at 2025-02-25 23:00 UTC and was resolved at 2025-02-26 00:00 UTC; the computed duration was 59 min. Grammarly reported implementing a fix and monitoring results, but did not state a cause.
Monday, February 24, 2025
3 incident changes
- OutageMajor incident
- OutageCritical incident
KeeperKeeper vault login errors - resolved
Keeper reported critical US-region login errors affecting Keeper Admin Console and Keeper Web Vault from 2025-02-24 04:48 UTC to 2025-02-24 05:05 UTC (16 min), recommending “work offline.” A backend API and resulting database query triggered high database load; service was resolved, with a permanent fix planned for Monday, Feb 24.
- OutageMajor incident
KeeperLogin errors in US region
Keeper reported a major incident involving login errors in the US region, affecting Keeper Admin Console (US) and Keeper Web Vault (US). It started at 2025-02-24 03:54 UTC and was resolved at 2025-02-24 04:28 UTC, lasting 34 min; no cause or specific fix was stated.
Saturday, February 22, 2025
2 incident changes
- OutageMajor incident
- OutageMajor incident
Omni AnalyticsIntermittent page errors on embedded dashboards
Omni Analytics reported a major incident in EastUsa: some customers saw error pages on a subset of embedded dashboards from 2025-02-22 00:28 UTC to 2025-02-22 01:50 UTC, lasting 1 h 22 min. A new route was not enabled in embedded contexts; Omni rolled back the change and noted a page refresh might be required.
Thursday, February 20, 2025
3 incident changes
- OutageMajor incident
FullStoryFullstory unavailable for some users
FullStory reported a major Fullstory Web Application outage affecting some users from 2025-02-20 21:05 UTC to 2025-02-20 21:22 UTC, lasting 17 min. Session capture was unaffected; FullStory rolled back changes it said caused the outage and confirmed normal operations.
- DegradationMajor incident
- DegradationMajor incident
Wednesday, February 19, 2025
1 incident change
- OutageMajor incident
GrammarlyIssues with writing suggestions and generative AI
Grammarly reported a major outage affecting some writing suggestions and generative AI features across Grammarly for Mac, Grammarly for Windows, and Grammarly's Browser Extension. It started at 2025-02-19 17:17 UTC and resolved at 2025-02-19 18:55 UTC, lasting 1 h 37 min. A fix was implemented at 18:34 UTC; no cause was stated.
Tuesday, February 18, 2025
3 incident changes
- OutageMajor incident
Lever reported a major Data API outage starting 2025-02-18 22:48 UTC, resolved at 2025-02-22 01:17 UTC (3 days 2 h). A short-term fix left intermittent issues; normal API use was reported on 02-19 17:22 UTC. The postmortem cited database replica issues and Lever Hire inaccessibility for approximately 50% of customers for a few hours.
- OutageCritical incident
LeverIntermittent issues impacting Lever Hire
Lever reported a critical incident affecting Lever Hire and the Lever API, with intermittent 500 errors and higher latency; database unavailability and replica issues made Hire inaccessible for approximately 50% of customers for a few hours. The incident started 2025-02-18 22:20 UTC and was resolved 2025-02-22 01:16 UTC, lasting 3 days 2 h.
- OutageMajor incident
Lever500 Error when accessing Lever platform
Lever reported a major outage affecting most North America customers, with 500 errors blocking access to Lever Hire from 2025-02-18 15:12 UTC until 2025-02-18 21:09 UTC (5 h 57 min). Lever implemented a fix; its postmortem cited an unavailable database instance and compounding database-replica issues.
Friday, February 14, 2025
2 incident changes
- DegradationMajor incident
Omni AnalyticsIntermittent errors
Omni Analytics reported a major incident affecting EastUsa, with intermittent errors in the web application and query execution from 2025-02-14 21:58 UTC to 2025-02-14 22:10 UTC (11 min). A network component upgrade caused intermittent connectivity problems; the change was rolled back and the incident resolved.
- OutageMajor incident
LatticeLattice pages are not loading
Lattice reported a major incident in which the application home page temporarily failed to load. It started at 2025-02-14 17:33 UTC and was resolved at 2025-02-14 17:41 UTC, lasting 8 min; Lattice stated that a fix was implemented.
Thursday, February 13, 2025
2 incident changes
- OutageMajor incident
- OutageMajor incident
Wednesday, February 12, 2025
2 incident changes
- OutageMajor incident
- OutageMajor incident
Pipedream reported major elevated error rates affecting HTTP and Timer event sources and workflows, including backend components. The incident started at 2025-02-12 04:41 UTC and was resolved at 2025-02-12 06:44 UTC, lasting 2 h 2 min; no cause or specific fix was stated.
Tuesday, February 11, 2025
2 incident changes
- DegradationMajor incident
Close reported a major incident affecting API, Application UI, and email/calendar syncing from 2025-02-11 22:31 UTC to 2025-02-11 23:34 UTC, lasting 1 h 2 min. Users experienced degraded performance and elevated errors; Close rolled out a fix, with UI/API performance recovering before delayed syncing was fully resolved.
- OutageCritical incident
GrammarlyGrammarly is experiencing temporary service interruption.
Grammarly reported a critical outage affecting Account Management, Grammarly Editor, Grammarly for Mac, Grammarly for Windows, Grammarly's Browser Extension, and Login; products were temporarily unavailable. It started at 2025-02-11 20:39 UTC and lasted 1 h 47 min, resolving at 2025-02-11 22:26 UTC. A fix was implemented at 21:18 UTC; no cause was stated.
Monday, February 10, 2025
2 incident changes
- OutageMajor incident
KeeperLogin errors in US region
Keeper reported a major US-region login outage affecting Keeper Admin Console (US) and Keeper Web Vault (US), starting 2025-02-10 17:30 UTC and resolved at 2025-02-10 17:49 UTC (19 min). The postmortem attributed failed new login sessions to a database lock in the primary writer instance and said the issue resolved without intervention; a backend update was planned.
- OutageMajor incident
DremioQueries stuck in metadata retrieval in Dremio Cloud (EU)
Dremio Cloud (EU) queries stalled at metadata retrieval during a major incident from 2025-02-10 10:02 UTC to 2025-02-10 17:55 UTC (7 h 53 min), now resolved. Dremio reported upstream timeouts and queuing in a core indexing service, mitigated by throttling; initial analysis suggested a recent underlying infrastructure change on Google may have triggered the failure.
Saturday, February 8, 2025
1 incident change
- OutageMajor incident
Friday, February 7, 2025
1 incident change
- DegradationMajor incident
DagsterIssues with global op concurrency keys
Dagster reported a major API and Dagster Cloud UI degradation from 2025-02-07 15:37 UTC to 2025-02-07 16:11 UTC (34 min): some runs with concurrency keys lacking explicit configuration or a default limit were blocked, and concurrency settings had UI issues. Fixes restored progress, but previously blocked runs might still require manual termination.
Thursday, February 6, 2025
1 incident change
- DegradationMajor incident
HexInstability in project loads
Hex reported major instability in project loads affecting the Main site, starting 2025-02-06 19:39 UTC and resolved at 2025-02-06 21:29 UTC, lasting 1 h 49 min. Hex stated that a fix had been implemented and was being monitored at the start of the incident.
Wednesday, February 5, 2025
5 incident changes
- OutageMajor incident
CensusSome syncs failing with "Missing corresponding dataset file for prefix: record_deletes.0"
Census reported a major Sync Engine incident starting 2025-02-05 22:38 UTC: some syncs failed with "Missing corresponding dataset file for prefix: record_deletes.0" after a code change introduced a bug. A revert deployed at 22:56 UTC; the incident was resolved at 2025-02-05 23:30 UTC after over 30 minutes without errors, with a computed duration of 51 min.
- DegradationMajor incident
GrammarlyGenerative AI assistance is working with interruptions
Grammarly’s generative AI assistance experienced interruptions in a major-impact incident starting at 2025-02-05 21:05 UTC, lasting 22 min and resolved at 2025-02-05 21:28 UTC. Writing suggestions remained available; no cause or fix was stated.
- OutageCritical incident
HexProjects not loading for some users
Hex reported a critical Main site outage in which projects were not loading for some users, from 2025-02-05 19:03 UTC to 2025-02-05 19:53 UTC (50 min). A fix was implemented by 02-05 19:37 UTC, and the incident was resolved.
- OutageMajor incident
- OutageMajor incident
RudderStackGoogle Ads offline conversion destination got impacted.
RudderStack reported a major incident affecting Google Ads offline conversion destinations in US and EU regions after Google Ads API v16 deprecation, causing missing or delayed data. It started and resolved at 2025-02-05 13:00 UTC (reported duration: 0 min). Events were replayed to recover data, but customers without backups may still experience data loss.
Tuesday, February 4, 2025
1 incident change
- OutageMajor incident
Hex projects were not loading on the Main site in a major-impact outage starting 2025-02-04 22:52 UTC and lasting 37 min. A fix was implemented by 2025-02-04 22:56 UTC, and the incident was resolved at 2025-02-04 23:30 UTC.
Monday, February 3, 2025
2 incident changes
- OutageMajor incident
SubstackSubstack home page and app home tab errors
Substack reported a major incident affecting its website home page and app home tab, with increased errors and Notes missing from some users’ feeds. It lasted 1 h 24 min, from 2025-02-03 19:25 UTC to 2025-02-03 20:49 UTC; Substack restored feeds for all users and reported that error rates had subsided.
- OutageMajor incident
PendoPendo Feedback: Partial Front End Outage
Pendo Feedback experienced a partial front-end outage affecting Feedback - Feedback UI and Feedback UI, rated major by Pendo. It started at 2025-02-03 15:10 UTC and was resolved at 2025-02-03 15:30 UTC, lasting 20 min; no cause or fix was stated.
Friday, January 31, 2025
1 incident change
- OutageMajor incident
FireboltFirebolt V2 UI Experiencing Outage
Firebolt V2 UI access was down in a major incident starting 2025-01-31 00:23 UTC, resolved at 2025-01-31 01:29 UTC; the recorded duration was 1 h 5 min. Programmatic access could also be affected if a user token expired. Firebolt reported full operation restored at 01:15 UTC; no cause was stated.
Thursday, January 30, 2025
3 incident changes
- OutageCritical incident
Hex reported a critical web app outage affecting the Main site, starting 2025-01-30 17:10 UTC and resolved at 2025-01-30 17:56 UTC (computed duration: 45 min). A fix was implemented by 2025-01-30 17:21 UTC, followed by monitoring; no cause was stated.
- OutageCritical incident
Hex reported a critical Main site outage that prevented projects from loading, starting at 2025-01-30 14:35 UTC and resolved at 2025-01-30 15:55 UTC, lasting 1 h 20 min. Hex reported implementing a fix and monitoring results; no cause was stated.
- OutageCritical incident
CensusIP Address Change for Database Requests
Census reported a critical Sync Engine outage starting 2025-01-30 02:59 UTC: a networking misconfiguration sent database requests from unadvertised IPs, causing syncs to fail for customers whose databases rejected those IPs. Census rolled back to a previous configuration and resolved the incident at 2025-01-30 03:31 UTC; the reported duration was 31 min.
Wednesday, January 29, 2025
3 incident changes
- MaintenanceMajor incident
- OutageMajor incident
UpstashDisk failure in some Regional Databases
Upstash reported a major outage affecting database reachability in AWS US-EAST-1 and Redis Regional - AWS US-EAST-1. Recorded start and resolution: 2025-01-29 18:03 UTC (computed duration: 0 min); the update reports disk failure at 16:52 UTC and recovery at 17:13 UTC after restarting affected components, with no data lost.
- OutageCritical incident