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.
Thursday, October 23, 2025
7 incident changes
- OutageMajor incident
GrammarlyAI Grader and Citation Finder agents are not working as expected.
Grammarly reported a major disruption affecting AI Grader and Citation Finder agents, listing Generative AI assistance and Grammarly Editor as affected components. It started at 2025-10-23 19:17 UTC and was resolved at 2025-10-23 22:37 UTC, lasting 3 h 19 min. Grammarly said it identified the root cause but did not disclose it or the fix.
- OutageMajor incident
Pinecone[Serverless][GCP][us-central1] 5xx errors on some read and write operations
Pinecone reported a major incident causing 5xx errors on some read and write operations for Serverless Indexes in GCP us-central1, starting 2025-10-23 17:32 UTC. A fix was implemented at 17:42 UTC, and the incident was resolved at 2025-10-23 18:23 UTC after 51 min.
- DegradationMajor incident
- OutageMajor incident
- OutageMajor incident
Monday.comInvestigating connectivity issues across accounts and devices in AU server
Monday.com reported a major connectivity incident across accounts and devices in the AU server, listing AUS, EU, US and Platform components as affected. It started at 2025-10-23 11:08 UTC and was resolved at 2025-10-23 11:28 UTC (19 min). A fix was implemented by 2025-10-23 11:15 UTC; no cause was stated.
- OutageMajor incident
- OutageCritical incident
StatsigAll US-West Requests Failing
Statsig reported a critical US-West outage affecting configuration APIs for SDK initialization, background syncing, and the Console API. It started at 2025-10-23 00:10 UTC and was resolved at 2025-10-23 00:35 UTC, lasting 25 min; a networking change routed requests to an incorrect backend, causing exceptions, and Statsig addressed the change.
Wednesday, October 22, 2025
2 incident changes
- OutageMajor incident
AssemblyAIRequests failing for Slam-1 model
AssemblyAI reported a major partial outage affecting Slam-1 pre-recorded transcription requests, with slow processing, increased errors and failures. It started at 2025-10-22 17:56 UTC and was resolved at 2025-10-22 23:58 UTC, lasting 6 h 1 min. Universal requests were unaffected and offered as a workaround; Slam-1 performance returned to normal before resolution.
- OutageMajor incident
WixRESOLVED: Editor, Site List, and other Wix Services Experiencing Issues
Wix reported a major outage affecting Editor, Site List, sign-in, site loading and other services, disrupting site management and access. It started at 2025-10-22 12:43 UTC and resolved at 2025-10-22 12:59 UTC; the reported duration was 15 min. Wix implemented a fix but did not state a cause.
Tuesday, October 21, 2025
9 incident changes
- OutageMajor incident
Webflow[Resolved] Publishing, webhook delivery failures, and delays in form actions
Webflow reported a major incident affecting publishing and webhook delivery, with delays to form Actions, starting 2025-10-21 22:34 UTC and resolved at 2025-10-21 23:18 UTC (44 min). A fix was implemented; hosted websites remained operational, but some users may need to republish to reflect recent changes.
- OutageMajor incident
DrataSome Okta users unable to login
Some Drata users were unable to log in through Okta in a major-impact incident starting 2025-10-21 19:13 UTC. Drata reported deploying a fix and mitigating the issue at that time, then marked it resolved at 2025-10-21 19:17 UTC; the recorded duration was 3 min.
- OutageMajor incident
Pinecone[Serverless][Azure][eastus2] 5xx errors on some read and write operations
Pinecone reported a major incident affecting Serverless Indexes in Azure eastus2, with 5xx errors on some read and write operations. It started at 2025-10-21 17:57 UTC and resolved at 2025-10-21 19:24 UTC, lasting 1 h 26 min. A fix was implemented; no cause was stated.
- DegradationMajor incident
- OutageMajor incident
PusherElevated API Errors in AP4 Cluster
Pusher reported a major AP4 incident affecting Channels API message publishing, with elevated errors and latency, starting 2025-10-21 15:06 UTC and resolved at 2025-10-21 17:43 UTC (computed duration: 2 h 36 min). Pusher identified an issue with a backend caching server and implemented a fix; many customers may have been unable to publish new messages.
- OutageMajor incident
- DegradationMajor incident
MessageBird (Bird)Slow processing of messages through Viber
MessageBird (Bird) reported a major Viber messaging degradation from 2025-10-21 14:11 UTC to 2025-10-24 07:43 UTC, lasting 2 days 17 h. Sending was slow due to reduced processing rates from Viber, and a limited subset of customers could not send messages. The vendor confirmed sending was fully restored and resolved the incident.
- OutageMajor incident
StatuspageAtlassian Cloud Services impactedEvent
A major incident linked to an AWS DynamoDB outage potentially caused intermittent login issues at manage.statuspage.io. Recorded start: 2025-10-21 09:48 UTC; computed duration: unknown, with conflicting timestamps. The postmortem reports disruption between Oct 20, 2025 06:48 UTC and Oct 21, 2025 04:05 UTC; full functionality returned Oct 21, 2025 - 05:24 UTC.
- OutageMajor incident
PineconeSome users may be unable to access the Pinecone web console. All API services remain fully operational.
Some users were unable to access the Pinecone web console during a major-impact incident from 2025-10-21 01:27 UTC to 2025-10-21 03:30 UTC, lasting 2 h 3 min. All API services remained fully operational; Pinecone reported implementing a fix at 10-21 02:20 UTC and subsequently resolved the incident.
Monday, October 20, 2025
32 incident changes
- DegradationMajor incident
RunwayWe've identified a problem and are working on a fix
Runway reported a major degradation affecting App, Backend, and Public API, with longer generation queue waits. It started at 2025-10-20 21:14 UTC and resolved at 2025-10-20 23:33 UTC, lasting 2 h 18 min. A fix normalized errors and generation throughput, while the generation backlog temporarily kept queue waits elevated.
- OutageMajor incident
VantaIssues installing Vanta Device Monitor
Vanta Device Monitor installations were failing in a major-impact outage that started at 2025-10-20 21:11 UTC and lasted 14 min. Vanta marked it resolved at 2025-10-20 21:25 UTC, stating installations should function as expected; no cause or specific fix was disclosed.
- 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.