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.
Monday, July 27
16 incident changes
- MajorMajor incident
- DegradationMajor incident
DatadogSynthetics Test Results Delayed
Datadog reported a major Synthetics degradation starting 2026-07-27 19:05 UTC: tests continued running, but results were delayed. A fix was implemented, and the incident was resolved at 2026-07-27 19:52 UTC after 46 min.
- OutageMajor incident
DigitalOceanAgent Platform Requests Returning HTTP 500 Errors
DigitalOcean’s Agent Platform requests returned HTTP 500 errors, affecting Agentic Inference Cloud - Agent Runtime and Agent Runtime, with major impact. The incident started at 2026-07-27 18:31 UTC and was resolved at 2026-07-28 15:24 UTC, lasting 20 h 52 min; DigitalOcean reported identifying the issue and implementing a fix but provided no cause.
- MajorMajor incident
- OutageMajor incident
Discordsession starts, DM message delivery down
Discord reported a major outage affecting session starts and live DM delivery: users could have trouble logging in or receiving DMs live. It started at 2026-07-27 17:48 UTC and was resolved at 2026-07-27 18:05 UTC, lasting 17 min; no cause or fix was stated.
- OutageCritical incident
dbt LabsCertificate errors affecting the dbt platform
A critical dbt platform incident caused certificate or "insecure connection" warnings on US, AU, and EU/EMEA multi-tenant AWS instances after a certificate configuration change. The incident started at 2026-07-27 16:54 UTC and was resolved at 2026-07-27 18:50 UTC, lasting 1 h 56 min; dbt deployed a fix and reported normal access restored.
- OutageMajor incident
DescriptIssue with uploads to media library
Descript reported a major incident affecting uploads to the media library’s root directory, starting 2026-07-27 16:37 UTC and resolved at 2026-07-27 16:54 UTC, with a reported duration of 16 min. Customers could work around the failure by creating a folder and uploading directly into it; no specific cause or fix was disclosed.
- OutageCritical incident
SentryError and profile ingestion issues in US
Sentry reported a critical US error and profile ingestion outage starting 2026-07-27 16:23 UTC, lasting 2 h 3 min and resolved at 2026-07-27 18:27 UTC. Ingestion was back up at 16:56 UTC, but ingestion and alerting delays continued; Sentry later confirmed the backlog was cleared and ingestion returned to normal.
- OutageCritical incident
Rippling reported a critical outage preventing access to its web and mobile apps, starting 2026-07-27 16:11 UTC and resolved at 2026-07-27 18:37 UTC (2 h 26 min). Rippling rolled back its latest deployment; access was restored at 16:32 UTC, and performance metrics were back to normal by 17:08 UTC.
- OutageMajor incident
WorkOSContinued email delivery errors
WorkOS reported a major incident involving email delivery errors and Dashboard email delivery statuses not updating. It started at 2026-07-27 14:10 UTC and was resolved at 2026-07-27 17:37 UTC, lasting 3 h 27 min. WorkOS reported remediation restored delivery rates and Dashboard status updates; no cause was stated.
- MajorMajor incident
- MajorMajor incident
- DegradationMajor incident
WorkOSElevated errors during email delivery
WorkOS reported a major email-delivery degradation starting 2026-07-27 10:05 UTC and resolved at 2026-07-27 13:04 UTC, lasting 2 h 58 min. An initial mitigation did not fully resolve the elevated errors; WorkOS applied a refined mitigation and confirmed delivery rates had recovered.
- OutageCritical incident
GongGong Application Sign-in Issues
Gong reported a critical sign-in outage starting 2026-07-27 08:46 UTC, later narrowed to a subset of users across all environments signing in using Office 365 who could experience failures or authentication timeouts. The incident was resolved at 2026-07-27 10:05 UTC after 1 h 19 min; no specific cause or fix was disclosed.
- MajorMajor incident
- MajorMajor incident
Sunday, July 26
2 incident changes
- OutageMajor incident
RevenueCatProblems connecting to Apple services
RevenueCat reported a major Apple Receipt Server outage preventing validation of new purchases, starting 2026-07-26 23:06 UTC and resolved 2026-07-27 09:50 UTC (10 h 44 min). Temporary entitlements of at most 24 hours preserved access while validation was unavailable; all impacted purchases were replayed by resolution, with related webhook and integration events delayed.
- OutageMajor incident
SegmentData processing pipeline issue
Segment reported a major data processing issue affecting Data Processing Pipeline (US), Engage (US), and Journeys (US) from 2026-07-26 01:43 UTC to 2026-07-26 04:10 UTC, lasting 2 h 27 min. A fix was implemented by 03:02 UTC, and the incident was resolved.
Saturday, July 25
2 incident changes
- DegradationMajor incident
SegmentConnections Processing Delays
Segment reported major Connections processing delays affecting Streaming Destinations (US), delaying destination delivery. The incident started at 2026-07-25 22:45 UTC and resolved at 2026-07-26 04:39 UTC, lasting 5 h 53 min. A fix was implemented at 07-25 23:39 UTC, with processing latency recovering under monitoring.
- OutageMajor incident
SupabaseAuthentication issues for some projects
Some Supabase projects experienced authentication issues in a major-impact incident starting 2026-07-25 14:11 UTC and lasting 34 min, resolved at 2026-07-25 14:45 UTC. Supabase implemented a fix at 07-25 14:21 UTC and reported authentication had returned to normal at 07-25 14:25 UTC.
Friday, July 24
13 incident changes
- DegradationMajor incident
PlanetScaleInsights metrics underreporting
PlanetScale reported a major incident: Insights metrics underreported for Postgres and Vitess databases, while database traffic and connectivity were unaffected. It started at 2026-07-24 14:41 UTC and was resolved at 2026-07-24 17:42 UTC, lasting 3 h 0 min. Mitigations were in place by 07-24 17:04 UTC, with signs of recovery.
- DegradationMajor incident
ClickHouse CloudMonitoring and billing impact on customer services in ap-southeast-1
ClickHouse Cloud reported a major monitoring and billing degradation in ap-southeast-1, with possible service availability degradation; the initial update named eu-west-1. Impacts included stale dashboards, missing notifications/Prometheus metrics, stalled billing metering and unapplied autoscaling recommendations. It lasted 8 h 20 min, from 2026-07-24 13:07 UTC to 2026-07-24 21:28 UTC, with missing data backfilled.
- OutageCritical incident
WixRESOLVED: Issues With Multiple Wix Services
Wix reported a critical outage affecting Checkout, My Sites, Sign-In, Site Dashboard, Site Editing and Site Loading, starting 2026-07-24 11:29 UTC. A fix was implemented by 11:57 UTC, and the incident was resolved at 2026-07-24 12:16 UTC; the recorded duration was 46 min.
- MajorMajor incident
- OutageMajor incident
Notion was not loading during a major outage that started at 2026-07-24 11:24 UTC and lasted 1 h 11 min. Notion reported service was back to normal at 2026-07-24 12:35 UTC; no cause or specific fix was stated.
- OutageCritical incident
RenderService Disruption in Oregon
Render reported a critical disruption affecting Oregon Web Services, with some services unreachable or experiencing failed requests. The incident started at 2026-07-24 11:16 UTC and was resolved at 2026-07-24 13:30 UTC, lasting 2 h 14 min. Render observed recovery across all services at 11:27 UTC and said it believed an upstream provider caused the issue.
- CriticalCritical incident
- CriticalCritical incident
- MajorMajor incident
- CriticalCritical incident
- OutageMajor incident
MatillionS3 Load/Unload or Azure Blob Storage Load/Unload COPY failures
Matillion reported a major outage involving S3 Load/Unload or Azure Blob Storage Load/Unload COPY failures, affecting Pipeline Execution in AU, EU and US regions. It started at 2026-07-24 08:02 UTC and was resolved at 2026-07-24 15:13 UTC, lasting 7 h 10 min; Matillion reported identifying the issue and implementing a fix.
- OutageMajor incident
SalesforceService Disruption: Core Service
Salesforce reported a critical Core Service disruption affecting 1 instance, from 2026-07-24 02:58 UTC to 2026-07-24 03:11 UTC (13 min). The incident was resolved; no cause or fix was stated.
- OutageMajor incident
XeroGlobal: Xero - some customers may be experiencing issues in Xero
Xero reported a major global incident affecting Xero Platform and Settings: some customers encountered slowness, errors and unavailable features when accessing or using Xero. It ran from 2026-07-24 01:59 UTC to 2026-07-24 03:02 UTC (1 h 3 min). Xero attributed the issue to a product release and restored service through a rollback.
Thursday, July 23
14 incident changes
- OutageMajor incident
CohereDashboard Login Service Disruption
Cohere reported a major Dashboard login outage: a continuous refresh loop prevented authentication. The incident ran from 2026-07-23 22:56 UTC to 2026-07-23 23:46 UTC (50 min); Cohere implemented a fix and confirmed resolution. API access, model inference, and all other Cohere services were unaffected.
- OutageCritical incident
Retoolretool-email unavailable
Retool reported a critical Email Server outage from 2026-07-23 22:22 UTC to 2026-07-24 18:34 UTC, lasting 20 h 12 min. Some Retool Emails failed with “Disabled for sending spam” due to an upstream email provider issue; official user invites and password resets were unaffected. Retool restored the sending domain and normal delivery, and added safeguards against recurrence.
- MajorMajor incident
- OutageMajor incident
Verceland v0Telemetry data loss for Drains
Vercel reported major telemetry delivery loss for Drains, recorded as starting and resolving at 2026-07-23 19:00 UTC (computed duration: 0 min). Its update identifies the affected window as 19:12–19:18 UTC: traces and events are unrecoverable, while logs remain accessible and exportable in the Logs UI dashboard. A fix was deployed; additional monitoring is being added.
- OutageCritical incident
PerplexityComputer sandbox issues
Perplexity reported critical Computer sandbox issues starting at 2026-07-23 17:48 UTC, lasting 25 min and resolved at 2026-07-23 18:14 UTC. The vendor identified the problem and rolled back the impacted services; no specific cause was stated.
- OutageMajor incident
MongoDB AtlasCluster connectivity issues in Azure westusEvent
MongoDB Atlas reported a major outage affecting some Azure westus clusters: intermittent connection failures, inter-node communication issues, nodes appearing down, and delayed cluster modifications. It started 2026-07-23 16:21 UTC and resolved 2026-07-23 20:28 UTC (4 h 6 min); Azure confirmed networking issues, and recovery completed after Azure rolled out mitigation.
- OutageMajor incident
OptimizelyLogin results in 429 errorEvent
Optimizely reported a major outage in which login returned 429 errors, affecting access to some products through Optimizely Identity. It started at 2026-07-23 15:26 UTC and was resolved at 2026-07-23 18:41 UTC, lasting 3 h 15 min; Optimizely attributed it to a disruption with its identity provider, Okta.
- OutageCritical incident
JFrogJFrog Cloud Platform outage affecting subset of customers in Azure US West regionEvent
A critical JFrog Cloud Platform outage affected a subset of customers using Artifactory and Security - Xray in Azure US West (California), from 2026-07-23 15:04 UTC to 2026-07-23 20:32 UTC, lasting 5 h 27 min. JFrog reported several Azure backend service outages, implemented a fix, and marked the incident resolved.
- DegradationMajor incident
InngestFunction processing delaysEvent
Inngest reported major function-processing delays starting 2026-07-23 14:17 UTC, resolved at 2026-07-23 15:24 UTC (1 h 6 min); delays began around 14:03 UTC. An issue publishing to a new Kafka topic delayed function scheduling; the team isolated the topic and scaled consuming services to clear the backlog. No events were dropped.
- OutageMajor incident
Box[Medium] Issues with Box HubsEvent
Box Hubs users were unable to load the Hubs gallery; the vendor recorded major impact. The incident started at 2026-07-23 14:14 UTC and was resolved at 2026-07-23 14:30 UTC, with a computed duration of 15 min. Box reported identifying the underlying cause without specifying it and confirmed full functionality was restored.
- MajorMajor incident
- DegradationMajor incident
Box[Medium] Issues with File Requests
Box reported major impact to File Request, with users potentially experiencing delayed metadata updates when uploading files. The incident started 2026-07-23 09:45 UTC and was resolved 2026-07-23 11:42 UTC, lasting 1 h 56 min; Box confirmed full functionality was restored.
- OutageMajor incident
Verceland v0Timeouts loading charts and observability data in Dashboard
Vercel reported a major incident causing Dashboard chart and observability-data loading timeouts for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. It lasted 45 min, from 2026-07-23 07:33 UTC to 2026-07-23 08:18 UTC. Vercel identified the source and implemented a fix, with recovery reported at 07-23 07:55 UTC.
- OutageCritical incident
v0Dashboard authentication errors
v0 reported a critical incident involving dashboard authentication errors that made the dashboard inaccessible for some users. It started at 2026-07-23 06:47 UTC and lasted 54 min, resolving at 2026-07-23 07:41 UTC; a fix was implemented by 2026-07-23 07:08 UTC.