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, March 12
7 incident changes
- OutageMajor incident
ConfluenceStatic macro rendering is failing in Confluence Cloud
Confluence Cloud reported a major outage affecting certain Marketplace macros, with users seeing “Error rendering macro 'static-macro': Page loading failed.” It started at 2026-03-12 11:42 UTC and was resolved at 2026-03-13 00:26 UTC, lasting 12 h 43 min. Confluence reported deploying a fix and confirmed normal service for affected customers.
- OutageMajor incident
- DegradationMajor incident
- OutageMajor incident
CanvaMedia uploads failing for some users
Canva reported a major incident affecting media uploads for some users, starting 2026-03-12 04:33 UTC and resolved at 2026-03-12 04:53 UTC (20 min). Affected users could see an upload failure error; Canva said the incident was mitigated but provided no cause or specific fix.
- DegradationCritical incident
BrexInternational Wire Partial Outage
Brex reported a critical International Wire Partial Outage affecting Banking and Bill Pay, starting at 2026-03-12 02:42 UTC and resolved at 2026-03-12 03:09 UTC (26 min). Brex said it identified the issue and put a fix in place; no cause was stated.
- OutageCritical incident
- OutageMajor incident
Wednesday, March 11
10 incident changes
- OutageCritical incident
CanvaUsers may experience a 503 error message when accessing canva.com.
Canva reported a critical incident in which users could encounter a 503 error when accessing canva.com. It started at 2026-03-11 23:28 UTC and was resolved at 2026-03-12 00:06 UTC, lasting 37 min; no cause or fix was stated.
- OutageMajor incident
DiscordSome servers unavailable
Some Discord servers were unavailable in a major-impact Gateway outage starting 2026-03-11 23:07 UTC and lasting 26 min, until 2026-03-11 23:33 UTC. Discord reported implementing a fix at 23:11 UTC and subsequently marked the incident resolved.
- DegradationMajor incident
- OutageMajor incident
- OutageMajor incident
AirtableSome users unable to access Airtable
Some users could not access Airtable during a major-impact incident starting 2026-03-11 19:01 UTC, resolved at 2026-03-12 01:19 UTC (6 h 18 min). Airtable reported full service recovery at 03-11 19:31 UTC but kept the incident open; a fix was implemented by 03-11 22:03 UTC.
- DegradationMajor incident
MakeScenario executions delayed on the us1.make.com zone
Make reported major delays in scenario executions on us1.make.com, starting 2026-03-11 18:25 UTC and resolved 2026-03-12 13:49 UTC, lasting 19 h 23 min. Delays subsided before recurring; Make reported a fix and normal processing at 03-11 21:54 UTC, then continued monitoring until resolution.
- OutageCritical incident
- OutageMajor incident
WixRESOLVED: Issues Loading Wix Editor and Dashboard
Wix reported a major incident affecting loading of My Sites, Site Dashboard, Wix Editor and Wix Studio, starting 2026-03-11 15:07 UTC. A fix was implemented at 15:22 UTC, and the incident was resolved at 2026-03-11 15:33 UTC; the reported duration was 25 min.
- OutageCritical incident
GreenhousePublic, Greenhouse Hosted Job Boards Not Responding
Greenhouse’s public hosted job boards stopped responding in a critical-impact outage starting 2026-03-11 14:48 UTC. The computed duration was 6 min, with resolution reported at 2026-03-11 14:55 UTC; a fix was implemented, but no cause was stated.
- OutageMajor incident
Tuesday, March 10
8 incident changes
- OutageMajor incident
MongoDB AtlasAtlas Clusters Snapshot Failures
MongoDB Atlas cluster snapshots were failing in a major-impact incident affecting MongoDB Cloud, from 2026-03-10 23:18 UTC to 2026-03-11 02:30 UTC (3 h 11 min). MongoDB implemented a fix and confirmed resolution; customers faced snapshot failures during the incident.
- DegradationMajor incident
- OutageMajor incident
- OutageMajor incident
- OutageMajor incident
- DegradationMajor incident
- DegradationMajor incident
ConfluenceAutomation events delayed for some customers in the APAC region
Confluence reported a major incident delaying automation events for some APAC customers, starting 2026-03-10 00:15 UTC and resolved at 2026-03-10 00:59 UTC (43 min). A hotfix restored automation performance while the backlog was processed; the vendor confirmed normal service for affected customers.
- DegradationMajor incident
JiraAutomation events delayed for some customers in the APAC region
Some APAC customers experienced delayed automations in Jira, Jira Service Management, Jira Work Management, Jira Product Discovery and Confluence. Jira rated the incident major; it started at 2026-03-10 00:06 UTC and was resolved at 2026-03-10 00:59 UTC, lasting 52 min. A hotfix restored automation performance while the backlog was processed.
Monday, March 9
4 incident changes
- OutageMajor incident
RenderCustom domains are unable to be created
Render’s Custom Domains experienced a major outage that prevented custom domain creation from 2026-03-09 20:19 UTC to 2026-03-09 20:39 UTC, lasting 20 min. Render marked the incident resolved but did not state a cause or fix.
- OutageMajor incident
DiscordIssues sending and loading messages
Discord reported a major API outage affecting sending and receiving messages, starting 2026-03-09 17:08 UTC and lasting 50 min until resolution at 2026-03-09 17:58 UTC. A fix was implemented at 17:29 UTC; no cause was stated.
- DegradationCritical incident
GrammarlyIncreased latency across Grammarly product offerings
Grammarly reported a critical degradation causing intermittent or slow features, login trouble, and “Service unavailable” errors from 2026-03-09 16:52 UTC to 2026-03-09 20:07 UTC, lasting 3 h 14 min. A fix implemented at 19:15 UTC restored login and use of Grammarly and Superhuman; the incident was resolved.
- DegradationMajor incident
Sunday, March 8
1 incident change
- DegradationCritical incident
BrexOkta sign in widget loading slowly
Brex’s Okta sign in widget loaded slowly, affecting Dashboard access, with vendor-rated critical impact. The incident started at 2026-03-08 14:48 UTC and was resolved at 2026-03-08 15:42 UTC, lasting 53 min; Brex reported identifying the issue but provided no cause or fix details.
Saturday, March 7
5 incident changes
- DegradationMajor incident
- OutageMajor incident
SnowflakeAWS - Europe (Zürich): INC0153183
Snowflake reported a major outage in AWS - Europe (Zürich), potentially preventing sign-ins, queries and data management. It started at 2026-03-07 20:05 UTC and was resolved at 2026-03-07 22:20 UTC; the recorded duration was 2 h 14 min. Snowflake identified a third-party cloud platform issue and confirmed service restoration after coordinating a fix with the provider.
- OutageMajor incident
- OutageMajor incident
- OutageMajor incident
Friday, March 6
10 incident changes
- DegradationMajor incident
- OutageMajor incident
Mux Video - VOD had major audio loss affecting some clips using "basic" or "premium" video_quality, caused by an encoding-change metadata mismatch. It started 2026-03-06 22:57 UTC and was resolved 2026-03-07 01:57 UTC (3 h 0 min); new clips work, but affected clips require re-creation from original assets to restore audio.
- DegradationMajor incident
- DegradationMajor incident
- OutageMajor incident
SocketGitHub app reports are stuck not starting
Socket reported a major outage affecting some GitHub app reports not starting, from 2026-03-06 16:15 UTC to 2026-03-07 07:04 UTC, lasting 14 h 48 min. Socket suspected an upstream GitHub webhook problem and advised closing and reopening PRs with stuck checks to trigger another webhook; the incident was resolved.
- OutageCritical incident
UpstashRegion ap-northeast-1 outage on Upstash Global
Upstash reported a critical outage affecting Redis Global in Tokyo, Japan (ap-northeast-1), causing elevated latency and connection errors for some databases. The incident ran from 2026-03-06 13:50 UTC to 2026-03-06 14:49 UTC (59 min). A traffic spike increased network utilization and connection load; Upstash mitigated it by scaling regional capacity and redistributing load across additional nodes.
- OutageMajor incident
SemgrepInvestigating issues with pull request checks and repository scans
Semgrep reported a major outage affecting repository scans and GitHub pull request checks: some customers saw scans not starting or checks not appearing. It started at 2026-03-06 12:04 UTC and was resolved at 2026-03-06 16:18 UTC, lasting 4 h 14 min. A fix was rolled out, and scans returned to normal operation.
- OutageMajor incident
- OutageCritical incident
- OutageCritical incident
BitbucketDisrupted Bitbucket availability
Bitbucket reported a critical outage affecting Website, API, Git via HTTPS, Git via SSH, and Pipelines, leaving affected users unable to access services. It started at 2026-03-06 02:44 UTC and was resolved at 2026-03-06 05:11 UTC, lasting 2 h 27 min. The postmortem attributed the disruption to a hosting-provider regional provisioning API rate limit blocking application workers from handling website traffic.
Thursday, March 5
4 incident changes
- DegradationMajor incident
- OutageMajor incident
Codeiumand WindsurfWe are investigating reports of completions/Tab not working
Codeium reported a major outage affecting Windsurf Tab completions starting 2026-03-05 16:23 UTC, lasting 1 h 22 min. A fix was implemented by 03-05 16:51 UTC, and the incident was resolved at 2026-03-05 17:46 UTC.
- OutageMajor incident
Sigma ComputingIssue with Burst email exports are resolved
Sigma Computing reported a major outage of Burst email exports starting 2026-03-05 10:10 UTC, lasting 4 days 7 h until resolution at 2026-03-09 17:31 UTC; standard exports remained operational. Engineers deployed a fix and re-enabled Burst Email Exports at 03-07 01:27 UTC, with no recurring problems observed during subsequent monitoring.
- OutageMajor incident
ConfluentMetrics API was experiencing failures from 03:23 UTC to 03:58 UTC
Confluent reported a major Confluent Cloud Metrics API outage, with unavailability from 2026-03-05 03:23 UTC to 2026-03-05 03:58 UTC. The incident record ran from 2026-03-05 04:40 UTC to resolution at 2026-03-05 07:22 UTC (2 h 42 min). Confluent reported mitigation and confirmed normal operation at resolution.