What vendors changed

DDescriptShare Page Outage

Descript reported a major Share Page outage with a recorded start of 2026-08-24 18:56 UTC and resolution of 2026-08-24 17:15 UTC; duration is unknown. The vendor said a fix had been implemented and the issue was resolved.

DigitalOceanCloud Control Panel and API

DigitalOcean reported a critical Cloud Control Panel/Public API outage starting 2026-08-24 17:14 UTC, resolved 2026-08-25 19:04 UTC (25 h 49 min). Customers faced API errors and panel access failures; mitigation restored access. The postmortem reports 3.5 hours of active degradation, peaking at 25% errors; running Droplets, network routing and Volumes remained functional.

SnowflakeINC20000173

Snowflake reported a major Snowsight authentication outage in AWS - US West (Oregon), causing immediate logout after successful authentication. The vendor stated a start of 15:00 UTC August 24, 2026; recorded duration was 1 h 41 min, resolved at 2026-08-24 18:03 UTC. Snowflake attributed the issue to a system configuration and implemented a fix.

WiseDelayed AED payments

PaddleRetain

Paddle reported a major Retain outage, recorded from 2026-08-24 08:35 UTC to 2026-08-24 09:22 UTC (47 min), though its initial update said the issue began around 7:56 UTC. A fix was deployed at 09:11 UTC, and all services were operating normally at resolution.

GitHuband GitHub CopilotElevated errors on Fable 5 due to upstream provider

GitHub reported a major degradation affecting Claude Fable 5 in Copilot products and IDE surfaces, with elevated errors and requests failing mid-response; no other models were impacted. The incident started at 2026-08-24 07:12 UTC and was resolved at 2026-08-24 07:58 UTC, lasting 46 min. GitHub attributed it to an upstream provider issue, resolved through the provider’s mitigation.

Claudeand AnthropicElevated errors for multiple modelsHN

Claude reported a major incident involving elevated errors across claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork, affecting Claude Mythos 5, Claude Fable 5, Claude Opus 5 and Claude Opus 4.8. It started 2026-08-24 05:06 UTC and was resolved 2026-08-24 08:30 UTC, lasting 3 h 24 min.

TTelnyxTelnyx Cloud Storage Outage Across All Regions

HHarnessFeature Management & Experimentation (FME) user interface unavailable

Fly.ioNetwork Issues in LAX Region

Fly.io reported a major network incident in the Los Angeles (LAX) region, where apps could experience higher latency or be unreachable. It started at 2026-08-23 01:28 UTC and was resolved at 2026-08-23 02:10 UTC, lasting 41 min. Fly.io stated that upstream networking issues had resolved.

E2BEU region sandbox traffic connection issues

LLever500 Errors when attempting to access Lever

A critical incident caused 500 errors when accessing Lever, affecting Global Data Center - LeverTRM - Hire and Hire. It started at 2026-08-21 20:12 UTC and was resolved at 2026-08-24 14:16 UTC, lasting 2 days 18 h. Lever implemented a fix at 08-21 20:29 UTC and promised an RCA within 7-10 business days.

SemaphoreIssues with Bitbucket integration

CloudsmithNew upstream packages may not appear in repositories

Cloudsmith reported a major global package-caching outage affecting Package Downloaded webhooks; package pulls remained unaffected. Recorded from 2026-08-21 18:15 UTC to 2026-08-21 18:54 UTC (39 min), impact reportedly began approximately 17:00 UTC. Caching resumed after a fix; packages pulled between 17:00 and 18:45 UTC were missing from repositories and will be cached on subsequent pulls.

LLatticeAdmin Compensation Cycle Recommendations page showing "Something Went Wrong" error

Lattice reported a major incident affecting the admin Compensation Cycle Recommendations table, which showed a "Something Went Wrong" error, starting 2026-08-21 16:30 UTC. It was resolved at 2026-08-21 18:24 UTC, lasting 1 h 53 min. A fix was deployed; admins were instructed to refresh the page to see data successfully.

GitLab403 errors across GitLab.com

GitLab reported a critical incident involving elevated 403 errors across GitLab.com, affecting CI/CD, Git Operations, and Website. It started at 2026-08-21 15:56 UTC and was resolved at 2026-08-21 16:25 UTC, lasting 29 min; a fix was already in place at the first update, and error rates returned to normal.

MintlifyDelayed documentation updates from GitHub

MMaven Centralrepo1.maven.org is down

DDrataBrief SafeBase App Request Failures

Drata reported critical SafeBase request failures: some requests errored or timed out because edge traffic filtering rules blocked legitimate traffic. Recorded start and resolution were both 2026-08-21 01:00 UTC (computed duration: 0 min), although the vendor described approximately six minutes of failures on August 20.

SSalesforceService Disruption: Core Service

Salesforce reported a critical Core Service disruption on CS246 starting 2026-08-20 23:37 UTC, with users losing access to services hosted on that instance. The incident lasted 45 min and was resolved at 2026-08-21 00:22 UTC after a site switch; no technical cause was confirmed.

SocketFirewall Events rejected/dropped

Socket reported a major Socket API incident in which the Events collection system incorrectly rejected Firewall Events. It started at 2026-08-20 23:05 UTC and was resolved at 2026-08-21 01:06 UTC, lasting 2 h 1 min; customers’ Firewall Events could be rejected or dropped during that period.

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.

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.

AAblyElevated 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.

CCriblOAuth secrets containing C.* expressions fail to resolve during authentication

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.

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.

HHarnessAll modules are running slow in Prod1/2/3/4 due to cloud provider incident

CConfluentElevated 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.

PPandaDocSome 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.

RenderDeployment Issues

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.

GGoogle CloudWe are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.

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.

SnowflakeINC20000168

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.

MMaterializeUpstream vendor causing authentication related issues

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.

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.

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.

SSalesforceMarketing 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.

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.

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.

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.

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.

RRunPodEUR-NO-2 Network Issue

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.