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 shown in UTC.
Follow every change in a feed reader: Atom feed.
Tuesday, August 18
16 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.
- OutageMajor incident
Fireworks AIKimi K3 service disruption
Kimi K3 experienced elevated errors and degraded availability during a major incident starting 2026-08-18 05:52 UTC, caused by connectivity issues affecting one region. Availability recovered by 06:22 UTC; the incident was resolved at 2026-08-18 07:01 UTC after 1 h 9 min.
- DegradationMajor incident
AstronomerIntermittent task instances failures.
Astro Hosted experienced intermittent task instance failures with major impact from 2026-08-18 04:17 UTC to 2026-08-18 07:36 UTC, lasting 3 h 18 min. Astronomer identified an issue affecting an internal rollout related to the pre_execute Airflow hook and resolved the incident after completing a fix rollout across all Astro deployments.
- OutageMajor incident
SurveyMonkeyExcel/CSV Exports are failing
SurveyMonkey reported a major outage: all Summary and Responses Data exports to Excel/CSV/SPSS failed, while PDF and PPT exports still worked. It started at 2026-08-18 00:42 UTC and was resolved at 2026-08-18 01:03 UTC, lasting 20 min; a fix was implemented.
Monday, August 17
10 incident changes
- OutageCritical incident
MatillionService Disruption (All Regions) - Projects Not Accessible
Matillion reported a critical disruption that made projects inaccessible across all regions, affecting Designer and Pipeline Execution in AU, EU and US regions. It started at 2026-08-17 17:53 UTC and lasted 55 min, resolving at 2026-08-17 18:48 UTC; a fix was implemented, but no cause was stated.
- OutageCritical incident
MatillionService Disruption (AU Region) - Projects Not Accessible
Matillion reported a critical AU Region outage that made projects inaccessible, affecting Designer and Pipeline Execution. It started at 2026-08-17 17:40 UTC and was resolved at 2026-08-17 17:42 UTC; the computed duration was 1 min. No cause or specific fix was stated.
- OutageMajor incident
DockerIssues building DHI customizations
Docker reported a major incident affecting builds of DHI customizations from 2026-08-17 15:21 UTC to 2026-08-17 22:04 UTC, lasting 6 h 43 min. Docker attributed the disruption to a third-party vendor outage and confirmed customizations were going through after the GitHub outage ended.
- OutageCritical incident
SalesforceService Disruption: Marketing Cloud Core Service
Salesforce reported a critical Marketing Cloud Core Service disruption affecting 116 instances. It started at 2026-08-17 15:18 UTC and was resolved at 2026-08-17 15:57 UTC, lasting 39 min.
- OutageMajor incident
dbt LabsGit Failures in dbt Platform
dbt Labs reported a major Git outage starting 2026-08-17 15:02 UTC, lasting 6 h 19 min and resolving at 2026-08-17 21:21 UTC. A widespread GitHub outage caused failures in dbt deps, repository connections, Studio IDE, Scheduled Jobs and GitHub authentication; dbt confirmed all affected systems were functioning normally.
- DegradationMajor incident
CircleCIGitHub Incidents impacting CircleCI functionality
CircleCI reported major degradation affecting pipeline triggering and login, with possible failures reporting running jobs’ status to GitHub Pull Requests. The incident ran from 2026-08-17 14:04 UTC to 2026-08-17 19:05 UTC, lasting 5 h 1 min. CircleCI attributed the disruption to a GitHub incident and resolved it after GitHub’s APIs appeared to be operating normally.
- OutageCritical incident
GitHuband GitHub CopilotIncident with GitHub.comHN
GitHub reported a critical outage affecting Issues, Pull Requests, APIs, Actions and Copilot, with elevated errors and latency. Peak web/API error rates were approximately 20%; archive and raw-content downloads reached approximately 50%. It started 2026-08-17 13:40 UTC and was resolved at 2026-08-17 21:15 UTC, lasting 7 h 35 min.
- OutageCritical incident
SalesforceService Disruption: Marketing Cloud Core Service
Salesforce reported a critical disruption to Marketing Cloud Core Service affecting 105 instances. It started at 2026-08-17 11:21 UTC and was resolved at 2026-08-17 11:58 UTC, lasting 37 min; no cause or fix was stated.
- OutageMajor incident
SalesforceCc Storefront SAnd Or Business Manager Unavailable: B2 CCore
Salesforce reported a major B2 CCore outage affecting POD248, intermittently blocking Storefronts and Business Manager access and causing 500 errors. It ran from 2026-08-17 11:03 UTC to 2026-08-17 12:36 UTC, lasting 1 h 33 min. Salesforce attributed the disruption to a known third-party vendor issue affecting the database network connection.
- DegradationMajor incident
GitLabProject and Group Deletions Delayed
GitLab.com reported a major degradation affecting immediate and scheduled project and group deletions, leaving some visible past expected deletion dates. It ran from 2026-08-17 07:24 UTC to 2026-08-17 13:56 UTC (6 h 32 min). A fix reached production; project deletion queues cleared, and GitLab expected group deletions to continue processing.
Sunday, August 16
2 incident changes
- OutageMajor incident
ConvexAccount verification/team invite emails not working
Convex reported a major outage preventing dashboard emails, including team invitations and new account verification, across Business, Free & Starter, and Professional. It started at 2026-08-16 23:33 UTC and lasted 1 h 53 min, resolving at 2026-08-17 01:26 UTC; a fix was implemented at 2026-08-17 00:50 UTC.
- OutageCritical incident
Claudeand AnthropicService disruption on Claude servicesHN
Claude reported a critical disruption involving authentication issues on claude.ai, Claude Code, and Claude Cowork, plus degraded performance across those services, Claude Console, and the Claude API. It started at 2026-08-16 21:58 UTC and was resolved at 2026-08-16 22:34 UTC, lasting 35 min; a fix was deployed at 22:22 UTC.
Saturday, August 15
3 incident changes
- DegradationMajor incident
- OutageCritical incident
Brex reported a critical Mastercard Network outage affecting card authorization, causing transactions to be incorrectly declined. It started at 2026-08-15 04:49 UTC and was resolved at 2026-08-15 05:53 UTC, lasting 1 h 4 min; Brex said transactions should now be correctly processed.
- OutageMajor incident
Friday, August 14
14 incident changes
- OutageMajor incident
Anthropicand ClaudeElevated errors for Claude Fable 5
Claude Fable 5 requests on claude.ai experienced elevated errors, rated major. The incident started at 2026-08-14 23:57 UTC and resolved at 2026-08-15 00:27 UTC (30 min). Anthropic separately reported impact from 20:00 Aug 14, 2026 to 00:11 Aug 15 , 2026 UTC; no specific cause or fix was disclosed.
- OutageCritical incident
RunPodUS-IL-1 DC is Unavailable
RunPod’s US-IL-1 datacenter was unavailable due to a power outage, with critical impact, from 2026-08-14 21:30 UTC to 2026-08-15 03:40 UTC, lasting 6 h 10 min. Power was restored to most servers by 08-15 02:59 UTC; the vendor confirmed normal datacenter operation at resolution.
- DegradationMajor incident
Anthropicand ClaudeService disruption on Claude services
A major degradation affected Claude API (api.anthropic.com), Claude Code, and Claude Cowork. The incident started at 2026-08-14 20:30 UTC and was resolved at 2026-08-14 21:58 UTC (1 h 27 min); Anthropic reported customer impact from 20:14 to 20:38 UTC. A fix was deployed at 20:44 UTC, but no specific cause was disclosed.
- OutageMajor incident
Fly.io’s major secrets service outage blocked new app creation and secret updates; existing apps continued running. It lasted 1 h 3 min, from 2026-08-14 19:30 UTC to 2026-08-14 20:33 UTC. Fly.io cited a failed deployment and failed over the secrets database to a replica, after which the Machines API appeared healthy.
- OutageCritical incident
Snowflake reported a critical Snowsight outage in Azure - East US 2 (Virginia), blocking access/sign-in with “503 Service Unavailable” errors. Recorded from 2026-08-14 17:29 UTC to 2026-08-14 19:35 UTC (2 h 5 min), customer impact reportedly began at 17:05 UTC August 14, 2026. Snowflake implemented a fix for a system configuration issue and confirmed service restoration.
- OutageCritical incident
- OutageMajor incident
UnbounceElevated Page Server Errors (Asia Pacific Region)
Unbounce reported a major Page Servers outage in Asia Pacific: visitors to live pages could see gateway errors; no other regions were affected. It started at 2026-08-14 15:28 UTC and was resolved at 2026-08-14 17:42 UTC, lasting 2 h 14 min. Unbounce implemented a fix and reported health checks back to 100%.
- OutageMajor incident
GrammarlyUsers May Experience Login Issues Across Some Grammarly and Superhuman Products
Grammarly reported a major outage involving login issues across some Grammarly and Superhuman products and preventing some users from accessing Grammarly Editor documents. It lasted 2 h 33 min, from 2026-08-14 15:24 UTC to 2026-08-14 17:57 UTC; a fix was implemented and the incident was resolved.
- OutageCritical incident
Snowflake reported a critical Snowsight availability outage affecting Applications in AWS - US East (Ohio), with intermittent authentication failures and "service unavailable" errors. The incident started at 2026-08-14 15:19 UTC and resolved at 2026-08-14 16:28 UTC; recorded duration was 1 h 8 min. Automated recovery restored service; a postmortem links to an RCA on Snowflake Community.
- OutageMajor incident
RetoolErrors calling resources with Per-User authentication in Apps built with the New App Editor
Retool reported a major incident causing errors when calling resources with Per-User authentication in Apps built with the New App Editor. It started at 2026-08-14 15:06 UTC and was resolved at 2026-08-14 19:00 UTC, lasting 3 h 53 min. A fix was implemented by 2026-08-14 16:36 UTC; no cause was stated.
- OutageMajor incident
SanityElevated API and API CDN rates
Sanity reported a major incident affecting api.sanity.io and apicdn.sanity.io, with elevated error rates identified from 14:34 UTC until a fix restored normal rates at 14:40 UTC. The incident record started at 2026-08-14 14:46 UTC and was resolved at 2026-08-14 15:32 UTC; its recorded duration was 45 min.
- OtherMajor incident
Elastic CloudElasticsearch 9.5.1: false-positive matches in certain boolean queries
Elastic Cloud reported a major Elasticsearch 9.5.1 issue causing false-positive matches in boolean queries combining multi-value terms in must, filter, or should clauses with must_not on fields with disabled indexing. It ran from 2026-08-14 09:22 UTC to 2026-08-20 17:09 UTC (6 days 7 h); Elasticsearch 9.5.2 fixes it, and customers on 9.5.0 or 9.5.1 should upgrade.
- OutageMajor incident
DiscordIssue with establishing a call
Discord reported a major incident affecting call establishment from 2026-08-14 06:09 UTC to 2026-08-14 06:24 UTC, lasting 14 min. A fix was implemented by 2026-08-14 06:14 UTC, and the incident was resolved.
- OutageCritical incident