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 UTC.
Follow every change in a feed reader: Atom feed.
Tuesday, June 2
2 incident changes
- OutageMajor incident
OptimizelyInvestigating – Content Recommendation Service Degradation in EMEA region
Optimizely’s Content Recommendations API in EMEA could not serve recommendations during a major-impact incident from 2026-06-02 07:48 UTC to 2026-06-02 12:25 UTC, lasting 4 h 36 min. Users could see missing or unavailable recommendations across the platform. Optimizely reported an API disruption, implemented a fix at 08:51 UTC, and confirmed resolution.
- OutageMajor incident
LogRocketDashboard instability
LogRocket reported a major Dashboard incident involving slow and failing dashboard queries, starting 2026-06-02 05:23 UTC and resolved at 2026-06-02 06:10 UTC, lasting 46 min. The vendor identified the problem and reported rolling out a fix at 05:41 UTC; no cause was stated.
Monday, June 1
12 incident changes
- OutageMajor incident
XeroGlobal: Invoicing - some customers may be experiencing issues with accessing invoicing in Xero.
Xero reported a major global invoicing outage affecting some customers, starting 2026-06-01 23:55 UTC and resolved 2026-06-02 01:00 UTC, lasting 1 h 4 min. A product release made invoicing unavailable; Xero implemented a fix and confirmed resolution.
- OutageCritical incident
- OutageMajor incident
RenderUnable to load metrics for some services in Oregon
Render reported a major incident preventing metrics from loading for some services in Oregon; logs were unaffected. It started at 2026-06-01 21:25 UTC and was resolved at 2026-06-01 21:45 UTC, lasting 20 min.
- OutageCritical incident
- DegradationMajor incident
Bunny.netInvestigating Issues with Magic Containers and Databases
Bunny.net reported major degradation affecting Magic Containers and Bunny Database from 2026-06-01 16:02 UTC to 2026-06-01 20:18 UTC (4 h 16 min). Magic Containers workloads may have experienced processing delays, intermittent timeouts or reduced availability due to a hosting-provider network connectivity issue; service was reported restored at 06-01 17:24 UTC.
- OutageMajor incident
NeonIssue with project or branch operations in eu-central-1
Neon reported a major outage in eu-central-1 affecting project/branch creation and deletion and connections to new databases from approximately 10:30 UTC on June 01, 2026; existing database connectivity was unaffected. The incident record started at 2026-06-01 11:24 UTC and lasted 52 min, resolving at 2026-06-01 12:16 UTC. Neon stated the issue was fully resolved.
- OutageMajor incident
NeonIssue with project or branch operations is us-east-1
Neon reported a major outage affecting project/branch creation and deletion and new database connections in us-east-1; existing database connectivity was unaffected. Recorded from 2026-06-01 10:54 UTC to 2026-06-01 12:08 UTC (1 h 14 min), the incident was fully resolved; Neon reported customer impact between 10:22 UTC and 11:32 UTC.
- DegradationMajor incident
- DegradationMajor incident
JiraFor Jira-software viewIssues and viewBoard are degraded
Jira Software, Jira Service Management, and Jira Work Management had major degradation in Europe, blocking issues, boards, and backlogs and causing transition, comment, and navigation errors. Recorded from 2026-06-01 07:40 UTC to 2026-06-01 13:23 UTC (5 h 42 min), the incident involved caching infrastructure autoscaling failure; Atlassian deployed a fix to prevent recurrence.
- OutageCritical incident
Bunny.netIncreased Optimizer Errors
Bunny.net’s Optimizer served 5XX errors in a critical-impact incident that started at 2026-06-01 07:24 UTC and was resolved at 2026-06-01 10:38 UTC, lasting 3 h 14 min. No cause or specific fix was stated.
- OutageMajor incident
Ashby reported a major outage starting 2026-06-01 06:33 UTC, resolved at 2026-06-01 09:04 UTC; the recorded duration was 2 h 30 min. Its postmortem says the main application was slow and approximately 50% of user actions displayed errors during the affected period. AI features were re-enabled and accumulated work was being processed.
- OutageMajor incident
Box[Medium] Issues with Box AI
Box AI and Box Web Application - Box AI experienced a major-impact incident involving errors, failed AI responses or degraded performance. It started at 2026-06-01 00:58 UTC and was resolved at 2026-06-01 02:25 UTC, lasting 1 h 27 min; Box reported remediation and restored full functionality without specifying the cause or fix.
Sunday, May 31
2 incident changes
- OutageMajor incident
Expo reported a major EAS Build, EAS Submit and EAS Workflows outage affecting iOS build and submission jobs and macOS CI/CD workflows, caused by a macOS data center networking outage. It started 2026-05-31 20:38 UTC and was resolved 2026-06-01 03:47 UTC, lasting 7 h 8 min. Network recovery restored services; paid jobs cleared, but free jobs remained backlogged.
- DegradationMajor incident
Friday, May 29
11 incident changes
- OutageCritical incident
HootsuiteHootsuite login difficulties
Hootsuite reported a critical login outage affecting its Mobile Application and Web Application, potentially preventing dashboard access. The incident started at 2026-05-29 18:23 UTC and was resolved at 2026-05-29 19:05 UTC, lasting 42 min; no cause or specific fix was stated.
- OutageMajor incident
Elastic CloudIssue creating new projects in AWS ap-southeast-2
Elastic Cloud reported a major incident preventing creation of Serverless projects in AWS ap-southeast-2. It started at 2026-05-29 18:00 UTC and was resolved at 2026-05-29 18:36 UTC, with a computed duration of 35 min; no cause or specific fix was stated.
- OutageCritical incident
GitLabIssues with GitLab Duo in merge requests
GitLab reported a critical incident causing access errors for `@GitLabDuo` mentions in merge requests across GitLab.com, Dedicated, and Self-Managed. It started at 2026-05-29 12:50 UTC and lasted 10 h 51 min, resolving at 2026-05-29 23:41 UTC. A fix was deployed, and GitLab reported no related errors remaining in logs.
- OutageCritical incident
PendoPendo Academy Currently Inaccessible
Pendo Academy was inaccessible in all environments, showing “unauthorized” errors unrelated to user credentials. Pendo rated the incident critical; it started at 2026-05-29 12:40 UTC and was resolved at 2026-05-29 15:32 UTC, lasting 2 h 51 min. Pendo reported access restored across all regions but did not state a cause or fix.
- OutageMajor incident
CoralogixRUM (Real User Monitoring) Data Ingestion Unavailable in EU2
Coralogix reported a major outage affecting RUM data ingestion in EU2, starting at 2026-05-29 10:14 UTC and resolved at 2026-05-29 11:02 UTC (48 min). A fix was implemented, and all previously affected RUM data was available within the system after resolution.
- OutageMajor incident
ConfluentElevated error rates and latencies in Azure westus2 region
Confluent Cloud had a major outage with elevated errors and latencies in Azure westus2, linked to Azure network connectivity degradation. The incident ran from 2026-05-29 06:47 UTC to 2026-05-29 21:47 UTC (15 h 0 min), though Confluent reported symptoms beginning around 05:10 UTC. Azure’s degradation was mitigated and Confluent Cloud returned to normal.
- OutageMajor incident
SnowflakeAzure - West US 2 (Washington): INC0157956
Snowflake reported a major outage in Azure - West US 2 (Washington): customers could be unable to start, resume, or manage virtual warehouses. Recorded from 2026-05-29 06:47 UTC to 2026-05-29 22:28 UTC (15 h 41 min), it involved a third-party cloud platform issue. The provider implemented a fix; lingering latency and degradation were resolved.
- DegradationMajor incident
Elastic CloudUpstream Azure Outage Causing Service Degradation
An upstream Azure outage caused major degradation in Azure West US 2 (azure-westus2), limited to westus2-2, including Elastic Serverless projects. Non-high-availability deployments experienced connectivity errors, degraded performance and deployment-operation delays. The incident lasted 2 days 15 h, from 2026-05-29 06:32 UTC to 2026-05-31 21:33 UTC, with remediation and case-by-case support before resolution.
- OutageCritical incident
- OutageCritical incident
- OutageMajor incident
CanvaSome users may have issues accessing Canva
Some Canva users experienced payment issues affecting Billing and subscriptions in an incident rated major. It started at 2026-05-29 01:46 UTC and lasted 26 min, resolving at 2026-05-29 02:12 UTC; Canva reported implementing a fix and restoring normal billing and payment functionality.
Thursday, May 28
7 incident changes
- DegradationMajor incident
BuildkiteDelayed notifications
Buildkite reported a major incident delaying build and job notifications for a subset of customers, affecting email, GitHub commit status, Slack and webhooks. It started at 2026-05-28 20:20 UTC and was resolved at 2026-05-28 21:18 UTC; the computed duration was 57 min. Delayed notifications also delayed downstream CI, merge or deployment workflows for some customers.
- OutageMajor incident
Front[office365] Office channels offline preventing emails being sent or received
Front reported a major O365 outage affecting a subset of customers, with offline channels preventing email sending or receiving. It started at 2026-05-28 18:24 UTC and was resolved at 2026-06-01 23:35 UTC, lasting 4 days 5 h. Front added automatic channel recovery while continuing to investigate remaining sync failures with Microsoft.
- OutageMajor incident
GreenhouseAdobe Acrobat Sign experiencing issues sending for signature
Greenhouse reported a major Adobe Acrobat Sign incident: some customers encountered errors sending offers for signature. It started at 2026-05-28 16:23 UTC and was resolved at 2026-05-28 18:29 UTC, lasting 2 h 5 min. Greenhouse stated Adobe was experiencing an issue and investigating; no specific cause or fix was provided.
- OutageMajor incident
Rippling reported a major app and SSO outage from 2026-05-28 16:16 UTC to 2026-05-28 19:52 UTC, lasting 3 h 35 min. Database load caused the issues; Rippling scaled down contributing async jobs before re-enabling them. Supergroup membership latency delayed some access changes; Rippling reported all access and functionality restored and group memberships refreshed.
- OutageCritical incident
- DegradationCritical incident
- OutageMajor incident
SurveyMonkeySurveyMonkey Help Center is Down
SurveyMonkey’s Help Center was down for most users in a major-impact outage starting 2026-05-28 05:03 UTC and resolved at 2026-05-28 05:13 UTC (reported duration: 9 min). SurveyMonkey identified the issue and implemented a fix; the Help Center should now load normally.
Wednesday, May 27
8 incident changes
- DegradationMajor incident
GorgiasAI Agent degraded performance
Gorgias reported a major degradation affecting AI Agent and Ticket Translation, with higher latency caused by a third-party LLM provider outage. It started at 2026-05-27 15:28 UTC and was resolved at 2026-05-28 06:07 UTC, lasting 14 h 38 min. Gorgias switched LLM providers and reported gradual improvement before resolution.
- OutageMajor incident
GreenhouseReadMe - Harvest API Docs outage
Greenhouse’s Harvest API documentation site experienced a major outage starting 2026-05-27 15:08 UTC, leaving customers unable to access the documentation. It lasted 20 h 26 min and was resolved at 2026-05-28 11:34 UTC; Greenhouse said its documentation vendor was working to fix the issue.
- DegradationMajor incident
GorgiasAI Agent - Too many handovers
Gorgias reported a major AI Agent degradation causing some conversations to be handed over due to a confirmed partial degradation of OpenAI's API. It started at 2026-05-27 14:20 UTC and was resolved at 2026-05-27 18:02 UTC, lasting 3 h 41 min.
- OutageMajor incident
Rippling reported a major incident degrading Single Sign-on (SSO) and related identity flows, starting at 2026-05-27 14:01 UTC and resolved at 2026-05-27 14:12 UTC (11 min). A fix was deployed, successful SSO logins were confirmed, and error rates fell.
- OutageMajor incident
NetlifyFailed & delayed builds due to Github incident
Netlify’s Build Pipeline experienced delayed and failed builds due to a GitHub incident, with impact rated major. The incident ran from 2026-05-27 12:13 UTC to 2026-05-27 14:17 UTC, lasting 2 h 4 min; Netlify reported builds had returned to normal.
- OutageCritical incident
- OutageMajor incident
GitLab reported a major Git Operations outage with Git operation errors from 2026-05-27 07:31 UTC to 2026-05-27 09:55 UTC, lasting 2 h 24 min. Mitigation rules reduced errors, and GitLab confirmed resolution with metrics back to normal; no cause was confirmed.
- OutageMajor incident
ConfluenceUsers facing errors when attempting to view Calendars in Confluence
Confluence reported a major View Content incident: users received errors viewing Calendars on Confluence Cloud pages, starting 2026-05-27 06:03 UTC and resolved at 2026-05-27 07:48 UTC (1 h 45 min). Its final update reported user impact between 00:50 UTC and 07:30 UTC on 27 May 2026; engineers identified and resolved the underlying issue.
Tuesday, May 26
6 incident changes
- OutageMajor incident
RunwayIssues affecting Aleph 2.0 generations
Runway reported a major incident affecting Aleph 2.0 generations, now resolved. The recorded start was 2026-05-26 22:10 UTC and resolution was 2026-05-26 19:30 UTC; these timestamps conflict, and the computed duration is unknown. Runway stated that the incident lasted approximately 2 hours.
- OutageMajor incident
Elastic CloudMissing Metrics in Cloud Console - Azure Southeast Asia
Some users experienced missing metrics visualizations in the Elastic Cloud console for deployments in Azure Southeast Asia due to disrupted metric data ingestion. Elastic rated the impact major and reported the situation stabilized; the incident started and was resolved at 2026-05-26 21:35 UTC, with a recorded duration of 0 min.
- DegradationMajor incident
- OutageCritical incident
StatsigStatsig Console temporarily down
Statsig Console (console.statsig.com) was down in a vendor-rated critical incident from 2026-05-26 18:01 UTC to 2026-05-26 18:25 UTC, lasting 24 min. No flag checks or SDK calls were affected; Statsig marked it resolved and said it had determined the root cause, without disclosing the cause or fix.
- DegradationMajor incident
GitLabDelays in CI job processing by runners
GitLab reported a major degradation affecting CI/CD - Hosted runners on Linux, leaving some users’ CI jobs pending while waiting for runners. The incident started at 2026-05-26 16:16 UTC and lasted 1 h 5 min, resolving at 2026-05-26 17:21 UTC after a deployed fix restored normal job pickup.
- OutageCritical incident
GitLabGitLab Duo "Quota exceeded" Errors
GitLab’s critical Duo Agent Platform (DAP) incident blocked access for some customers with “Usage quota exceeded” errors from 2026-05-26 12:50 UTC to 2026-05-26 14:25 UTC (1 h 35 min). GitLab identified a Customers Portal feature flag as the likely cause, disabled it, and confirmed full resolution after cache refreshes.
Monday, May 25
2 incident changes
- OutageMajor incident
- OutageMajor incident
NetlifySupport Communication Delivery Issues
Netlify reported a major outbound email delivery outage affecting some services, including Netlify Helpdesk support communications, from 2026-05-25 15:31 UTC to 2026-05-25 17:32 UTC (2 h 0 min). Delivery was restored at 15:53 UTC, though queued emails could still be delayed; Netlify worked with its email provider during recovery.