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.
Thursday, August 20
20 incident changes
- OutageMajor incident
DynatraceMonitoring Visibility Impacted for AWS Lambda Layers on Node.js 22
Dynatrace reported a major outage: Classic Lambda layers on nodejs:22.mainline.v95 caused Lambda timeouts and lost OneAgent monitoring. It ran from 2026-08-20 21:10 UTC to 2026-08-24 09:54 UTC, lasting 3 days 12 h. OneAgent 1.343 fixes the issue for SaaS customers; customers unable to upgrade can downgrade to a previously working runtime.
- OutageMajor incident
Claudeand AnthropicElevated errors on requests to multiple models
Claude reported a major incident involving elevated errors on requests to multiple models, affecting claude.ai, Claude API (api.anthropic.com), Claude Code, and Claude Cowork. It started at 2026-08-20 19:16 UTC and was resolved at 2026-08-20 19:42 UTC, lasting 26 min; no cause or fix details were stated.
- OutageMajor incident
AblyElevated Error Rate in ap-southeast-1
Ably reported a major incident with elevated errors in ap-southeast-1, affecting Ably Pub/Sub - Asia-Pacific (Singapore) and Asia-Pacific (Singapore). It started at 2026-08-20 19:07 UTC and was resolved at 2026-08-20 19:10 UTC; the computed duration was 2 min. No cause or fix was stated.
- OutageMajor incident
- OutageMajor incident
v0and VercelNew container functions are failing
v0 reported a major Functions incident: newly deployed container functions could return 5XX errors starting at 2026-08-20 17:46 UTC. Customers could temporarily use a previously working deployment; a fix was deployed at 2026-08-20 18:23 UTC. The incident was resolved at 2026-08-20 18:34 UTC, lasting 47 min.
- OutageMajor incident
RetoolReact App Builder Sandbox Installs May Fail to Install Dependencies
Retool reported a major React App Builder incident: downstream dependency issues could prevent sandbox installation and connection on Cloud and Self-Hosted instances. It ran from 2026-08-20 17:26 UTC to 2026-08-20 23:20 UTC (5 h 54 min); Cloud recovered at 17:30 UTC, and self-hosted fixes shipped in 4.0.12-stable and 4.43.0-edge.
- DegradationMajor incident
- DegradationMajor incident
ConfluentElevated error rates and latency in GCP us-west1
Confluent Cloud reported a major incident affecting Kafka clusters in GCP us-west1, with elevated latency, request timeouts, and increased error rates. It started at 2026-08-20 17:10 UTC and was resolved at 2026-08-20 20:18 UTC, lasting 3 h 7 min. Confluent said the GCP issues were mitigated and monitoring showed no remaining impact.
- OutageMajor incident
PandaDocSome users experience issues with creation and viewing of documents
PandaDoc reported a major incident affecting document creation and viewing, with creating/editing, sending and uploading components listed for US & Global. It started at 2026-08-20 17:03 UTC and was resolved at 2026-08-20 21:42 UTC, lasting 4 h 38 min. PandaDoc reported mitigation at 17:20 UTC with no further degradation; no root cause was stated.
- OutageMajor incident
Render reported a major Builds and Deploys outage across Frankfurt, Ohio, Oregon, Singapore and Virginia, starting 2026-08-20 15:47 UTC and resolved at 2026-08-20 19:40 UTC (3 h 53 min). Render identified an upstream Google Cloud issue; Free Web Services builds, deploys and spin-up were temporarily disabled, then re-enabled during recovery.
- OutageMajor incident
- DegradationCritical incident
GitHub Copilotand GitHubIntermittent failures creating agent tasks
GitHub Copilot reported a critical incident starting 2026-08-20 14:43 UTC, resolved 2026-08-21 00:37 UTC (9 h 54 min). Some Copilot Cloud Agent users saw task status/results delayed up to 60–90 minutes, while tasks continued running and completing. GitHub cited a regional third-party cloud database outage and deployed a fix.
- OutageMajor incident
Snowflake reported a major outage in Azure - East US 2 (Virginia): customers may have been unable to connect through private connectivity solutions such as PrivateLink. It started at 2026-08-20 13:47 UTC and was resolved at 2026-08-20 15:43 UTC, lasting 1 h 56 min. The third-party cloud platform implemented mitigation; Snowflake verified service restoration.
- OutageMajor incident
- DegradationMajor incident
Elastic CloudIssue when creating Serverless projects in Azure eastus region
Elastic Cloud reported a major incident affecting new Serverless project initialization in Azure eastus, causing longer creation times due to an upstream Azure storage component issue. It started at 2026-08-20 12:48 UTC and lasted 3 h 34 min, resolving at 2026-08-20 16:22 UTC after Azure's storage issues were resolved and creation times returned to normal.
- OutageMajor incident
v0and VercelLogs unavailable to query in Dashboard
v0 reported a major outage preventing runtime log queries in the Dashboard from 2026-08-20 11:14 UTC to 2026-08-20 11:25 UTC, lasting 11 min. Log ingestion and build-log queries were unaffected. A fix restored runtime-log queries at 11:21 UTC, with full recovery confirmed at 11:25 UTC.
- OutageMajor incident
Fly.ioMPG (v1) partially down in ORD
Fly.io reported a major partial outage of MPG (v1) in ORD from 2026-08-20 07:25 UTC to 2026-08-20 07:57 UTC, lasting 32 min. An issue with the ord-0 Fly Kubernetes cluster left many MPG clusters unable to restart; a fix was implemented at 07:32 UTC, and the incident was resolved.
- OutageMajor incident
SalesforceMarketing Cloud Disruption: Marketing Cloud Core Service
Salesforce reported a major Marketing Cloud Core Service disruption affecting 1 instance, starting at 2026-08-20 03:37 UTC and resolved at 2026-08-20 04:03 UTC, lasting 26 min.
- OutageMajor incident
TailscaleCoordination service issues
Tailscale reported a major coordination service incident with elevated error rates, starting 2026-08-20 00:58 UTC and resolved at 2026-08-20 03:22 UTC, lasting 2 h 24 min. A fix was deployed by 02:38 UTC; no cause was stated.
- OutageMajor incident
Box[Medium] Issue with Microsoft Office Integration and Box Edit
Box reported a major-impact incident causing errors or slowness accessing Microsoft Office via Box and using Box Edit, from 2026-08-20 00:31 UTC to 2026-08-20 01:44 UTC (1 h 13 min). Box took remediation steps and confirmed full functionality was restored; no specific cause or fix was stated.
Wednesday, August 19
12 incident changes
- OutageMajor incident
MixpanelIssues Populating Event Properties in dropdown menus
Mixpanel reported a major incident affecting event-property population in dropdown menus across EU, IN and US application availability. It started at 2026-08-19 23:20 UTC and was resolved at 2026-08-20 03:05 UTC, lasting 3 h 44 min. A fix was implemented before resolution; no cause was stated.
- OutageMajor incident
Box[Medium] Issues with Multiple Box Services
Box reported a major-impact incident affecting Login, All Files, Uploads, Downloads and Box API. The archived start and resolution are both 2026-08-19 22:00 UTC (computed duration: 0 min). Box said no further impact was observed and marked the issue resolved; a preliminary postmortem was later posted.
- OutageCritical incident
RunPod reported a critical network connectivity outage in EUR-NO-2 starting at 2026-08-19 19:06 UTC. It lasted 48 min and was resolved at 2026-08-19 19:54 UTC, when RunPod confirmed the data center network was operating normally.
- OutageCritical incident
- OutageMajor incident
SurveyMonkeyBlank page for Multi-Survey Analysis
SurveyMonkey’s Multi-Survey Analysis displayed a blank page in a major-impact incident starting at 2026-08-19 17:23 UTC. A fix was implemented, and the incident was resolved at 2026-08-19 17:37 UTC after 14 min.
- DegradationMajor incident
QuickBooks OnlineQuickbooks Online Latency Issue
QuickBooks Online reported a major latency incident affecting some customers in Canada, EMEA and the United States, starting 2026-08-19 14:30 UTC and resolved at 2026-08-19 16:54 UTC (2 h 23 min). Engineering implemented a fix, and the final update confirmed all services were restored; no specific cause was disclosed.
- OutageMajor incident
- DegradationMajor incident
- OutageMajor incident
AssemblyAIEU endpoint session failures on Universal 3.5 Pro Realtime
AssemblyAI reported a major Universal 3.5 Pro Realtime outage: EU endpoint users could not create streaming sessions and received code 3005 during 13:00–13:12 UTC; US users were unaffected. The incident started at 2026-08-19 13:17 UTC and resolved at 2026-08-19 13:24 UTC (7 min), after a fix restored session creation.
- OutageCritical incident
DigitalOceanMajor Service Interruption in MKC1
DigitalOcean reported a critical MKC1 outage starting 2026-08-19 11:10 UTC, disrupting GPU workloads and Serverless Inference, with DOKS worker nodes entering NotReady states. It was marked resolved at 2026-08-19 19:34 UTC after 8 h 24 min; the regional control plane and other listed services were healthy, but GPU Droplets remained impacted while restoration continued.
- DegradationMajor incident
- OutageMajor incident
Tuesday, August 18
13 incident changes
- OutageMajor incident
ZapierZapier Functions temporarily unavailable
Zapier Functions had a major outage starting 2026-08-18 23:50 UTC, resolved at 2026-08-18 23:58 UTC after 8 min. Users could not create, edit, or run Functions, and migrations could be disrupted; Zaps and other Zapier services were unaffected, and no data loss occurred.
- OutageCritical incident
Grafana CloudCloud Logs read path outage on eu-west-2
Grafana Cloud reported a critical Cloud Logs read outage in eu-west-2 on loki-prod-012, affecting Explore, dashboards and alert evaluation querying Logs. The recorded start was 2026-08-18 22:53 UTC and resolution 2026-08-18 22:00 UTC, while the vendor described impact between approximately 22h15 and 22h23 UTC; duration is unknown.
- DegradationMajor incident
- OutageMajor incident
- OutageCritical incident
NetlifyElevated HTTP 500 errors serving sites and the Netlify UI
Netlify recorded a critical incident starting at 2026-08-18 20:00 UTC, with a computed duration of 0 min and status resolved. Its update reports error pages for some Netlify-hosted site visitors and dashboard users between 20:02 and 20:08 UTC, with normal service restored at 20:08 UTC.
- DegradationMajor incident
AstronomerIncorrect scheduler heartbeat metrics being reported
Astronomer reported a major degradation from 2026-08-18 18:51 UTC to 2026-09-10 22:19 UTC, lasting 23 days 3 h. A metrics reporting bug falsely flagged missed scheduler heartbeats, affecting Astro UI dashboard and monitoring visibility; task execution, scheduling, and workflow processing were unaffected. Astronomer reported rolling out a fix and later marked the issue resolved.
- OutageMajor incident
SegmentIntermittent Segment application login errors
Segment reported a major incident causing intermittent login errors for a subset of customers, affecting Web Interface (EU) and Web Interface (US). It started at 2026-08-18 17:49 UTC and was resolved at 2026-08-18 22:02 UTC, lasting 4 h 13 min; login was reported operating normally at 18:38 UTC.
- DegradationMajor incident
- OutageCritical incident
GitLab500 errors when fetching commits on GitLab.com
GitLab.com reported a critical incident causing 500 errors for a subset of requests when fetching commits, with API, CI/CD, Git Operations and Website listed as affected components. It started at 2026-08-18 13:55 UTC and was resolved at 2026-08-18 17:30 UTC, lasting 3 h 35 min. Error rates returned to normal; no cause or fix was stated.
- OutageMajor incident
Snowflake reported a major outage affecting Cortex Code in Snowsight in AWS - US East (N. Virginia), from 2026-08-18 12:58 UTC to 2026-08-18 14:51 UTC (1 h 53 min). Customers could encounter internal server errors; Snowflake identified container scheduling issues in its compute infrastructure and implemented a fix.
- OutageMajor incident
LovableWe are currently experiencing issues with our Shopify integration.
Lovable reported a major Shopify integration outage: creating new Lovable apps with Shopify was not working. It started at 2026-08-18 09:49 UTC and was resolved at 2026-08-18 10:22 UTC, lasting 32 min; Lovable confirmed the integration was restored.
- OutageMajor incident
GitHuband GitHub CopilotIncident with Actions
GitHub reported a major Actions outage starting 2026-08-18 09:36 UTC, resolved at 2026-08-18 10:23 UTC (46 min). Customers could not run jobs on Actions Larger Runners or view/manage Actions Runners and Runner Groups through the GitHub UI and API; GitHub attributed the failures to backend requests resolving essential metadata.
- DegradationMajor incident
ElevenLabsInbound Twilio calls experiencing intermittent connection failures
ElevenLabs reported a major degradation affecting <1% of inbound Twilio calls, preventing agent connections; outbound calls and other traffic were unaffected. The incident ran from 2026-08-18 06:00 UTC to 2026-08-18 12:43 UTC (6 h 43 min). A configuration error was rolled back; calls connected normally since ~11:00 UTC, with no customer action needed.