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, January 15
3 incident changes
- OutageMajor incident
Pinecone[Serverless][AWS][us-east-1] 5xx errors on read operations for some indexes
Pinecone reported a major incident causing 5xx errors on read operations for some Serverless indexes in AWS us-east-1. It started at 2026-01-15 12:12 UTC and was resolved at 2026-01-15 15:30 UTC, lasting 3 h 18 min. A fix was implemented by 2026-01-15 14:30 UTC; no cause was stated.
- OutageMajor incident
- OutageMajor incident
Wednesday, January 14
2 incident changes
- DegradationMajor incident
RipplingDegraded performance in Payroll
Rippling reported major degraded performance in its Payroll application starting 2026-01-14 20:54 UTC, lasting 3 h 19 min until resolution at 2026-01-15 00:13 UTC. A fix was implemented and monitoring began at 01-14 23:27 UTC.
- OutageMajor incident
RevenueCat reported a major API Uptime incident involving a spike in database-related errors from 2026-01-14 11:00 UTC to 2026-01-14 11:54 UTC, lasting 54 min. Fortress was enabled to mitigate errors, then disabled when the error rate returned to normal at 11:16 UTC; all Fortress receipts were replayed by resolution.
Tuesday, January 13
2 incident changes
- DegradationMajor incident
- DegradationMajor incident
Monday, January 12
11 incident changes
- OutageMajor incident
SurveyMonkeyRespondents cannot progress past a matrix question where 'Number of rows respondents must answer:' is set to 'All'
SurveyMonkey reported a major outage on some surveys: respondents could not progress past matrix questions with 'Number of rows respondents must answer:' set to 'All'. The incident started at 2026-01-12 23:47 UTC and lasted 40 min, resolving at 2026-01-13 00:27 UTC; a fix was implemented at 2026-01-13 00:19 UTC.
- OutageMajor incident
PipedreamPipedream and Pipedream Connect Event Sources and Webhooks are failing
Pipedream reported a major outage affecting Pipedream and Pipedream Connect Event Sources and Webhooks, disrupting HTTP event sources, HTTP workflows, destinations and Connect. It started at 2026-01-12 23:31 UTC and resolved at 2026-01-13 00:51 UTC, lasting 1 h 19 min. Pipedream implemented a fix but did not disclose the cause.
- OutageMajor incident
StatsigSuccess Rate drop for US East Region
Statsig reported a major outage affecting Config Delivery API - US East 1 and Log Event API, US East 1, with elevated errors for initialize and event logging traffic. It started at 2026-01-12 20:30 UTC and was resolved at 2026-01-12 22:24 UTC, lasting 1 h 54 min; no cause or fix was stated.
- OutageMajor incident
JiraDisrupted create and view issue for some customers
Jira reported a major partial service disruption affecting issue creation, viewing, editing, and board viewing for some customers. It started at 2026-01-12 18:23 UTC and was resolved at 2026-01-12 23:45 UTC, lasting 5 h 21 min; Jira confirmed services were operating normally for all impacted customers.
- OutageMajor incident
- OutageMajor incident
New RelicData and UI Irregularities - US and EU regions
New Relic reported a major US and EU incident causing NRDB timeouts/query lag, data ingestion errors, real-time data viewing issues, and delayed or missing alert notifications. It started at 2026-01-12 15:21 UTC and was resolved at 2026-01-12 18:10 UTC; New Relic reported recovery following mitigating actions and resolution of two concurrent ingestion and query service interruptions.
- OutageCritical incident
- OutageMajor incident
- DegradationMajor incident
KlaviyoIssues with Campaign Sending and Scheduling
Klaviyo reported a major campaign scheduling and sending incident starting 2026-01-12 11:12 UTC, lasting 1 h 10 min and resolved at 2026-01-12 12:23 UTC. New campaigns and scheduled RAST campaigns could not send; previously scheduled non-RAST campaigns continued processing. A fix restored service and all delayed campaigns were replayed; no data loss was expected.
- OutageMajor incident
SquarespaceConnectivity issues - 503 errors
Squarespace sites experienced connectivity issues and 503 errors affecting Site Loading, with a major impact level. The incident started at 2026-01-12 11:05 UTC and was resolved at 2026-01-12 11:27 UTC, lasting 22 min; no cause or fix was stated.
- OutageMajor incident
Friday, January 9
8 incident changes
- OutageMajor incident
PendoPendo Chatbot not operational in the Resource Center
Pendo’s Resource Center Chatbot was not operational in a major-impact incident affecting AU, EU, US1 and US environments. It started at 2026-01-09 20:46 UTC and resolved at 2026-01-09 21:18 UTC, lasting 31 min. Pendo attributed the disruption to Support Bot vendor latency and directed customers to its support request form until normal operation resumed.
- OutageMajor incident
Sigma ComputingChat Support experiencing 3rd party outageEvent
Sigma Computing’s major chat support outage ran from 2026-01-09 20:33 UTC to 2026-01-09 22:23 UTC, lasting 1 h 49 min. Third-party provider Intercom experienced an outage and reported implementing a fix; Sigma confirmed chat support was fully operational at resolution. Customers were directed to submit support tickets for urgent requests and warned of slower responses.
- OutageCritical incident
- OutageCritical incident
BrexExpense service unavailable
Brex’s Expense service was unavailable, affecting Spend Management, with impact rated critical. The incident started at 2026-01-09 19:43 UTC and was resolved at 2026-01-09 20:48 UTC, lasting 1 h 4 min. Brex reported a fix in place at 20:20 UTC but did not state a cause.
- DegradationMajor incident
SemgrepDegraded scan performance in CI and Semgrep Managed Scans
Semgrep reported major scan performance degradation in CI and Semgrep Managed Scans from 2026-01-09 17:02 UTC to 2026-01-09 23:27 UTC, lasting 6 h 25 min. Semgrep implemented several changes and reported recovery; at resolution, the system was stable and scans were executing normally.
- 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.