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, February 17
4 incident changes
- DegradationMajor incident
GreenhouseDegraded performance and delayed search results in Greenhouse Recruiting
Greenhouse reported a major incident affecting job boards and search-related requests in Greenhouse Recruiting, causing slow or incomplete search results. It ran from 2026-02-17 23:33 UTC to 2026-02-18 00:18 UTC (45 min). Greenhouse implemented a fix and confirmed resolution.
- OutageMajor incident
SmartsheetResource Management Advanced reports failing to create and refresh.
Smartsheet reported a major outage preventing Resource Management Advanced reports from being created or refreshed in the US Production environment, from 2026-02-17 16:08 UTC to 2026-02-17 18:55 UTC (2 h 46 min). A failure linking Resource Management Workflows to the main Data Shuttle engine caused the disruption; rolling back the most recent Data Shuttle deployment restored service.
- OutageMajor incident
- OutageMajor incident
Monday, February 16
5 incident changes
- OutageCritical incident
- OutageCritical incident
Runway reported a critical outage preventing task creation across App, Backend and Public API, starting 2026-02-16 16:29 UTC and resolved at 2026-02-16 17:11 UTC (42 min). A fix restored functionality; delayed requests were expected to resume processing, and previously failed submissions could be retried.
- OutageCritical incident
MatillionOngoing platform instability impacting design and runtime of pipelines
Matillion reported critical platform instability affecting pipeline design and runtime in both EU and US regions. The incident started at 2026-02-16 16:27 UTC and was resolved at 2026-02-16 17:12 UTC, lasting 45 min; no cause or fix was stated.
- OutageCritical incident
Monday.comInvestigating connectivity issues across accounts and devices
Monday.com reported a critical outage affecting platform connectivity, loading and automations, starting 2026-02-16 14:10 UTC and resolved at 2026-02-16 14:49 UTC (38 min). The postmortem attributed US customer downtime to an application-level bug introduced by a billing subsystem code change that increased platform load; a fix was implemented, and customers were advised to refresh their browsers.
- OutageMajor incident
Metabaseand Metabase CloudSome Metabase functionality unavailable
Some Metabase functionality was unavailable on the Metabase Cloud Platform in a vendor-rated major incident starting 2026-02-16 02:48 UTC. It was resolved at 2026-02-16 03:15 UTC after 27 min; no cause or specific fix was stated.
Saturday, February 14
1 incident change
- OutageMajor incident
AblyElevated Attach Error Rate in eu-west-1
Ably reported a major incident involving elevated attachment errors in eu-west-1, affecting Ably Pub/Sub - Europe (Ireland) and Europe (Ireland). It started at 2026-02-14 05:57 UTC and lasted 8 min, resolving at 2026-02-14 06:05 UTC; Ably implemented a fix but did not state a cause.
Friday, February 13
5 incident changes
- OutageMajor incident
UnbounceClick Conversions Not Being Captured
Unbounce reported a major incident in which link-click conversions were not captured, starting 2026-02-13 22:40 UTC and resolved at 2026-02-13 23:34 UTC (54 min). A fix restored tracking, but affected conversions may not have been recorded; Unbounce was working to restore them.
- DegradationCritical incident
Sumo LogicProblem with Metrics Collection in Australia (AU)
Sumo Logic reported a critical Metrics Collection incident in Australia (AU), causing latency in processing and displaying metrics data. It started at 2026-02-13 09:53 UTC and was resolved at 2026-02-13 10:43 UTC, lasting 50 min; a fix was implemented and normal operation restored.
- OutageMajor incident
AirtablePartial unavailability of Airtable 2026-02-12
Airtable reported a major partial outage starting 2026-02-13 05:40 UTC, marked resolved at 2026-02-13 07:49 UTC (2 h 8 min). Mitigation restored base reads/writes first, while adding collaborators/shares and creating/deleting applications remained unavailable. At resolution, all site functionality except billing management was reported working; billing restoration was ongoing.
- OutageMajor incident
AshbyAll-in-One: Native E-signature Experiencing Errors
Ashby’s All-in-One native e-signatures were non-functional in a major outage starting 2026-02-13 05:10 UTC, lasting 5 h 5 min until 2026-02-13 10:15 UTC. Ashby could display success despite signatures not completing; customers needed DocuSign or an external e-signature service. The upstream provider resolved the issue.
- OutageMajor incident
Thursday, February 12
8 incident changes
- DegradationMajor incident
LaunchDarklyData attribution issues with Experimentation
LaunchDarkly reported a major Experimentation degradation starting 2026-02-12 23:30 UTC, lasting 4 h 8 min, with certain experiment iterations receiving incorrectly attributed data. The incident was resolved at 2026-02-13 03:39 UTC; LaunchDarkly confirmed results for active experiments were accurate again.
- OutageMajor incident
SubstackSubstack Availability Issues
Substack reported a major availability outage affecting Substack.com, Substack publications, and Writer dashboards starting at 2026-02-12 23:25 UTC. It lasted 1 h 5 min and was resolved at 2026-02-13 00:31 UTC; Substack reported implementing a fix but did not state a cause.
- DegradationMajor incident
- OutageCritical incident
Postman's Agent Mode experienced high error rates in a critical incident affecting Postbot and US - Postbot. It started at 2026-02-12 16:51 UTC and was resolved at 2026-02-12 18:05 UTC, lasting 1 h 13 min; no cause or fix was stated.
- OutageCritical incident
- OutageMajor incident
- OutageMajor incident
JiraIncreased error rates on Jira and Jira Service Management Ecosystem Apps
Jira reported a major incident involving increased API error rates in Jira and Jira Service Management Ecosystem Apps, starting 2026-02-12 10:44 UTC and lasting 6 days 21 h. Forge and Connect apps were unaffected. The vendor ran a restoration process for affected apps and resolved permission errors across all Apps; the incident was resolved at 2026-02-19 08:04 UTC.
- OutageMajor incident
Wednesday, February 11
6 incident changes
- OutageMajor incident
ConfluentAll new cluster creations in Azure westus3, southcentralus, and eastus2 are failing
Confluent reported a major outage preventing all new Confluent Cloud cluster creations in Azure westus3, southcentralus, and eastus2, with customer impact starting February 11, 2026 at 09:50 UTC. The recorded incident lasted 4 h 30 min and was resolved at 2026-02-12 02:45 UTC; Confluent identified the issue with Azure support and confirmed cluster creation was fixed.
- 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
4 incident changes
- DegradationMajor incident
- 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
2 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.