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, February 11
5 incident changes
- OutageMajor incident
- OutageMajor incident
SquarespaceCustomers unable to create new trial sites
Customers were unable to create new trial sites in a major incident affecting Site Loading, starting 2026-02-11 20:18 UTC and resolved at 2026-02-11 22:00 UTC. The incident lasted 1 h 41 min; Squarespace reported monitoring and resolution but stated no cause or fix.
- OutageMajor incident
- OutageMajor incident
SubstackSubstack Availability Issues
Substack reported a major outage affecting Substack.com, Substack publications and Writer dashboards, with loading issues starting at 2026-02-11 14:24 UTC. A fix was deployed, and services, error rates and latency returned to normal by 15:15 UTC; the incident was resolved at 2026-02-11 15:45 UTC, lasting 1 h 21 min.
- DegradationMajor incident
SquarespaceAcuity Scheduling / Webhook delivery delay
Squarespace reported a major Acuity Scheduling webhook delivery delay from 2026-02-11 14:08 UTC to 2026-02-11 15:57 UTC, lasting 1 h 49 min. Customers relying on webhooks faced delayed delivery; Squarespace said it identified the cause and resolved the issue but did not disclose the cause or fix.
Tuesday, February 10
10 incident changes
- OutageMajor incident
- OutageMajor incident
RevenueCatIncreased error rate on our API
RevenueCat reported a major incident with increased API and dashboard errors from 2026-02-10 20:45 UTC to 2026-02-11 00:35 UTC, lasting 3 h 50 min. RevenueCat suspected a Cloudfront issue, applied an emergency mitigation, and purged the DNS cache; SDK APIs recovered, while DNS caching prolonged errors for some users before resolution.
- OutageMajor incident
SurveyMonkeyUsers on Canadian DC not able to complete some surveys from US DC
SurveyMonkey reported a major outage affecting users logged into its Canadian data center: submitting responses to a subset of surveys stored in the US data center returned errors. It started at 2026-02-10 19:20 UTC and was resolved at 2026-02-10 19:41 UTC, with a reported duration of 20 min; monitoring continued.
- OutageMajor incident
- OutageMajor incident
ActiveCampaignActiveCampaign Reports Issue
ActiveCampaign reported a major reporting analytics issue affecting some users of Custom Reports, including US Region - Custom Reports, starting 2026-02-10 16:40 UTC. Engineers reported the issue fixed on 02-12 16:28 UTC and began monitoring; the incident closed at 2026-02-17 10:47 UTC, with a recorded duration of 6 days 18 h.
- OutageCritical incident
Webflow[RESOLVED] Reports of form notification emails not being delivered
Webflow reported a critical outage affecting form notification emails for some customers, starting 2026-02-10 16:11 UTC and resolved 2026-02-11 17:05 UTC (24 h 54 min). An upstream provider issue disrupted email processing; delivery was restored, while form submissions remained successfully processed and accessible via the Forms tab in Site Settings.
- OutageMajor incident
RunwayIssues with Nano Banana Pro generations
Runway reported a major incident with increased failure rates for Nano Banana Pro generations affecting App, Backend, and Public API. It started at 2026-02-10 13:26 UTC and was marked resolved at 2026-02-10 15:46 UTC, lasting 2 h 20 min, although the final update still said investigation was ongoing; no cause or fix was stated.
- OutageMajor incident
- OutageMajor incident
CloudinarySearch API and Media Library Issues
Cloudinary reported a major incident affecting Search API functionality and visibility of newly uploaded assets in Media Library, listing AP, EU and US Admin API components. Symptoms started around 04:30 UTC; the incident record ran from 2026-02-10 08:21 UTC to resolution at 2026-02-10 12:02 UTC (recorded duration: 3 h 41 min).
- OutageMajor incident
ConvexSome custom domains not working
Convex reported a major incident affecting many custom domains, which failed with TLS errors due to a misconfiguration; listed components were Free & Starter, Live Traffic - Database Services, and Live Traffic - Function Runtime. It lasted 35 min, from 2026-02-10 01:26 UTC to 2026-02-10 02:01 UTC; all hostnames were reconfigured before resolution.
Monday, February 9
4 incident changes
- OutageCritical incident
- OutageMajor incident
RunwayIssues with Nano Banana Pro generations
Runway reported increased errors in Nano Banana Pro generations affecting App, Backend, and Public API, with major impact. The incident started at 2026-02-09 15:39 UTC and was resolved at 2026-02-09 17:57 UTC, lasting 2 h 17 min; no cause or fix was stated.
- OutageMajor incident
RunwayIssues with Gemini 3 Pro (Nano Banana Pro) generations
Runway reported a major Backend incident causing increased error rates for Gemini 3 Pro (Nano Banana Pro) generations. It started at 2026-02-09 10:52 UTC and was resolved at 2026-02-09 12:11 UTC, lasting 1 h 19 min; Runway said it was no longer seeing high error rates for the model.
- OutageMajor incident
CockroachDBConnectivity issues to Standard and Basic clusters on AWS
CockroachDB reported a major incident affecting connectivity to Standard and Basic clusters on AWS, starting 2026-02-09 03:04 UTC and resolved at 2026-02-09 15:20 UTC (12 h 16 min). The vendor resolved an internal misconfiguration and reported normal cluster operation at 04:15 UTC, then monitored until resolution.
Saturday, February 7
3 incident changes
- OutageMajor incident
- OutageMajor incident
JFrogPartial outage in JFrog Cloud Platform affecting services on Azure US West
JFrog reported a major partial outage affecting Azure US West customers, including Artifactory, Distribution, Pipelines, security services, Webhook and Web UI, caused by Azure infrastructure compute issues. It started at 2026-02-07 08:33 UTC and lasted 6 h 52 min; JFrog reported full restoration at 2026-02-07 15:26 UTC after the upstream outage was resolved.
- DegradationMajor incident
ConvexConvex Dashboard Availability
Convex reported a major incident causing intermittent Dashboard and CLI errors on Free & Starter, starting 2026-02-07 02:50 UTC and resolved at 2026-02-07 03:06 UTC (15 min). An overloaded database was identified, and Convex reported scaling it; live traffic to Convex deployments was unaffected.
Friday, February 6
6 incident changes
- OutageCritical incident
JiraDisrupted JIRA and JSM availability
Jira reported a critical outage affecting Jira and JSM access for some users in us-east-1, with connection failures and unavailable services. It started at 2026-02-06 20:24 UTC and was resolved at 2026-02-07 05:38 UTC, lasting 9 h 13 min; mitigation efforts included initiating a point-in-time recovery.
- OutageCritical incident
GrammarlyThe AI-powered Docs is not working as expected
Grammarly reported a critical interruption in Grammarly Editor that prevented access to AI-powered Docs and made some documents inaccessible. It started at 2026-02-06 20:09 UTC and was resolved at 2026-02-06 20:52 UTC, lasting 42 min. A fix was implemented at 20:36 UTC; no cause was stated.
- OutageMajor incident
- OutageMajor incident
GrammarlySome agents may be unavailable or work intermittently
Grammarly reported a major outage affecting Superhuman Go & Agents: Gmail, Outlook, Salesforce, and Jira agents could be unavailable or intermittent in Grammarly, Superhuman, and Coda. It started at 2026-02-06 15:02 UTC and was resolved at 2026-02-06 15:49 UTC, lasting 46 min; the vendor said functionality should be restored.
- DegradationMajor incident
- OutageMajor incident
WasabiSystem Errors in US-WEST-1 Region
Wasabi reported a major outage affecting S3 services in US-West-1 (Oregon), disrupting customer access and operations. The incident started at 2026-02-06 08:45 UTC and was resolved at 2026-02-06 12:28 UTC, lasting 3 h 42 min. Wasabi attributed the disruption to a partial datacenter power issue affecting multiple racks.
Thursday, February 5
7 incident changes
- DegradationMajor incident
- DegradationMajor incident
DatadogDelays in Monitor Evaluations
Datadog reported a major incident involving delays in monitor evaluations, starting 2026-02-05 15:24 UTC and resolved at 2026-02-05 17:43 UTC, lasting 2 h 18 min. Customers could experience delayed monitor evaluations across the listed services; Datadog reported full monitor recovery at 17:23 UTC but provided no specific cause or fix.
- OutageCritical incident
JiraSome users in us-east-1 region unable to access Jira and JSM.
A critical outage prevented some users in us-east-1 from accessing Jira and JSM, starting 2026-02-05 14:13 UTC and resolving 2026-02-05 21:38 UTC, lasting 7 h 25 min. Jira placed affected sites in maintenance mode to expedite resolution; services returned to normal for all affected customers.
- OutageMajor incident
PendoInvestigating Issues with Guides and Resource Center
A major incident affected Guide statuses and access/editing of Resource Center Guide Modules across AU, EU, JPN, US1 and US environments. It ran from 2026-02-05 12:21 UTC to 2026-02-08 14:57 UTC (3 days 2 h); Pendo rolled out a fix and confirmed resolution after monitoring and reviewing guide statuses.
- OutageCritical incident
- OutageMajor incident
- OutageCritical incident
PendoGuides using segments are non-operational in Production and Staging Environments
Pendo reported a critical outage affecting guides using segments in Production and Staging Environments, including Visual Design Studio failures and nonfunctional Resource Center Guide Modules. The incident started at 2026-02-05 01:20 UTC and was resolved at 2026-02-05 04:45 UTC; Pendo reported full restoration and no guide content lost.
Wednesday, February 4
6 incident changes
- OutageMajor incident
- OutageMajor incident
- DegradationMajor incident
- DegradationMajor incident
- OutageMajor incident
SanityContent Agent and Canvas elevated error rate
Sanity reported a major incident affecting Content Agent and Canvas from 2026-02-04 10:23 UTC to 2026-02-04 11:17 UTC, lasting 53 min; some requests failed, though retries sometimes succeeded. The upstream AI provider implemented a fix and recovered, returning error rates to normal.
- OutageCritical incident
Tuesday, February 3
9 incident changes
- OutageMajor incident
PulumiErrors when creating new Pulumi Neo tasks
Creating new Pulumi Neo tasks produced errors during a major-impact incident starting 2026-02-03 23:26 UTC and resolved at 2026-02-03 23:33 UTC, lasting 6 min. Pulumi identified and rolled back the change that caused the issue.
- DegradationMajor incident
- OutageMajor incident
ConfluentConfluent Cloud Service Outage
Confluent reported a major Confluent Cloud outage starting 2026-02-03 21:33 UTC, resolved 2026-02-04 00:48 UTC (3 h 14 min). A networking configuration change in us-west-2 caused intermittent client connectivity and disruptions affecting Kafka, Flink, Metrics API, Logging, Provisioning, and Authentication; Confluent reverted the change and reported normal operations.
- OutageCritical incident
DrataDrata app not loading correctly
Drata reported a critical outage preventing access across all app functionality, starting 2026-02-03 19:06 UTC and resolved 2026-02-04 00:04 UTC (4 h 57 min). Drata attributed elevated error rates to upstream Cloudflare incidents; functionality was briefly reported restored before errors returned.
- OutageMajor incident
SanityContent Agent and Canvas experiencing elevated error rates
Sanity reported a major incident affecting Content Agent and Canvas from 2026-02-03 15:54 UTC to 2026-02-03 16:08 UTC, lasting 14 min. Elevated error rates caused some requests to fail, though retries sometimes succeeded. Sanity identified an upstream AI provider issue; a provider-level fix restored normal error rates.
- OutageCritical incident
BrazeUS02 Dashboard and SDK increased errors
Braze reported a critical incident affecting the US02 Dashboard and SDK Data Collection, with increased errors and possible Dashboard timeouts. The incident started at 2026-02-03 15:41 UTC and was resolved at 2026-02-03 16:02 UTC, lasting 21 min. Services were restored; the SDK automatically retries failed requests, and no action is required.
- DegradationMajor incident
Jupyter (Anaconda)Anaconda.org performance impacted
Anaconda.org experienced a major performance degradation affecting its database, front-end web service and conda.anaconda.org repository service, from 2026-02-03 13:45 UTC to 2026-02-03 15:05 UTC, lasting 1 h 19 min. A fix was implemented by 14:40 UTC; the incident was resolved, with no cause stated.
- OutageMajor incident
- DegradationCritical incident