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.
Thursday, August 6
8 incident changes
- OutageMajor incident
MessageBird (Bird)Connectors failing for some customers.
MessageBird (Bird) reported a major outage affecting Connectors and CRM - Connectors for some customers in Asia (India), Europe and US (West). It started at 2026-08-06 17:05 UTC and was resolved at 2026-08-06 22:08 UTC, lasting 5 h 3 min. A fix was implemented, but the root cause was not disclosed.
- OutageCritical incident
RevenueCatRico is having issues
RevenueCat reported a critical Rico outage affecting AI features and Dashboard - AI features, with all service requests failing due to an upstream AI inference provider outage. The incident started at 2026-08-06 17:04 UTC and was resolved at 2026-08-06 18:14 UTC, lasting 1 h 10 min; the provider had recovered and Rico was operating normally by 17:16 UTC.
- DegradationCritical incident
GitHub Copilotand GitHubIncident with ActionsHN
GitHub Actions had critical degraded availability starting 2026-08-06 15:22 UTC, resolved at 2026-08-07 02:04 UTC; recorded duration was 10 h 41 min. Workflows failed or remained queued on GitHub-hosted and self-hosted runners, with infrastructure failures affecting 71% of runs at peak. Recovery instructions for stuck Actions Runner Controller pods were deletion or application redeployment.
- OutageMajor incident
- OutageCritical incident
RunPodEUR-NO-1 Network Storage Issue
RunPod reported a critical Network Storage issue in EUR-NO-1, affecting storage availability in that data center. The incident ran from 2026-08-06 13:47 UTC to 2026-08-06 15:38 UTC, lasting 1 h 51 min; RunPod confirmed network storage was resolved and operating normally, without stating a cause or specific fix.
- OutageMajor incident
CoralogixRUM data is unavailable for specific users
Coralogix reported a major RUM outage affecting some customers’ ability to view RUM data or access RUM-related features. It began at 2026-08-06 09:37 UTC and was resolved at 2026-08-06 10:15 UTC; the computed duration was 37 min. A fix was implemented, but no cause was stated.
- DegradationMajor incident
SentryDelayed Error ingestion in our US region
Sentry reported a major delay in US Error Ingestion from 2026-08-06 08:59 UTC to 2026-08-06 11:21 UTC, lasting 2 h 21 min. A fix was applied, new events returned to real-time processing, and all backlogged events were processed by resolution.
- OutageMajor incident
NotionBrief partial unavailability of notion.com
Notion reported a major outage affecting access to notion.com and Notion Sites, with possible issues loading or using Notion clients. The incident started at 2026-08-06 00:29 UTC and was resolved at 2026-08-06 00:37 UTC (8 min tracked duration; the update reported 14 minutes of inaccessibility). Notion reverted the change that inadvertently triggered the outage.
Wednesday, August 5
17 incident changes
- DegradationMajor incident
Elastic CloudElasticsearch 9.5.0 contains a query-correctness defect
Elastic Cloud reported a major Elasticsearch 9.5.0 defect: boolean queries combining must, filter, or should with must_not on unindexed fields could return false positives and inflated counts. It lasted from 2026-08-05 22:59 UTC to 2026-08-12 08:59 UTC (6 days 10 h); Elasticsearch 9.5.1 fixed it, and customers running 9.5.0 were advised to upgrade.
- DegradationMajor incident
- DegradationMajor incident
HashiCorpand Terraform Cloud (HCP)Infragraph Snapshot are stuck
HashiCorp reported stuck Infragraph snapshots and degraded performance, with major impact, starting at 2026-08-05 20:09 UTC. The incident lasted 1 h 58 min and was resolved at 2026-08-05 22:08 UTC; engineering said systems should be operating normally, but provided no cause or specific fix.
- OutageCritical incident
- OutageMajor incident
CohereDocumentation Content Loading Issues
Cohere reported a major partial outage of its documentation site: some pages failed to load correctly due to an issue with upstream documentation provider Fern. The incident started at 2026-08-05 19:36 UTC and was resolved at 2026-08-05 20:35 UTC, lasting 58 min; Cohere confirmed service was back to normal.
- OutageCritical incident
Descript reported a critical Rooms outage starting at 2026-08-05 19:29 UTC, lasting 28 min and resolved at 2026-08-05 19:57 UTC. Functionality was fully restored at 19:32 UTC, followed by monitoring; no cause was stated.
- OutageCritical incident
Terraform Cloud (HCP)and HashiCorpInfragraph Service and UI down
Terraform Cloud (HCP) reported a critical outage of the Infragraph Service and UI starting 2026-08-05 15:11 UTC. Engineering implemented a fix and confirmed normal operation at 2026-08-05 15:39 UTC; the reported duration was 27 min.
- OutageMajor incident
DremioDremio Cloud US app and login unavailable
Dremio Cloud US experienced a major outage affecting application loading and login; Dremio Cloud Europe operated normally. The incident started at 2026-08-05 14:47 UTC and was resolved at 2026-08-05 18:49 UTC, lasting 4 h 2 min; Dremio reported service recovery and healthy services while monitoring.
- OutageCritical incident
ActiveCampaignIssue Affecting Segmented Campaigns in the EU Region
ActiveCampaign reported a critical outage affecting segmented campaign sending in the EU Data Center, starting 2026-08-05 10:59 UTC and resolved 2026-08-06 11:40 UTC, lasting 24 h 41 min. A fix was implemented at 08-05 13:12 UTC; no cause was stated.
- OutageMajor incident
Apollo GraphQLEmbedded Explorer and Embedded Sandbox temporarily down
Apollo GraphQL’s Embedded Explorer and Embedded Sandbox were down in a major-impact incident from 2026-08-05 09:43 UTC to 2026-08-05 10:08 UTC, lasting 25 min. Apollo identified the issue, deployed a fix, and confirmed resolution; no cause was stated.
- OutageMajor incident
CoralogixLog Query failures across EU1 region
Coralogix reported a major incident causing log query failures in Explore → Logs (v2 and Legacy), including errors accessing archived log data. It started at 2026-08-05 08:46 UTC and was resolved at 2026-08-05 09:01 UTC, lasting 15 min. Although initially reporting EU1 and US1 impact, Coralogix confirmed only EU1 was affected; all services were restored.
- OutageMajor incident
MongoDB AtlasGCP capacity constraints affecting Atlas deployments
MongoDB Atlas reported a major incident affecting some customers’ deployments due to GCP capacity constraints across North America, Europe, and Asia Pacific/Australia, including M50 and S70L instance types. It started at 2026-08-05 05:17 UTC and was resolved at 2026-08-05 12:14 UTC, lasting 6 h 56 min; MongoDB said symptoms had largely subsided and Atlas was fully operational.
- OutageMajor incident
NotionNotion MCP connections are having auth issues
New Claude-to-Notion MCP authorizations failed with “Invalid authorization request,” blocking new connections. Notion rated the incident major and reported failures starting approximately 01:25 UTC on August 5, 2026; the incident was logged at 2026-08-05 03:34 UTC and resolved at 2026-08-05 04:33 UTC (computed duration: 58 min).
- DegradationMajor incident
GreenhousePartial Service Disruption
Greenhouse reported a major partial disruption in Greenhouse Recruiting - Silo 1, affecting user searches, candidate unhire actions, emails, availability requests, referrals, offer letters, scorecards, candidate notes and interview-plan editing. It started 2026-08-05 02:18 UTC and resolved 2026-08-05 13:29 UTC (11 h 10 min); a fix was implemented at 08-05 03:56 UTC.
- OutageMajor incident
ConvexAction failures for business deployments that use createFunctionHandle
Convex reported a major incident causing actions that call createFunctionHandle to fail on business deployments; Free, Starter and Professional users were unaffected. It started at 2026-08-05 01:42 UTC and was resolved at 2026-08-05 01:57 UTC, lasting 14 min. Convex reported implementing and deploying a fix before confirming resolution.
- OutageMajor incident
- OutageMajor incident
Terraform Cloud (HCP)and HashiCorpHCP Terraform UI Not Loading
HCP Terraform had a major UI outage causing blank white screens from 2026-08-05 00:05 UTC to 2026-08-05 01:59 UTC, lasting 1 h 54 min. API calls, CI integrations, and CLI usage were not expected to be affected. Engineering implemented a fix at 00:44 UTC and confirmed resolution at 01:59 UTC.
Tuesday, August 4
18 incident changes
- DegradationMajor incident
- OutageMajor incident
CockroachDBCluster connectivity and execution issues
CockroachDB reported a major outage preventing some Basic and Standard clusters in eu-west1 from connecting or executing queries. It ran from 2026-08-04 23:46 UTC to 2026-08-05 19:50 UTC (20 h 3 min). Immediate impact was mitigated by 2026-08-05 03:55 UTC; resolution followed monitoring confirming stability, with no root cause stated.
- OutageMajor incident
- OutageMajor incident
Anthropicand ClaudeElevated errors across many models
Anthropic reported a major incident affecting claude.ai, Claude API (api.anthropic.com), Claude Code and Claude Cowork: some users had login issues, including OAuth, and model request errors. It started at 2026-08-04 20:48 UTC and was resolved at 2026-08-04 21:59 UTC, lasting 1 h 11 min; no specific cause or fix was stated.
- OutageMajor incident
Box[Medium] Issues with Uploads and Downloads
Box reported major impact to uploads and downloads across its API and web application, with errors and slowness affecting customers. The incident ran from 2026-08-04 20:23 UTC to 2026-08-04 20:44 UTC (21 min). Box attributed upload failures and delays to frontend load-balancer routing and restored service by rerouting upload traffic and provisioning additional capacity.
- OutageCritical incident
Grafana CloudSome Grafana Instances Unavailable
Some Grafana instances in GCP US Central (prod-us-central-0, prod-us-central-3, prod-us-central-4) were unavailable during a critical incident from 2026-08-04 19:11 UTC to 2026-08-05 01:32 UTC (6 h 20 min). Grafana reported cloud-provider compute capacity exhaustion, moved affected workloads to alternative capacity, and rolled out a change to restore service.
- OutageMajor incident
Fly.ioMPG creation is failing in GRU due to lack of capacity
Fly.io reported a major outage in GRU: new MPG clusters could fail to create due to insufficient capacity. It started at 2026-08-04 19:03 UTC and was resolved at 2026-08-05 03:22 UTC, lasting 8 h 19 min; Fly.io tweaked hosts to allow more machine allocation.
- OutageCritical incident
Discord reported a critical API outage affecting direct messages, interactions, shop, and SDK integrations from 2026-08-04 18:49 UTC to 2026-08-04 20:17 UTC, lasting 1 h 27 min. A fix was in place by 19:53 UTC, with nearly all users recovered by 19:59 UTC; the incident was resolved at 20:17 UTC.
- OutageMajor incident
OneSignalApple push notifications failing in about 3% of cases
OneSignal reported a major incident causing about 3% of Apple push notifications to fail, from 2026-08-04 17:20 UTC to 2026-08-04 19:24 UTC (2 h 4 min). The vendor attributed it to a slight change in how Apple's push notification connections work, applied a mitigation, and confirmed normal operation.
- OutageCritical incident
- OutageCritical incident
BrexErrors Affecting Brex API Requests
Brex reported a critical incident affecting API requests, starting 2026-08-04 16:01 UTC and resolved at 2026-08-04 20:34 UTC, lasting 4 h 32 min. Brex stated a fix was in place at 08-04 17:50 UTC; no cause was disclosed.
- OutageMajor incident
WasabiSystem Errors in EU-CENTRAL-2
Wasabi reported a major S3 outage in Frankfurt (eu-central-2) from 07:36 UTC to 08:03 UTC on 4 August 2026, caused by a frontend software update; rollback restored service. The record lists start 2026-08-04 14:20 UTC and resolution 2026-08-04 07:30 UTC, conflicting with the update; computed duration is unknown.
- OutageMajor incident
DockerAutomated builds and Bitbucket
Docker reported a major outage: Git pushes to Bitbucket repositories did not trigger automated builds; GitHub repositories were unaffected. The incident ran from 2026-08-04 14:12 UTC to 2026-08-04 16:09 UTC, lasting 1 h 57 min. A fix was deployed at 15:42 UTC, and Bitbucket build triggers were confirmed restored at resolution.
- DegradationMajor incident
JFrogJFrog Cloud Platform performance degradation for Azure EU West Region
JFrog reported a major incident affecting Artifactory in Azure EU West (Netherlands), with some customers potentially experiencing a brief service interruption. It started and was resolved at 2026-08-04 13:24 UTC, with a computed duration of 0 min; JFrog validated service stability and continued monitoring.
- OutageMajor incident
SnykSnyk Open Source .NET Tests Failing
Snyk reported a major incident affecting all Snyk Open Source .NET project workflows, including import, retest, and pull request checks, across AU, EU, GOV, US-01 and US-02 components. It started at 2026-08-04 13:07 UTC and was resolved at 2026-08-04 14:29 UTC, lasting 1 h 21 min; engineers deployed a fix and confirmed recovery.
- OutageMajor incident
- DegradationMajor incident
SocketElevated latency across multiple surfaces
Socket reported major elevated latency affecting Socket for GitHub, Package Pages, Socket API, Socket Dashboard and Socket Website, starting 2026-08-04 07:42 UTC. A fix was implemented by 2026-08-04 08:33 UTC, and the incident was resolved at 2026-08-04 08:45 UTC after 1 h 3 min.
- OutageCritical incident
LovablePreviews for TanStack applications are currently unavailable
Lovable reported a critical outage affecting TanStack application previews and published apps; previews could show an internal server error. The incident started at 2026-08-04 00:27 UTC and was resolved at 2026-08-04 01:52 UTC, lasting 1 h 25 min; Lovable reported all systems operating normally.
Monday, August 3
2 incident changes
- OutageMajor incident
- OutageMajor incident
MongoDB AtlasElevated errors on VoyageAI APIs
VoyageAI APIs experienced elevated 5xx errors affecting VoyageAI Embedding and Reranking Models, with major impact, from 2026-08-03 18:47 UTC to 2026-08-03 21:18 UTC (2 h 31 min). A fix was applied at 19:02 UTC, and normal operation was confirmed at resolution.