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.
Friday, January 9
3 incident changes
- DegradationMajor incident
- OutageCritical incident
Box[Critical] Issues with Logins, Notes and API
Box reported a critical incident affecting Logins, Notes and API, recorded as starting 2026-01-09 07:14 UTC and resolved 2026-01-09 06:00 UTC. The resolution precedes the recorded start, so duration is unknown; Box stated there was no current impact.
- DegradationMajor incident
ConvexIntermittent increased error rates
Convex reported intermittent increased error rates to/from database affecting Free & Starter and Live Traffic - Database Services, with major impact. The incident started at 2026-01-09 00:51 UTC and was resolved at 2026-01-09 01:40 UTC, lasting 48 min; no cause or specific fix was stated.
Thursday, January 8
7 incident changes
- OutageMajor incident
- OutageMajor incident
ConfluenceConfluence site unreachable for some users
A major Confluence Cloud outage affected some users in us-east-1, disrupting page viewing and editing; the incident started 2026-01-08 15:27 UTC and lasted 3 h 42 min. Atlassian attributed database overload to a configuration change and an unexpected traffic burst. Service was restored, with resolution recorded at 2026-01-08 19:09 UTC.
- OutageMajor incident
- DegradationMajor incident
ConfluentMultiple customers are reporting networking instability in the Azure West Europe region
Confluent Cloud experienced major networking instability affecting multiple customers in Azure West Europe from 2026-01-08 12:30 UTC to 2026-01-08 16:25 UTC, lasting 3 h 55 min. Confluent reported implementing a fix at 13:09 UTC and subsequently confirmed resolution.
- OutageMajor incident
- DegradationMajor incident
SemgrepSome CI Scans are not completing successfully
Semgrep reported a major CI scan degradation starting 2026-01-08 10:40 UTC: some scans failed to complete or took a long time, getting stuck at "Uploading scan results" or "Finalizing scan". A fix was implemented at 12:11 UTC, and the incident was resolved at 2026-01-08 13:36 UTC after 2 h 56 min.
- OutageCritical incident
Box[Critical] Issues with Multiple Box Services
Box reported a critical outage affecting Login, Public API, Uploads, Downloads and Box Notes, starting 2026-01-08 01:39 UTC and resolved at 2026-01-08 02:37 UTC (58 min). Customers experienced elevated errors and timeouts; Box reported taking remediation steps and confirmed all affected services were restored.
Wednesday, January 7
2 incident changes
- OutageMajor incident
CanvaUsers may experience issues with Logging in/Signing up.
Canva reported a major incident affecting logging in and signing up, starting 2026-01-07 23:29 UTC and resolved 2026-01-08 03:09 UTC, lasting 3 h 39 min. A fix was in place by 2026-01-08 01:02 UTC, followed by monitoring; no cause was stated.
- OutageCritical incident
BitbucketUnable to reach bitbucket site
Bitbucket Cloud reported a critical outage starting 2026-01-07 16:23 UTC, resolved at 2026-01-07 18:53 UTC (2 h 29 min). Affected customers could not load the dashboard and experienced degraded navigation and intermittent public REST API failures; the postmortem attributed the disruption to unexpected public API load causing long-running database queries.
Tuesday, January 6
6 incident changes
- OutageMajor incident
- OutageCritical incident
- OutageMajor incident
- OutageCritical incident
Braze reported a critical incident causing errors accessing the US05 Cluster Dashboard, starting 2026-01-06 15:41 UTC and resolved at 2026-01-06 16:29 UTC (47 min). Messaging sending and other services were unaffected. Dashboard service was restored and monitored before resolution.
- OutageMajor incident
LeverResumes and Offers Failing to Load
Lever reported a major incident: resumes failed to load, offers did not display, and manually adding resumes to opportunities produced errors. It ran from 2026-01-06 10:52 UTC to 2026-01-06 13:51 UTC, lasting 2 h 59 min and disrupting hiring workflows. A fix was implemented at 2026-01-06 12:47 UTC; no cause was stated.
- OutageMajor incident
JiraDisrupted Automation for Jira triggers not running for some customers
A major incident prevented some Automation for Jira rules from executing in Jira and Jira Service Management in Asia Pacific and South East regions; other regions were unaffected. It started 2026-01-06 05:18 UTC and was resolved 2026-01-07 11:32 UTC, lasting 30 h 14 min. New events were fixed, and failed rules were rerun by replaying historical events.
Monday, January 5
6 incident changes
- OutageMajor incident
Sigma ComputingScheduled Backend Tasks not running on AWS US
Sigma Computing reported a major AWS US outage affecting scheduled exports, materializations, and warehouse view updates from 2026-01-05 21:38 UTC to 2026-01-05 23:33 UTC, lasting 1 h 55 min. A fix was implemented, and Sigma stated that queued tasks should start recovering automatically after resolution.
- OutageMajor incident
AsanaDowntime for the Asana web app
Asana reported a major web app outage preventing new sessions, starting 2026-01-05 21:17 UTC and resolved at 2026-01-05 21:50 UTC (32 min). Existing web sessions, mobile and API traffic were unaffected. Engineers identified and reverted the change blocking new sessions, restoring service.
- OutageMajor incident
LeverIncorrect counts for candidates in pipeline stages
Lever reported a major incident showing incorrect candidate pipeline-stage counts across multiple customer accounts, affecting Hire and LeverTRM - Hire in EU and Global Data Centers. Candidate profile indexing stopped due to a service outage; service was restored and affected data backfilled. The incident ran from 2026-01-05 17:00 UTC to 2026-01-12 18:26 UTC, lasting 7 days 1 h.
- OutageCritical incident
A critical Census outage affected Census Sync Management UI and Sync Engine from 2026-01-05 15:17 UTC to 2026-01-05 20:24 UTC (5 h 7 min). Syncs could not run, and website access was disrupted. Census attributed the outage to an indexing change and said rebuilding previous indexes delayed recovery.
- OutageCritical incident
Monday.comInvestigating connectivity issues across accounts and devices
A critical connectivity outage affected Platform and US - Platform from 2026-01-05 14:29 UTC to 2026-01-05 15:36 UTC (1 h 7 min). The postmortem attributed 31 minutes of US access disruption to an application-level issue; EMEA and APAC access were unaffected. A fix was implemented; automations could be delayed or not trigger.
- OutageMajor incident
Saturday, January 3
2 incident changes
- OutageMajor incident
MakeConnectivity Issues Detected
Make reported a major login outage affecting eu1.make.celonis.com and eu2.make.com; background scenarios continued processing normally. It started at 2026-01-03 05:31 UTC and resolved at 2026-01-03 20:51 UTC, lasting 15 h 19 min. Make applied a fix at 01-03 10:48 UTC but did not disclose the root cause.
- OutageMajor incident
Box[Medium] Issue with Enterprise Reporting
Box reported a major Enterprise Reporting outage: some requested and scheduled reports were not generated, and missing reports should be rerun. Recorded start: 2026-01-03 00:16 UTC; recorded resolution: 2026-01-02 13:30 UTC, preceding the start, so duration is unknown. Box reported no current impact.
Friday, January 2
4 incident changes
- OutageCritical incident
AshbyAll-In-One: Issues sending E-Signatures
Ashby reported a critical All-In-One outage affecting e-signature requests through Dropbox Sign, starting 2026-01-02 21:12 UTC and resolved at 2026-01-02 23:36 UTC, lasting 2 h 23 min. Dropbox Sign resolved its downtime, and Ashby verified that e-signature functionality worked again.
- DegradationMajor incident
WorkOSDelayed Webhook Deliveries
WorkOS reported major delays affecting some webhook event types in AuthKit and Core Services - AuthKit, from 2026-01-02 20:48 UTC to 2026-01-03 14:20 UTC (17 h 31 min). Directory Sync and Magic Auth code functionality were unaffected. WorkOS increased processing capacity, and webhook delivery latencies returned to normal.
- OutageMajor incident
Dropbox SignDropbox Sign is experiencing an outage.
Dropbox Sign reported a major outage affecting signing, signature requests, finished document delivery, API callbacks, fax services, and HubSpot and Salesforce integrations. It ran from 2026-01-02 20:13 UTC to 2026-01-02 23:25 UTC, lasting 3 h 12 min. The vendor identified the issue, implemented a fix, and marked the incident resolved; no cause was stated.
- OutageMajor incident
PineconeIntermittent unavailability across all environments for some indexes
Pinecone reported a major incident causing intermittent unavailability for some indexes across all environments, starting at 2026-01-02 16:31 UTC. A fix was implemented by 01-02 17:18 UTC, and the incident was resolved at 2026-01-02 17:58 UTC; the reported duration was 1 h 26 min.
Thursday, January 1
1 incident change
- OutageMajor incident
Wednesday, December 31, 2025
2 incident changes
- DegradationCritical incident
- OutageMajor incident
Pinecone[Serverless][AWS][us-west-2] 5xx errors on some read path operations
Pinecone reported a major incident causing 5xx errors on some Serverless read-path operations in AWS us-west-2. It started at 2025-12-31 03:13 UTC and was resolved at 2025-12-31 03:29 UTC, lasting 16 min; a fix was implemented, but no cause was stated.
Tuesday, December 30, 2025
2 incident changes
- OutageMajor incident
- OutageMajor incident
Monday, December 29, 2025
1 incident change
- DegradationMajor incident
WorkOSDegraded AuthKit Behavior
WorkOS reported major AuthKit degradation causing intermittent errors from 2025-12-29 12:26 UTC to 2025-12-29 14:13 UTC, lasting 1 h 47 min. DDoS protection mitigated an attack but produced false positives, causing intermittent 404s for end users; WorkOS adjusted rule sensitivity and marked the incident resolved.
Saturday, December 27, 2025
3 incident changes
- OutageMajor incident
ActiveCampaignIncrease in Failures Using the API
ActiveCampaign reported increased API failures affecting API Availability and US Region - API Availability, with major impact. The incident started at 2025-12-27 17:00 UTC and was resolved at 2025-12-27 17:28 UTC, lasting 28 min; engineers identified the root issue but did not disclose the cause or specific fix.
- OutageCritical incident
Jira, Trelloand BitbucketOutbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Products
Jira reported a critical incident affecting outbound email, mobile push notifications, and support ticket delivery across cloud products, recorded from 2025-12-27 04:42 UTC to 2025-12-27 05:20 UTC (37 min). The postmortem reports email and notification failures beginning at 02:48 UTC, triggered by expired monitoring-infrastructure TLS certificates; core Jira and Confluence remained available, and affected services were restored.
- OutageCritical incident
ConfluenceOutbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Products
A critical incident affected email delivery, mobile notifications and support ticket creation across Atlassian Cloud products from 2025-12-27 02:48 UTC to 2025-12-27 05:20 UTC (2 h 32 min). Core Jira and Confluence functionality remained available. Atlassian attributed the issue to expired monitoring TLS certificates disrupting its metrics pipeline and confirmed all affected services were restored.
Tuesday, December 23, 2025
1 incident change
- OutageCritical incident
RunwayUnable to start new tasks
Runway reported a critical outage preventing new tasks across App, Backend, and Public API from 2025-12-23 17:06 UTC to 2025-12-23 17:17 UTC, lasting 11 min. A fix released at 17:10 UTC improved processing; delayed requests were expected to resume, and failed submissions could be retried. The incident was resolved.
Monday, December 22, 2025
3 incident changes
- OutageMajor incident
- OutageMajor incident
SquarespaceDomain Registrations
Squarespace reported a major incident affecting domain registrations on squarespace.com from 2025-12-22 13:52 UTC to 2025-12-22 15:37 UTC, lasting 1 h 45 min. The Domains panel of sites was unaffected. Squarespace identified the issue, implemented a fix, and marked the incident resolved.
- DegradationMajor incident
JFrogJFrog Connect partial disruption with subset of devices appearing offline
JFrog Connect had a major partial disruption causing some devices to appear offline or disconnected in the dashboard, starting 2025-12-22 08:51 UTC and lasting 47 h 52 min. It was resolved at 2025-12-24 08:44 UTC after engineers applied a fix and verified all devices were reporting status accurately.
Saturday, December 20, 2025
1 incident change
- OutageCritical incident
Help ScoutDocs site not loading
Help Scout’s Docs Sites failed to load in a critical outage starting 2025-12-20 21:24 UTC. Sites were loading again by 2025-12-20 21:59 UTC, and the incident was resolved at 2025-12-20 22:43 UTC, lasting 1 h 19 min.
Friday, December 19, 2025
3 incident changes
- OutageMajor incident
RudderStackControl Plane & Activation API Disruption
RudderStack reported a major Control Plane and Activation API outage starting 2025-12-19 18:40 UTC, causing possible web app access errors; data-plane event ingestion was unaffected. An internal service outage affected dependent components, and RudderStack rolled out a fix. All services returned to normal at 2025-12-19 19:14 UTC, after 34 min.
- OutageCritical incident
Front recorded a critical App outage starting 2025-12-19 17:29 UTC, lasting 3 h 53 min and resolving at 2025-12-19 21:23 UTC. Its postmortem reports US-West-2 API latency from 14:50 UTC to 18:10 UTC prevented website loading and queued messages; no messages were lost. Missed-message and application-webhook backfills were completed.
- OutageCritical incident
MakeLoging to the platform is not available
Make reported a critical login outage starting 2025-12-19 00:17 UTC; webhooks and scenario executions remained operational. Service was restored by 2025-12-19 03:28 UTC, but some execution logs remained delayed until backfilling finished at 2025-12-19 11:02 UTC. The incident lasted 10 h 44 min.