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.
Wednesday, August 26
9 incident changes
- OutageMajor incident
MixpanelDegraded Query API Performance impacting US Projects
Mixpanel reported a major Query API degradation causing HTTP 500 errors and report-loading failures for US Data Residency projects; EU and IN projects were unaffected. It started at 2026-08-26 21:39 UTC and resolved at 2026-08-26 22:45 UTC, lasting 1 h 6 min; a fix was implemented, and no customer data was lost.
- OutageMajor incident
DremioEngine scaling issues in Dremio Cloud (US)
Dremio Cloud (US) reported a major outage preventing some classic engines from starting or scaling, from 2026-08-26 21:25 UTC to 2026-08-26 21:55 UTC (30 min). A provisioning artifact was inadvertently removed during a compliance-related infrastructure change; running engines were unaffected. A fix was applied and normal operations confirmed.
- DegradationCritical incident
GitHub Copilotand GitHubIncident with ActionsHN
Critical Actions and Pages degradation lasted 2 h 49 min, from 2026-08-26 15:11 UTC to 2026-08-26 18:01 UTC. Actions jobs failed to start, then experienced delays exceeding five minutes; Pages performance degraded. Saturated database-primary writes triggered the disruption; failover did not fully restore service. Queues recovered, but 3.7% of early larger-runner jobs remained stuck pending cancellation.
- DegradationMajor incident
Otter.aiDelayed Summary and Speaker tagging
Otter.ai reported a major incident delaying Summary and Speaker tagging and also impacting Otter Chat. It started at 2026-08-26 13:46 UTC and lasted 31 h 38 min, resolving at 2026-08-27 21:24 UTC when Otter said its systems were fully restored.
- DegradationMajor incident
DrataPublic API in US region degraded
Drata’s major US Public API degradation caused request failures and potentially incorrect framework/control readiness data from 2026-08-26 13:32 UTC to 2026-08-28 23:58 UTC (2 days 10 h). No data was lost; EU and APAC were initially unaffected. Drata deployed fixes and reported normal operation at resolution, with no customer action required.
- OutageCritical incident
SmartsheetSheets in Smartsheet US are failing to load
Smartsheet reported a critical US incident affecting sheet loading, Reports, Dashboards, and premium apps including Dynamic View, WorkApps, Resource Management, and Control Center. It started at 2026-08-26 13:28 UTC and resolved at 2026-08-26 18:23 UTC, lasting 4 h 55 min. Smartsheet implemented a fix and monitored recovery.
- OutageMajor incident
CensusFacebook (Meta) Sync Failures - API access disrupted
Facebook (Meta) syncs failed with “API access disrupted” in a major incident affecting Census Sync Management UI and Sync Engine from 2026-08-26 13:09 UTC to 2026-08-26 14:11 UTC (1 h 2 min). Census identified an Activations Meta app issue and implemented a fix; all affected syncs will recover on their next triggered or scheduled run.
- OutageMajor incident
Figma reported a major MCP disruption preventing some Codex and ChatGPT users from seeing tools such as use_figma. The incident started at 2026-08-26 12:08 UTC and resolved at 2026-08-26 16:19 UTC (computed duration: 4 h 10 min); Figma stated impact began at 10:14 UTC and recovery began at 14:03 UTC.
- OutageMajor incident
v0and VercelFailures logging in with Vercel CLI
Vercel CLI login (vc login) experienced errors in a major-impact incident from 2026-08-26 03:06 UTC to 2026-08-26 04:28 UTC, lasting 1 h 22 min. The vendor reported identifying the source and testing a fix before marking the incident resolved; affected customers had trouble logging in through the CLI.
Tuesday, August 25
13 incident changes
- OutageMajor incident
BuildkiteBuildkite service disruption
Buildkite reported a major site-wide outage starting 2026-08-25 22:55 UTC, resolved 2026-08-26 00:18 UTC (1 h 22 min). Internal DNS failure blocked new builds and delayed job dispatch; web, APIs and notifications were affected. Mitigations restored service; no build requests were lost. The postmortem places customer disruption at 22:47 UTC to 23:16 UTC.
- OutageMajor incident
SalesforceMule Soft Service Disruption: Anypoint MQ-Broker-eu-west-1
Salesforce reported a major disruption to Anypoint MQ-Broker-eu-west-1 in the EU region, starting 2026-08-25 20:01 UTC and lasting 1 h 49 min. Customers may have been unable to authenticate, retrieve data, or initiate new jobs, with affected requests returning 5xx errors. Service was restored at 2026-08-25 21:50 UTC and confirmed operating normally.
- OutageCritical incident
SemgrepWidespread errors on Semgrep AppSec Platform
Semgrep reported a critical incident affecting Dashboard and Scans and CI/CD, starting 2026-08-25 19:21 UTC and lasting 2 h 40 min. A bad release caused widespread platform failures; rollback restored stability, and a successful release fully resolved the issue at 2026-08-25 22:01 UTC.
- OutageMajor incident
WorkOSDashboard sign-in errors
WorkOS reported a major Dashboard sign-in outage that could prevent users from authenticating, starting 2026-08-25 17:35 UTC and resolved at 2026-08-25 18:41 UTC, with a computed duration of 1 h 5 min. A fix was applied at 17:41 UTC and confirmed to have resolved elevated sign-in errors at 17:54 UTC.
- OutageMajor incident
Jupyter (Anaconda)Anaconda backend service outage
Anaconda reported a major backend outage affecting APIs, authentication, repositories, EduBlocks and Pyscript, involving an inability to spawn new compute nodes. The recorded start was 2026-08-25 17:10 UTC, though reported impacts began at 15:45 UTC. A fix was implemented; resolution was recorded at 2026-08-25 18:52 UTC, with a computed duration of 1 h 41 min.
- DegradationMajor incident
CloudsmithRequest latency and timeout
Cloudsmith reported a major incident affecting metadata requests and package downloads, starting 2026-08-25 16:38 UTC and lasting 1 h 30 min. Customers experienced latency and timeouts between 16:04 and 17:13 UTC, with a recurrence between 18:48 and 19:08 UTC; Cloudsmith confirmed normal operations at 08-26 07:55 UTC.
- OutageMajor incident
Pinecone[SERVERLESS][GCP][us-central1] 5xx errors on some read and write requests
Pinecone reported a major incident affecting Serverless Indexes in GCP us-central1, with 5xx errors on some read and write requests. It started at 2026-08-25 15:50 UTC and was resolved at 2026-08-25 16:11 UTC, lasting 21 min; Pinecone stated that a fix was implemented.
- DegradationMajor incident
GitLabGeneral slowness and intermittent 502s on Gitlab.com
GitLab.com’s API and Website experienced slowness and intermittent 502 errors in a major-impact incident starting 2026-08-25 09:59 UTC and lasting 14 h 13 min. GitLab reported no active user impact for several hours before resolution and confirmed a fix was implemented at 2026-08-26 00:12 UTC; no specific cause was disclosed.
- DegradationMajor incident
Confluenceand JiraNotifications are delayed
Confluence reported a major incident delaying email, mobile and slack notifications for Jira, JSM and Confluence, starting 2026-08-25 08:42 UTC and resolved at 2026-08-25 14:33 UTC, lasting 5 h 51 min. Teams applied corrective measures in one impacted region; the vendor confirmed normal service for all customers without specifying a cause.
- OutageMajor incident
BigCommerceSingle Sign-On (Microsoft) login issue for subset of stores
BigCommerce reported a major Control Panel incident affecting Microsoft Azure AD Single Sign-On login for a subset of stores. It started at 2026-08-25 06:56 UTC and was resolved at 2026-08-25 07:25 UTC, lasting 29 min; BigCommerce identified the issue and reported implementing a fix before resolution.
- DegradationCritical incident
Box[Critical] Issue with Downloads
Box reported a critical download issue affecting Box Zones users in the Asian region, who may have been unable to download files. It started at 2026-08-25 06:53 UTC and was resolved at 2026-08-25 07:37 UTC, lasting 44 min; Box reported improvement after remediation steps, and its postmortem also noted ZIP downloads were affected.
- DegradationMajor incident
ConfluentElevated error rates and latencies in Azure Southeast Asia region
Confluent reported a major Confluent Cloud degradation in Azure Southeast Asia, with elevated errors, latency and intermittent connectivity affecting produce/consume availability. Recorded from 2026-08-25 04:17 UTC to 2026-08-25 07:29 UTC (3 h 11 min), it reportedly began around 03:13 UTC and was associated with a Microsoft Azure disruption; services returned to normal.
- OutageCritical incident
Snowflake reported a critical outage in Azure - Southeast Asia (Singapore), where infrastructure connectivity issues may have prevented customers from accessing services. It started at 2026-08-25 03:53 UTC and was resolved at 2026-08-25 04:35 UTC, lasting 41 min; Snowflake implemented a fix and confirmed restoration through monitoring. Other regions were unaffected.
Monday, August 24
12 incident changes
- OutageMajor incident
GitLabInvestigating GitLab Agent for Kubernetes (KAS) Deployment Failures
GitLab reported a major incident affecting GitLab Agent for Kubernetes (KAS), with deployment failures from 2026-08-24 21:22 UTC to 2026-08-24 22:45 UTC, lasting 1 h 23 min. GitLab identified a recent change believed to contribute to the failures, rolled it back, and confirmed resolution.
- OutageMajor incident
Box[Medium] Issue with Uploads
Box reported a major-impact upload incident starting 2026-08-24 21:21 UTC, resolved at 2026-08-24 22:03 UTC (41 min). Users could encounter upload errors or slowness across the Box web application and API; the postmortem also noted affected write operations. Box reported remediation and improvement but did not specify the cause or fix in the available evidence.
- OutageMajor incident
Databricks reported a major Lakebase outage on AWS in EU Central 1, affecting database creation, access, administrative operations and queries. Customer impact ran from 20:22 UTC to 22:08 UTC on August 24, 2026; the incident record started at 2026-08-24 21:12 UTC and was resolved at 2026-08-24 22:55 UTC (1 h 43 min).
- OutageMajor incident
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.
- OutageCritical incident
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.
- OutageMajor incident
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.
- CriticalCritical incident
- OutageMajor incident
- DegradationMajor incident
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.
- OutageMajor incident
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.
- CriticalCritical incident
- MajorMajor incident
Sunday, August 23
1 incident change
- OutageMajor incident
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.
Friday, August 21
9 incident changes
- MajorMajor incident
- OutageCritical incident
Lever500 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.
- MajorMajor incident
- OutageMajor incident
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.
- OutageMajor incident
LatticeAdmin 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.
- OutageCritical incident
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.
- MajorMajor incident
- CriticalCritical incident
- OutageCritical incident
DrataBrief 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.
Thursday, August 20
1 incident change
- OutageMajor incident
SalesforceService 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.