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 9
6 incident changes
- OutageMajor incident
v0and VercelElevated Build Errors for Secure Compute/Static IPs Projects
v0 reported a major incident with elevated build errors for Secure Compute/Static IPs projects, affecting Builds and Secure Compute - Builds. It started at 2026-06-09 14:09 UTC and was resolved at 2026-06-09 14:46 UTC, lasting 36 min; a fix was implemented, but no cause was stated.
- OutageMajor incident
ContentfulOptimization Hub Unavailable
Contentful’s Optimization tab was unavailable for Contentful Personalization and Contentful Analytics customers starting at 2026-06-09 13:57 UTC. The vendor rated the impact major and resolved the incident at 2026-06-09 14:18 UTC, after 20 min, stating that the underlying issue was resolved and the Optimization Hub was available again.
- DegradationMajor incident
SnykDegradation Affecting app.snyk.io
Snyk reported major degradation on app.snyk.io (SNYK-US-01), causing continuous loading or slowness in the UI and potentially affecting project testing. It started at 2026-06-09 11:22 UTC and was resolved at 2026-06-09 14:14 UTC, lasting 2 h 51 min. A fix was implemented; monitoring found no further issues.
- OutageMajor incident
JiraSome users experiencing issues viewing boards and work items
Some Jira Service Management and Jira Cloud customers experienced intermittent errors and degraded performance viewing boards and work items in a major-impact incident. It started at 2026-06-09 05:29 UTC and was resolved at 2026-06-09 18:28 UTC, lasting 12 h 58 min. Jira reported applying a fix and restoring normal operations at 10:36 UTC.
- OutageMajor incident
CanvaSome users may have issues accessing designs on Canva
Some Canva users had issues accessing designs, affecting Editing designs and Viewing designs. Canva rated the incident major; it started at 2026-06-09 03:41 UTC and was resolved at 2026-06-09 04:19 UTC, lasting 38 min. Engineers identified the issue and worked to implement a fix, but no cause or specific fix was stated.
- OutageMajor incident
Expo reported a major EAS outage affecting EAS Build, EAS Submit and EAS Workflows, with possible build failures during higher-than-usual database load. It started at 2026-06-09 02:35 UTC and was resolved at 2026-06-09 03:18 UTC, lasting 42 min. Expo said database load subsided and builds resumed normal processing.
Monday, June 8
7 incident changes
- DegradationMajor incident
DrataSafeBase <> Salesforce integration degradation
Drata reported major SafeBase Salesforce integration degradation starting 2026-06-08 22:38 UTC, resolved 2026-06-09 22:07 UTC after 23 h 28 min. Salesforce data lookups intermittently failed for a subset of customers due to refresh token expiration at its integration provider; SafeBase remained operational and no customer data was affected. The integration was fully restored.
- OutageMajor incident
- OutageMajor incident
NordLayerElevated levels of sign-in errors (MFA)
NordLayer reported a major incident involving elevated MFA sign-in errors affecting NordLayer Applications, NordLayer Control Panel, and NordLayer Service Management Platform (SMP). It ran from 2026-06-08 15:57 UTC to 2026-06-08 19:56 UTC, lasting 3 h 58 min; a fix was implemented and the incident was resolved.
- OutageCritical incident
A critical Snowflake outage affected Snowsight in Azure - East US 2 (Virginia), potentially causing page not found errors and login failures. It started at 2026-06-08 15:23 UTC and was resolved at 2026-06-08 16:40 UTC, lasting 1 h 16 min. The service self-recovered; Snowflake later linked a completed RCA on Snowflake Community.
- OutageCritical incident
- OutageCritical incident
MatillionNew Agent deployments having issues running Tasks in US Region
New Agent deployments had issues running Tasks in the US Region, affecting Agents and US Region - Agents. Matillion rated the incident critical; it started at 2026-06-08 12:08 UTC and was resolved at 2026-06-08 12:26 UTC, lasting 18 min. No cause or fix was stated.
- OutageMajor incident
GitLabCredits Dashboard Disruption
GitLab.com Credits dashboards failed to load, displaying “An error occurred while fetching data,” in a major incident starting 2026-06-08 09:17 UTC and resolved at 2026-06-08 13:22 UTC, lasting 4 h 5 min. Mitigation restored loading before GitLab confirmed normal operation; customers could not access their credit dashboards during the disruption.
Sunday, June 7
4 incident changes
- OutageCritical incident
- DegradationMajor incident
CloudinaryDAM View Assets Error
Cloudinary reported a major DAM degradation: recently added, deleted, or modified assets could appear outdated, while asset actions and the API still worked. Recorded start: 2026-06-07 13:30 UTC; the vendor reported onset around 1:17 PM UTC on June 7, 2026. A fix was implemented; resolution was confirmed at 2026-06-08 06:31 UTC (duration: 17 h 1 min).
- OutageMajor incident
CircleCImacOS jobs failing to start
CircleCI reported a major incident preventing macOS jobs across all resource classes from starting, from 2026-06-07 04:20 UTC to 2026-06-07 04:44 UTC (24 min). A fix restored normal job starts; customers whose jobs failed to start during the incident may rerun them.
- OutageMajor incident
SalesforceMaintenance Overrun Service Disruption Began: Analytics Cloud, Explore, Home Page +6 more
Salesforce reported a major maintenance-overrun service disruption affecting 1 instance and Analytics Cloud, Explore, Home Page, Loada View, Publishto Tableau Cloud, Refreshan Extract, Sign In, Subscriptions, and Web Edit. It began at 2026-06-07 00:55 UTC and was resolved at 2026-06-07 02:55 UTC, lasting 2 h 0 min.
Saturday, June 6
3 incident changes
- OutageMajor incident
JiraUsers experiencing issues loading work items in Atlassian products
Jira reported a major incident affecting loading, creating and viewing work items in some regions, starting 2026-06-06 23:21 UTC. A fix was implemented, and the incident was resolved at 2026-06-07 00:13 UTC; the reported duration was 51 min.
- OutageCritical incident
Klaviyo reported a critical outage of all WhatsApp functionality, including message sending, integration setup and template editing, due to an upstream provider outage. The incident started at 2026-06-06 17:18 UTC and was marked resolved at 2026-06-06 23:05 UTC, lasting 5 h 47 min; Klaviyo confirmed services were restored after monitoring.
- OutageMajor incident
Pinecone[Serverless][AWS][us-west-2] 5xx errors for some requests on some indexes
Pinecone reported a major outage causing 5xx errors for some requests on some Serverless indexes in AWS us-west-2. It started at 2026-06-06 17:05 UTC and was resolved at 2026-06-06 20:40 UTC, lasting 3 h 35 min; no cause or fix was stated.
Friday, June 5
8 incident changes
- DegradationMajor incident
ChargebeeAPI Service Degradation
Chargebee reported a major degradation affecting API (US), causing intermittent request timeouts. The incident record started and resolved at 2026-06-05 23:00 UTC (computed duration: 0 min); the update reported 2 minutes of timeouts during 05-06-2026 22:16 UTC to 22:22 UTC and confirmed services were operating normally.
- OutageMajor incident
RenderIssues with GitHub connections
Render reported a major incident affecting GitHub connections, starting at 2026-06-05 16:21 UTC and resolved at 2026-06-05 17:14 UTC, lasting 53 min. During recovery, Render advised customers to try redeploying affected services; no cause was stated.
- OutageMajor incident
XeroGlobal: Reporting - Errors loading reports
Xero reported a major global Reporting outage: some customers saw error messages or pages failing to load. It started at 2026-06-05 15:47 UTC and was resolved at 2026-06-05 16:30 UTC, lasting 43 min; Xero implemented a fix and monitored the results.
- OutageMajor incident
GitLabIssue with processing CI jobs
GitLab reported a major outage in which CI jobs were not processing on GitLab Hosted Runners and Hosted Runners on Linux, from 2026-06-05 11:58 UTC to 2026-06-05 13:46 UTC (1 h 48 min). GitLab reverted a recent change it suspected as the cause; job processing resumed and the queue cleared by resolution.
- OutageCritical incident
- OutageCritical incident
- DegradationMajor incident
SentinelOne[AP1] - Delayed Data Ingestion
SentinelOne reported a major AI SIEM (Data) ingestion degradation in Singapore (AP1), delaying security event data, asset inventories, or alerts for some customers. It started at 2026-06-05 09:03 UTC and was resolved at 2026-06-05 10:32 UTC, lasting 1 h 28 min. A fix was applied, and SentinelOne confirmed all services were restored.
- OutageMajor incident
BasetenElevated errors in a single US-East cluster
Baseten reported a major incident affecting Dedicated Inference, with elevated errors in a single US-East cluster. It started at 2026-06-05 02:10 UTC and was resolved at 2026-06-05 02:29 UTC, lasting 19 min; no cause or fix was stated.
Thursday, June 4
10 incident changes
- DegradationMajor incident
RenderEmails, including notifications, are delayed
Render reported a major email degradation affecting verification emails and workspace or service notifications, with Render Dashboard listed as affected. It started at 2026-06-04 23:27 UTC and resolved at 2026-06-05 00:39 UTC, lasting 1 h 11 min. Render attributed delays to its email provider; all outstanding emails were sent and processing returned to normal.
- DegradationMajor incident
WorkOS reported a major AuthKit email-delivery degradation affecting customers without custom domains due to an upstream provider issue. It started 2026-06-04 23:22 UTC and resolved 2026-06-05 00:49 UTC, lasting 1 h 26 min; the provider scaled up backlog processing, and all queued messages were sent.
- DegradationCritical incident
BrexSlow loading of activity logs and audit trail
Brex reported a critical Dashboard incident causing slow loads or timeouts for activity on expenses, bills, users, cards and account audit trails; other product areas were unaffected. It started at 2026-06-04 21:23 UTC and lasted 38 min, resolving at 2026-06-04 22:01 UTC. Brex reported a fix in place at 2026-06-04 21:37 UTC.
- OutageMajor incident
NetlifyElevated error rates for a subset of sites using Edge Functions
Netlify reported a major Edge Functions incident causing elevated 504 errors and slow page loads for some sites beginning approximately 17:00 UTC. The recorded incident started at 2026-06-04 20:24 UTC, lasted 34 min, and resolved at 2026-06-04 20:59 UTC. Mitigation restored normal error rates around 20:30 UTC; no customer action was required.
- OutageCritical incident
SquarespaceAcuity Scheduling Elevated Errors
Squarespace reported a critical disruption involving Acuity Scheduling elevated errors and Accounts & Billing; all users and services may have been affected. It started at 2026-06-04 18:58 UTC and was resolved at 2026-06-04 19:30 UTC, lasting 31 min. A fix was implemented, but no cause was stated.
- DegradationMajor incident
DrataDegraded AIQA Performance
Drata reported a major incident isolated to AIQA, with elevated errors attributed to degraded performance of an upstream provider. It ran from 2026-06-04 16:22 UTC to 2026-06-04 17:29 UTC, lasting 1 h 7 min. Drata reported that the provider stabilized and a fix was implemented before marking the incident resolved.
- OutageMajor incident
RetoolRetool Mobile apps cannot be opened in the in-browser preview
Retool Mobile apps failed to load in browser user-mode and editor previews during a major outage starting 2026-06-04 15:13 UTC, resolved at 2026-06-04 19:16 UTC (4 h 2 min). Editing mobile apps and native iOS/Android use were unaffected; Retool reported implementing a fix.
- OutageMajor incident
- OutageMajor incident
- OutageMajor incident
Elastic CloudCustomers may see delays with creating Azure serverless projects
Elastic Cloud reported a major incident causing delays creating Azure serverless projects and possible temporary unavailability of existing Azure projects. It started at 2026-06-04 01:51 UTC and was resolved at 2026-06-04 09:20 UTC, lasting 7 h 28 min; recovery began during monitoring, but no cause was stated.
Wednesday, June 3
10 incident changes
- OutageMajor incident
SalesforceField Service Mobile Feature Disruption: Field Service Mobile
Salesforce reported a major Field Service Mobile disruption across 29 instances: customers with performance priming enabled could experience syncing failures. It started 2026-06-03 21:27 UTC and was resolved 2026-06-10 22:49 UTC, lasting 7 days 1 h. Salesforce identified a recent deployment as the technical trigger and restored syncing by completing rollbacks.
- OutageMajor incident
LaunchDarklyFlag dashboard is failing to load
LaunchDarkly’s flag dashboard failed to load in a major-impact outage affecting flag targeting, from 2026-06-03 19:31 UTC to 2026-06-03 20:26 UTC (55 min). A fix was implemented, and LaunchDarkly confirmed the dashboard was successfully loading when the incident was resolved.
- OutageCritical incident
Box[Critical] Issues with Multiple Box Services
Box reported a critical outage affecting Login, All Files, Notes, Uploads and Box API. It started and was marked resolved at 2026-06-03 17:53 UTC (computed duration: 0 min). Box said its systems automatically detected and corrected the underlying issue, with no current impact.
- OutageMajor incident
Klaviyo’s major Shopify API outage caused integration setup errors and data-sync delays from 2026-06-03 14:23 UTC to 2026-06-03 17:16 UTC, lasting 2 h 52 min. Klaviyo attributed it to a partial upstream-service outage; syncing returned to normal, with automated retries clearing backlogs and failed integration states. Customers whose new integration setup failed can retry.
- DegradationCritical incident
- OutageCritical incident
AmplitudeAmplitude Platform Unavailability
Amplitude reported a critical outage affecting application access and interface loading across Analytics, Audiences, Data, Experiment, Guides & Surveys, and Session Replay. It started at 2026-06-03 13:13 UTC and was resolved at 2026-06-03 13:26 UTC, lasting 13 min. Amplitude implemented a fix and expected no data loss.
- OutageCritical incident
AmplitudeAmplitude Platform Unavailability
Amplitude’s critical platform outage prevented application access or caused significant interface errors, with issues reported since 11:58 AM UTC. The incident was recorded from 2026-06-03 12:25 UTC to 2026-06-03 12:52 UTC (27 min), when normal service was restored. Amplitude expected no data loss and said no customer action was needed.
- OutageMajor incident
RunwayIssues with Seedance and Seedream generations
Runway reported a major incident with increased error rates for Seedance and Seedream generations across App, Backend, and Public API. It started at 2026-06-03 08:04 UTC and was resolved at 2026-06-03 08:23 UTC; the computed duration was 18 min. Tasks were recovering by 08:18 UTC; no cause or fix was stated.
- OutageCritical incident
- DegradationMajor incident
Tuesday, June 2
1 incident change
- OutageMajor incident
MongoDB AtlasInvestigating connection issues to ADFA in GCP
A major outage affected connections and queries to MongoDB Atlas Data Federation and Online Archive instances in GCP regions from 2026-06-02 23:00 UTC to 2026-06-03 00:11 UTC, lasting 1 h 11 min. MongoDB identified a networking issue in GCP regions and reported mitigation, with connections working at resolution.