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, October 20, 2025
50 incident changes
- DegradationMajor incident
Convexnode actions intermittently unavailableEvent
Convex reported a major incident causing intermittent Node.js Runtime node action unavailability, attributed to AWS Lambda issues. It started at 2025-10-20 19:14 UTC and was resolved at 2025-10-21 03:39 UTC, lasting 8 h 24 min.
- OutageMajor incident
PusherUS3 cluster - major outageEvent
Pusher reported a major US3 outage affecting Channels presence channels, Channels REST API and Channels WebSocket client API, with latency, 503 errors and full service downtime. It started at 2025-10-20 18:36 UTC and resolved at 2025-10-20 20:41 UTC, lasting 2 h 5 min. The postmortem identifies Redis cluster startup failures; Pusher reported implementing a fix.
- OutageMajor incident
CodaAttachment and image processing delaysEvent
Coda reported a major outage delaying virus scanning and processing of uploaded images and attachments for document collaborators. Uploads were stored successfully. The incident started at 2025-10-20 18:09 UTC and was resolved at 2025-10-20 20:08 UTC, lasting 1 h 59 min; no cause or fix was stated.
- OutageMajor incident
PineconeSome users may be unable to access the Pinecone web console. All API services remain fully operational.Event
Some users could not access Pinecone’s web console during a major-impact outage; all API services remained fully operational. The incident started at 2025-10-20 17:43 UTC and was resolved at 2025-10-20 18:00 UTC, lasting 16 min. Pinecone reported implementing a fix and monitoring the results.
- DegradationMajor incident
PusherMT1 cluster - increased latencyEvent
Pusher reported major increased latency on Channels cluster `mt1`, affecting Channels Dashboard, Channels presence channels, Channels REST API and Channels WebSocket client API. It started at 2025-10-20 17:26 UTC and was resolved at 2025-10-21 07:14 UTC, lasting 13 h 48 min. Pusher attributed the latency to an external cloud-provider incident.
- OutageMajor incident
KeeperAWS outage affecting KeeperPAM connections and scheduled rotationsEvent
Keeper reported a major outage affecting KeeperPAM cloud connections, scheduled rotations and discovery operations due to an AWS outage in US-EAST-1. It started at 2025-10-20 17:25 UTC and was resolved at 2025-10-20 20:31 UTC, lasting 3 h 5 min; Keeper cleared the alert as most AWS services were restored.
- DegradationMajor incident
- OutageCritical incident
- OutageMajor incident
BrazeAWS US East 1 outageEvent
Braze reported a major AWS US East 1 outage starting 2025-10-20 16:21 UTC, resolved 2025-10-20 23:41 UTC. AWS capacity shortages delayed Data Processing and Outbound messaging on US03 and US05; affected Twilio services disrupted SMS authentication and messaging. Engineers load-balanced work and cleared backlogs; Twilio recovered.
- DegradationCritical incident
- OutageMajor incident
RudderStackIssues with python transformations in US.Event
RudderStack reported a major outage affecting Python Transformations in the US from 2025-10-20 15:32 UTC to 2025-10-20 21:51 UTC (6 h 18 min). The vendor attributed the issues to an ongoing AWS incident and limited AWS resources; increased EC2 instance launches restored capacity, and all backlog was cleared with no lingering customer impact reported.
- OutageCritical incident
VantaVanta web app loading issues (US region)Event
Vanta reported a critical outage affecting US-region web app loading, with slowness and errors across the platform attributed to the AWS US-East-1 outage. It started at 2025-10-20 15:25 UTC and was resolved at 2025-10-20 22:26 UTC, lasting 7 h 0 min; Vanta confirmed the web app was stable in all regions.
- DegradationMajor incident
- OutageMajor incident
Pulumi reported a major AWS outage affecting Deployments, Docs, and Registry, with intermittent documentation and registry loading errors for customers in the eastern United States. It started at 2025-10-20 15:05 UTC and resolved at 2025-10-21 03:26 UTC, lasting 12 h 20 min; Pulumi attributed the disruption to the global AWS outage and confirmed all impacted areas recovered.
- OutageMajor incident
LeverLever - Resume Parsing OutageEvent
Lever reported a major resume parsing outage starting 2025-10-20 14:54 UTC, with intermittent parsing disruptions attributed to the AWS outage and residual issues at its resume parsing vendor. The incident was resolved at 2025-10-21 12:08 UTC after 21 h 14 min; customers could encounter intermittent disruptions when parsing resumes during that period.
- OutageMajor incident
UpstashUpstash Console issuesEvent
Upstash reported a major incident affecting Console dashboard access and related operations, with Developer API (api.upstash.com) availability issues also reported. It started at 2025-10-20 14:52 UTC and was resolved at 2025-10-20 18:50 UTC, lasting 3 h 58 min. Upstash attributed the issues to an upstream cloud provider and deployed a workaround.
- OutageMajor incident
ConvexUsage info on Convex dashboard is unavailableEvent
Convex dashboard usage information could not be queried during a major incident starting 2025-10-20 14:48 UTC and resolved at 2025-10-20 22:00 UTC, lasting 7 h 11 min. Convex suspected a new round of AWS issues and later reported identifying the issue and implementing a fix.
- OutageCritical incident
Sprout SocialSprout Social OutageEvent
A critical outage affected the Sprout Social API and Web Application, causing navigation delays and login issues. It started at 2025-10-20 14:36 UTC and was resolved at 2025-10-21 13:23 UTC, lasting 22 h 46 min. Sprout attributed the outage to a wider AWS service issue and confirmed all services were restored.
- OutageMajor incident
CloseService interruptionEvent
Close reported a major service interruption affecting calling, including Outgoing Calls and Phone Service, from 2025-10-20 14:20 UTC to 2025-10-20 20:27 UTC (6 h 7 min). Close attributed the disruption to an AWS outage in an unspecified region that affected many services, including calling, and confirmed resolution.
- DegradationMajor incident
Omni AnalyticsQuery Execution Delays
Omni Analytics reported major query execution delays in EastUsa from 2025-10-20 14:20 UTC to 2025-10-21 00:18 UTC, lasting 9 h 58 min. Cloud-provider infrastructure issues caused a query backlog; rerunning queries did not speed execution. Omni added resources and confirmed stable service before resolving the incident.
- DegradationMajor incident
HoneycombDelays in SLO, Service Maps processingEvent
Honeycomb reported a major US1 degradation starting 2025-10-20 14:16 UTC, with SLO and Service Maps processing delays exceeding 5 minutes and later querying and trigger delays. Constrained EC2 capacity in AWS us-east-1 was cited; resolution came at 2025-10-21 15:41 UTC after 25 h 24 min, with no customer data reaching its load balancers lost.
- DegradationMajor incident
SubstackPost emails delayedEvent
Substack reported a major incident starting 2025-10-20 13:41 UTC, delaying scheduled post emails and partially disrupting publication dashboards, subscriber tabs and statistics. The vendor linked scheduled-post delays to a service-provider outage; manual publishing was a workaround. Scheduled sends recovered and the backlog cleared; the incident resolved at 2025-10-21 00:52 UTC after 11 h 11 min.
- OutageMajor incident
PandaDocPandaDoc application won't loadEvent
PandaDoc reported a major outage preventing the application from loading, with affected components across EU and US & Global services. The incident ran from 2025-10-20 13:34 UTC to 2025-10-20 14:06 UTC (31 min); PandaDoc confirmed normal operation was restored but did not state a cause or specific fix.
- OutageMajor incident
CockroachDBAWS us-east-1 outage impacting cluster operations and backupsEvent
CockroachDB reported a major AWS us-east-1 outage causing failures or delays in cluster creation, node additions, and backups; existing clusters remained operational. The incident started at 2025-10-20 13:28 UTC and was resolved at 2025-10-21 14:56 UTC, lasting 25 h 27 min. AWS resolved the underlying outage, and CockroachDB verified normal operations had resumed.
- OutageMajor incident
IterablePlatform Impact – Third-Party Vendor Disruption (Regional)Event
Iterable reported a major outage affecting its web application, global APIs, sends and Journeys, causing errors, timeouts and delays from 2025-10-20 13:15 UTC to 2025-10-20 21:54 UTC (8 h 39 min). A third-party provider experienced instability and applied regional mitigations. Queued sends cleared, and lingering AI and datasharing latency was resolved.
- OutageMajor incident
GrainOutages with upstream providers causing instabilityEvent
Grain reported a major outage affecting Grain Recorder and Recording Processing from 2025-10-20 13:09 UTC to 2025-10-21 11:30 UTC, lasting 22 h 21 min. AWS instance-launch failures prevented scheduled and ad-hoc recorders from starting; Grain moved recording to a new AWS Region, then deployed further mitigations after patch side effects caused continued recorder failures.
- OutageMajor incident
Webflow[RESOLVED] Reports of errors on hosted sites, publishing, and loading the Webflow DashboardEvent
Webflow reported a major outage affecting hosted sites (500/504 errors), publishing, Dashboard access and subscription purchases. Recorded from 2025-10-20 11:48 UTC to 2025-10-21 01:31 UTC (13 h 43 min), it ended with all systems operational. Webflow cited an upstream-provider issue for the initial disruption and advised republishing sites to clear remaining errors.
- OutageMajor incident
UnbounceApp.unbounce.com Currently Not AvailableEvent
Unbounce’s major app outage, attributed to AWS, started 2025-10-20 11:34 UTC and resolved 2025-10-20 23:28 UTC (11 h 53 min). Page publishing, Smart Traffic and Script Manager global scripts were affected. All features recovered, but some leads remained unprocessed and unavailable to integrations; Unbounce said they weren’t lost and processing would begin the next day.
- OutageMajor incident
CloseService InterruptionEvent
Close reported a major service interruption affecting calling, phone service and telephony provider connectivity from 2025-10-20 10:38 UTC to 2025-10-20 13:12 UTC, lasting 2 h 34 min. Close attributed the disruption to an AWS outage in us-east-1 and marked the incident resolved.
- DegradationMajor incident
RootlyOn-Call Notifications Delayed
Rootly reported a major incident delaying On-Call notifications, starting at 2025-10-20 10:31 UTC and resolved at 2025-10-20 11:36 UTC, lasting 1 h 5 min. Incident response and Slack continued working as expected; Rootly confirmed notification delays were fully resolved and all systems were operating normally.
- OutageMajor incident
- OutageMajor incident
MatillionLogin Issues with Matillion HubEvent
Matillion reported a major Hub outage causing errors or preventing some customers from logging in. The incident started at 2025-10-20 10:13 UTC and was resolved at 2025-10-20 12:31 UTC, lasting 2 h 17 min; partial service had been restored by the first update.
- OutageMajor incident
Bitrise reported a major outage of billing and subscription management because its billing service provider was down due to an AWS outage; builds ran without issues. The incident started at 2025-10-20 10:10 UTC and was resolved at 2025-10-20 14:24 UTC, lasting 4 h 13 min.
- OutageMajor incident
Jupyter (Anaconda)Outage with AWS providerEvent
Anaconda reported a major AWS-related outage causing degraded performance or unavailability across services, including authentication, repositories, notebooks and AI Platform. The incident ran from 2025-10-20 10:05 UTC to 2025-10-21 07:24 UTC (21 h 18 min); Anaconda reported services operational at 10-20 14:16 UTC before marking it resolved.
- OutageMajor incident
MatillionLogin Issues with Matillion HubEvent
Matillion reported a major Matillion Hub login incident: some customers may have encountered errors or been unable to log in. The recorded start was 2025-10-20 09:55 UTC, with a computed duration of 0 min; the incident was resolved and all login services were operating normally.
- OutageMajor incident
SentinelOne[NA1] Service Interruption due to AWS OutageEvent
SentinelOne reported a major USA (NA1) service interruption caused by an AWS outage, from 2025-10-20 09:55 UTC to 2025-10-21 13:16 UTC (27 h 20 min). Endpoints remained protected, but threat reporting and data ingestion were delayed, impairing managed response visibility. All services were restored and delayed data processed.
- OutageMajor incident
Help ScoutConnections IssuesEvent
Help Scout reported a major Web App connectivity outage starting 2025-10-20 09:50 UTC, lasting 2 h 46 min and resolved at 2025-10-20 12:37 UTC. The vendor attributed the disruption to a cloud infrastructure provider and confirmed normal platform performance after the provider’s disruption was fully resolved.
- OutageMajor incident
- OutageMajor incident
ChargebeeAWS Outage Impacting Chargebee ServicesEvent
Chargebee reported a major outage affecting Admin Console, API, Checkout, Dashboard and Webhooks in AU, EU and US from 2025-10-20 09:42 UTC to 2025-10-21 02:33 UTC (16 h 50 min). The postmortem cited AWS US-EAST-1 DNS resolution issues and EC2 instance scaling impairments; Chargebee reported normal operation after AWS implemented a fix.
- OutageMajor incident
MuxMux Player embeds increased error ratesEvent
Mux reported a major incident involving increased Mux Player embed errors from 07:30 UTC, caused by an underlying cloud vendor outage. The incident was tracked from 2025-10-20 09:39 UTC to 2025-10-20 22:04 UTC, lasting 12 h 25 min. Service was reported operational at 10:40 UTC, with monitoring continuing until resolution.
- OutageMajor incident
- OutageCritical incident
- DegradationMajor incident
1PasswordIntermittent performance issues with 1Password.comEvent
1Password reported a major degradation affecting the 1Password.com website, sign-in, and access to passwords and other items in USA/Global, with intermittent action errors. The incident ran from 2025-10-20 09:05 UTC to 2025-10-21 13:51 UTC (28 h 45 min); resolution followed AWS reporting all services back to normal.
- DegradationMajor incident
DrataAWS Increased Error Rates and Latencies causing degradation to multiple services and support access.Event
Drata reported a major degradation starting 2025-10-20 09:02 UTC: an AWS us-east-1 issue caused regional monitor failures and possible slow loading of drata.com. Resolved at 2025-10-20 12:00 UTC after 2 h 57 min, AWS’s DNS issue was fully mitigated, monitors processed normally, and drata.com loaded normally.
- OutageCritical incident
KlaviyoWidespread Access OutageEvent
Klaviyo reported a critical outage affecting login, sending and other services, caused by an upstream provider outage. The incident started at 2025-10-20 08:58 UTC and lasted 32 h 7 min, disrupting access and delaying sending, segmentation, unsubscribes and conversion attribution analytics. All services were restored, with resolution recorded at 2025-10-21 17:06 UTC.
- OutageMajor incident
- OutageMajor incident
- OutageMajor incident
- DegradationCritical incident
- DegradationCritical incident
CanvaUsers are encountering issues with accessing or using Canva.Event
Canva reported a critical incident preventing some users from accessing or using Canva, with increased error rates, slow design downloads, and errors generating images/video or creating and finding designs. It started at 2025-10-20 08:09 UTC and was resolved at 2025-10-20 21:43 UTC, lasting 13 h 33 min; no cause or specific fix was stated.