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.
Sunday, June 14
2 incident changes
- DegradationMajor incident
v0and VercelElevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
A major incident caused elevated latency and errors in FRA1 (Frankfurt, Germany), affecting the region and its CDN. It started at 2026-06-14 21:03 UTC and was resolved at 2026-06-15 01:24 UTC, lasting 4 h 20 min. Traffic was rerouted to CDG1 to mitigate impact, then fully restored to FRA1.
- OutageCritical incident
BrexServices failing to respond and timing out
Brex reported a critical outage affecting Dashboard, Partner API and Partner Integrations: database maintenance caused HTTP 500 errors and disrupted some card and transaction operations. Recorded from 2026-06-14 05:11 UTC to 2026-06-14 05:29 UTC (18 min), it was resolved after maintenance completed; failed API calls could be retried.
Saturday, June 13
2 incident changes
- OutageCritical incident
BrexElevated errors on the Team API and Brex Dashboard
Brex reported a critical incident affecting the Team API and Dashboard, starting 2026-06-13 15:10 UTC and resolved at 2026-06-13 15:17 UTC (7 min). Database maintenance caused HTTP 500 errors for some Team API requests and temporarily unavailable user information that could prevent Dashboard loading. Maintenance completed; failed API calls could be retried successfully.
- OutageCritical incident
Brex Travel experienced a critical outage preventing customers from booking and managing trips from 2026-06-13 05:21 UTC to 2026-06-13 07:53 UTC, lasting 2 h 32 min. Brex reported the issue resolved and said users could resume using Brex Travel; no cause or specific fix was stated.
Friday, June 12
7 incident changes
- OutageMajor incident
KlaviyoMeta Services DisruptionEvent
Klaviyo reported a major outage affecting WhatsApp messaging, Meta integrations, and Instagram connectivity from 2026-06-12 14:49 UTC to 2026-06-12 17:30 UTC (2 h 40 min), caused by an upstream provider disruption. Services returned to normal; failed messages were reprocessed, but a small number that never reached Klaviyo could not be recovered.
- OutageMajor incident
GorgiasWhatsApp, Instagram and Facebook messages might be delayedEvent
Gorgias reported a major outage affecting outbound Facebook, WhatsApp and Instagram messages, attributed to an outage on Meta’s side. It started at 2026-06-12 14:27 UTC and was resolved at 2026-06-12 18:29 UTC, lasting 4 h 2 min.
- OutageMajor incident
HootsuiteMeta Incident Affecting Hootsuite FunctionalityEvent
Hootsuite reported a major Meta-related incident affecting Facebook, Instagram, and Threads functionality, including publishing, analytics, and Inbox messaging. It started at 2026-06-12 14:01 UTC and lasted 4 h 17 min, resolving at 2026-06-12 18:18 UTC when Meta assets were fully accessible again in the Hootsuite dashboard.
- OutageMajor incident
LightdashDashboard charts failures (app.lightdash.cloud)
Lightdash reported a major outage affecting dashboard chart queries for app.lightdash.cloud users on Lightdash Cloud (US), with errors stating "Invalid timezone: project_timezone". It started at 2026-06-12 10:19 UTC and was resolved at 2026-06-12 10:44 UTC, lasting 24 min; a fix was applied and monitored.
- CriticalCritical incident
- DegradationMajor incident
ConfluentConfluent Cloud — Degraded inter-region connectivity — AWS us-west-2
Confluent Cloud reported major intermittent inter-region connectivity degradation affecting AWS us-west-2, causing delays or errors with Cluster Linking, Flink processing, and UI log access. Recorded start: 2026-06-12 07:42 UTC; the vendor later stated approximately 04:00 UTC. A mitigation was deployed; resolution was recorded at 2026-06-12 11:55 UTC, with a computed duration of 4 h 12 min.
- OutageMajor incident
LaunchDarklyElevated errors affecting LaunchDarkly application requests
LaunchDarkly reported major elevated errors affecting some application requests, with authentication, experiment management, flag targeting, progressive rollouts and the web app listed as affected. The incident started at 2026-06-12 04:23 UTC and resolved at 2026-06-12 04:58 UTC (35 min); monitoring confirmed no further impact beyond the initially reported error window.
Thursday, June 11
16 incident changes
- DegradationMajor incident
BuildkiteIncreased latency on REST and GraphQL APIs
Buildkite reported a major incident involving increased REST and GraphQL API latency for all customers, starting 2026-06-11 23:18 UTC and resolved 2026-06-12 00:16 UTC (57 min). Buildkite attributed the issue to elevated REST API service load and confirmed recovery after mitigation; the agent and stacks API were unaffected.
- DegradationCritical incident
ChargebeeEmail Service Degradation
Chargebee reported a critical email service degradation affecting Email Notifications in AU, EU and US, delaying system notifications due to an email-provider issue. It started at 2026-06-11 23:15 UTC and was resolved at 2026-06-12 02:12 UTC, lasting 2 h 57 min. New notifications resumed, and Chargebee said it would reprocess queued emails.
- OutageMajor incident
Some Grain local captures were stuck processing in a major Recording Processing incident from 2026-06-11 23:12 UTC to 2026-06-23 16:14 UTC, lasting 11 days 17 h. Grain resolved the incident and reported that all hung local captures were recovered.
- OutageCritical incident
1PasswordDevice Trust Authentication Service Experiencing Timeout Errors
1Password reported a critical Device Trust Authentication Service incident affecting USA/Global, with authentication failures, timeouts and 503 errors. It started at 2026-06-11 21:49 UTC and was resolved at 2026-06-12 23:18 UTC, lasting 25 h 29 min. Authentication services were reported recovered at 06-11 22:32 UTC; the vendor later reported identifying a cause and taking relief steps without specifying details.
- DegradationMajor incident
GorgiasDelays in HTTP integrations for some accounts
Gorgias reported major delays in HTTP integrations for some accounts from 2026-06-11 21:44 UTC to 2026-06-11 22:18 UTC, lasting 34 min. A fix was implemented at 2026-06-11 22:14 UTC, and the incident was subsequently resolved.
- MajorMajor incident
- OutageMajor incident
SalesforceService Disruption: Core Service
Salesforce reported a critical Core Service disruption affecting 1 instance, starting at 2026-06-11 16:20 UTC and resolved at 2026-06-11 16:22 UTC (2 min). Salesforce confirmed its mitigation was successful and service was stable; customers should no longer see impact. The technical trigger and underlying cause remained under investigation.
- OutageMajor incident
Grain reported a major Grain Recorder outage starting 2026-06-11 15:18 UTC, with scheduled bots delayed in joining and ad-hoc bot failures caused by an upstream provider outage. The incident lasted 6 h 6 min and was resolved at 2026-06-11 21:24 UTC, with no further bot-service degradation observed.
- CriticalCritical incident
- OutageMajor incident
DigitalOceanDeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"
DigitalOcean reported a major outage affecting Gradient AI DeepSeek V4 Pro, which returned HTTP 429 "Rate limit exceeded" errors in Agentic Inference Cloud - Model Services and Model Services. It started at 2026-06-11 14:24 UTC and was resolved at 2026-06-11 17:42 UTC, lasting 3 h 17 min; DigitalOcean identified the issue and implemented a fix without specifying details.
- DegradationMajor incident
FullStoryGuides & Surveys content delivery degraded
FullStory reported major Guides & Surveys degradation in its NA data center: guides, tours, surveys, and smart tips could display incorrectly, with interaction data delayed. The incident ran from 2026-06-11 13:58 UTC to 2026-06-11 17:08 UTC (3 h 10 min). Resource exhaustion caused the issue; delivery returned to normal, and additional safeguards are being implemented.
- CriticalCritical incident
- OutageCritical incident
GitLabIntermittent 5XX errors accessing in GitLab.com
GitLab.com experienced intermittent 5XX errors affecting website access, rated critical, from 2026-06-11 07:08 UTC to 2026-06-11 20:19 UTC (13 h 11 min). GitLab confirmed a cloud provider incident affecting a disk backing its primary database as the cause and reported normal operation at resolution.
- MajorMajor incident
- DegradationMajor incident
Box[Medium] Issue with Multiple Box Services
Box reported major degradation affecting API authentication, Login/SSO, Box Sign, and Box Edit / Tools, potentially disrupting access and work in Box. The incident ran from 2026-06-11 00:34 UTC to 2026-06-11 02:01 UTC (1 h 26 min). Box applied remediation and confirmed full functionality was restored.
- OutageCritical incident
Snowflake reported a critical outage affecting access to multiple core services in Azure - East US (Virginia) - Applications. It started and resolved at 2026-06-11 00:30 UTC, with a recorded duration of 0 min; Snowflake reverted a misconfigured change and confirmed service restoration. A completed postmortem links to an RCA on Snowflake Community.
Wednesday, June 10
10 incident changes
- OutageMajor incident
SmartsheetSmartsheet add-ons for Google is not working
Smartsheet reported a major outage of Smartsheet and Brandfolder add-ons for Google Docs, Sheets, and Slides from 2026-06-10 22:21 UTC to 2026-06-11 11:02 UTC, lasting 12 h 41 min. The postmortem says Google’s removal of an older runtime broke Smartsheet Merge for all ~234,000 users; code and deployment updates resolved it, with no customer data lost.
- CriticalCritical incident
- OutageMajor incident
DiscordActivities cannot be launched
Discord Activities could not be launched during a major incident starting 2026-06-10 17:15 UTC, lasting 1 h 19 min. Discord said it had disabled Activities, began ramping up traffic at 18:21 UTC, and marked the incident resolved at 2026-06-10 18:35 UTC.
- CriticalCritical incident
- OutageMajor incident
MuxElevated errors in Mux Data dashboard and API
Mux reported a major incident causing elevated errors in the Mux Data dashboard and API from 2026-06-10 14:04 UTC to 2026-06-10 18:58 UTC, lasting 4 h 53 min. A fix was implemented by 16:11 UTC, and the incident was resolved.
- OutageMajor incident
OptimizelyCMP: Modules are inaccessible
Optimizely reported a major CMP outage: Plan, Requests, and Library / DAM were inaccessible to customers. The incident started at 2026-06-10 11:49 UTC and lasted 7 h 31 min, resolving at 2026-06-10 19:20 UTC; a fix was implemented by 06-10 12:31 UTC, followed by monitoring.
- OutageMajor incident
WixRESOLVED: Issues Accessing Live Sites
Wix reported a major outage affecting some users’ access to live sites, starting at 2026-06-10 10:55 UTC and resolved at 2026-06-10 11:19 UTC (23 min). A fix was implemented by 06-10 11:14 UTC; no cause was stated.
- CriticalCritical incident
- OutageMajor incident
SalesforceMarketing Cloud Disruption: Marketing Cloud Core Service
Salesforce reported a major Marketing Cloud Core Service disruption affecting 1 instance from 2026-06-10 06:09 UTC to 2026-06-10 06:17 UTC, lasting 8 min. The incident was resolved; no cause or fix was stated.
- OutageMajor incident
SalesforceMarketing Cloud Disruption: Marketing Cloud Core Service
Salesforce reported a major Marketing Cloud Core Service disruption affecting 1 instance, from 2026-06-10 06:08 UTC to 2026-06-10 06:20 UTC (12 min). The incident was resolved; no cause or fix was stated.
Tuesday, June 9
10 incident changes
- CriticalCritical incident
- OutageMajor incident
DiscordAll clients may see issues connecting to Discord
All Discord clients could experience connection issues involving Gateway in a major-impact outage from 2026-06-09 21:24 UTC to 2026-06-09 21:44 UTC (reported duration: 19 min). Discord admitted more connections as capacity allowed, implemented a fix and confirmed resolution.
- OutageMajor incident
SecureframeSecureframe Agent devices missing from inventory
Some devices managed by Secureframe Agent dropped out of asset inventory, causing related tests to fail. Secureframe rated the incident major; it started at 2026-06-09 18:39 UTC and was resolved at 2026-06-10 02:11 UTC, lasting 7 h 32 min.
- OutageMajor incident
DialpadSome customers in the US and Canada may be experiencing issues with MMS messaging
Some Dialpad customers in the US and Canada experienced MMS messaging issues in a major-impact incident from 2026-06-09 16:34 UTC to 2026-06-09 17:14 UTC, lasting 40 min. Dialpad implemented a fix and confirmed resolution.
- OutageMajor incident
SalesforceHeroku Retroactive Feature Disruption: Dashboard, Platform API
Heroku reported a major Dashboard and Platform API disruption starting at 2026-06-09 15:32 UTC, lasting 35 min and resolved at 2026-06-09 16:07 UTC. Customers may have experienced authentication, deployment, scaling, Continuous Integration, build, and team-invitation issues; Heroku identified a recent change as the trigger and rolled it back.
- 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.