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, September 2
1 incident change
- OutageMajor incident
Elastic CloudElevated Error Rates for Specific Models Impacting Elastic Inference Service in EU Regions
Elastic Cloud reported a major incident with elevated error rates for Anthropic Claude Haiku 4.5, OpenAI GPT-5.6, and Google Gemini 2.5 Flash on Elastic Inference Service in EU regions, citing 21:50–23:42 UTC. It was resolved; recorded start and resolution were both 2026-09-02 00:04 UTC (computed duration: 0 min).
Tuesday, September 1
29 incident changes
- OutageMajor incident
Verceland v0Increased deployment failures
Vercel reported a major incident causing some deployments using IAD1 Function regions or Routing Middleware to fail. It started at 2026-09-01 19:59 UTC and lasted 59 min, resolving at 2026-09-01 20:58 UTC after a fix was deployed and Builds recovered.
- OutageMajor incident
BrexTrust Portal (trust-portal.brex.com) is downEvent
Brex’s Trust Portal (trust-portal.brex.com) was unavailable in a major-impact incident starting 2026-09-01 17:48 UTC. Brex reported the site restored at 09-01 19:20 UTC and marked the incident resolved at 2026-09-02 01:56 UTC; the recorded incident duration was 8 h 7 min.
- OutageCritical incident
Jupyter (Anaconda)Dot-org network interruptionEvent
Anaconda reported a critical network interruption affecting the anaconda.org front-end and conda.anaconda.org repository services, with elevated 503 errors on anaconda.org. It started at 2026-09-01 17:46 UTC and was resolved at 2026-09-01 19:05 UTC, lasting 1 h 18 min. A fix was rolled out at 18:53 UTC; no cause was stated.
- DegradationMajor incident
GorgiasVoice/SMS functionality degraded due to a Twilio incidentEvent
Gorgias reported a major Voice degradation starting 2026-09-01 17:05 UTC due to a Twilio incident, causing failed or delayed calls and inaccurate call test results for some customers. SMS, email, chat and helpdesk were unaffected. Resolved at 2026-09-01 18:00 UTC after 54 min, Voice functionality and call test results returned to normal.
- OutageMajor incident
MatillionCustomers receiving Authentication failed messages upon login attemptsEvent
Matillion reported a major Hub login outage starting 2026-09-01 17:03 UTC, resolved at 2026-09-01 17:55 UTC after 52 min; the support portal was also affected. New tokens could not be issued after hitting the global token limit; Matillion attributed widespread permission-check failures to an out-of-memory event triggered by a Permission Service deployment.
- MajorMajor incident
- MajorMajor incident
- MajorMajor incident
- OutageMajor incident
Apollo GraphQLService Disruptions Due to Google Cloud Platform IssuesEvent
Apollo reported a major outage from 2026-09-01 15:41 UTC to 2026-09-01 20:18 UTC (4 h 37 min), attributed to GCP issues in part of us-central1-b. New schemas could not be published; AWS Uplink remained available, allowing default multi-cloud GraphOS Routers and Gateways to start and fetch configuration. All Apollo products recovered.
- OutageMajor incident
SourcegraphSign-in and authentication errorsEvent
Sourcegraph reported a major incident affecting account sign-in and authentication, starting 2026-09-01 15:41 UTC and resolved 2026-09-02 09:39 UTC, lasting 17 h 58 min. Sourcegraph attributed the errors to a Google Cloud networking incident; sign-in had recovered by 2026-09-01 16:48 UTC, with monitoring continuing afterward.
- DegradationMajor incident
CockroachDBCloud Latency, Delays, Connection IssuesEvent
CockroachDB Basic/Standard experienced major latency, delays, and connection issues affecting us-central-1, asia-east-1 (later listed as us-central1, asia-east1), europe-west4-b, and us-central1-b from 2026-09-01 15:36 UTC to 2026-09-01 19:45 UTC (4 h 8 min). CockroachDB attributed the disruption to Google Cloud networking outages; network-level mitigation restored infrastructure, and all services were confirmed restored.
- OutageCritical incident
Sigma ComputingWidespread failures are preventing Sigma from loading for GCP-hosted organizations.Event
A critical outage prevented GCP-hosted organizations in us-central1 from reliably accessing Sigma. The recorded incident ran from 2026-09-01 15:34 UTC to 2026-09-01 16:55 UTC (1 h 20 min), though Sigma reported an approximate start of 2:46 PM UTC. The postmortem attributed the disruption to a Google Cloud networking incident; services returned to normal.
- MajorMajor incident
- DegradationMajor incident
DialpadPartial service disruptionEvent
Dialpad reported a major partial service disruption affecting Telephony Infrastructure: Inbound Calls, starting 2026-09-01 15:25 UTC and resolved at 2026-09-01 20:02 UTC, lasting 4 h 36 min. Dialpad stated that a fix was implemented but did not specify the cause or fix details.
- OutageMajor incident
GorgiasCloud service provider network incident may affect a subset of Gorgias CustomersEvent
Gorgias reported a major cloud service provider network incident potentially affecting a subset of customers, with Live Chat, REST API and Google Cloud Networking listed as affected components. It started at 2026-09-01 15:19 UTC and was resolved at 2026-09-01 18:59 UTC, lasting 3 h 39 min.
- OutageCritical incident
FullStoryMultiple Fullstory Services Unavailable (NA1 Data Center)Event
Fullstory reported a critical NA1 outage affecting data capture (web and native mobile), the Fullstory web application, API and other services. It ran from 2026-09-01 15:19 UTC to 2026-09-01 20:36 UTC (5 h 17 min). Fullstory linked the issue to Google Cloud Platform; services were restored, with backlogged data still processing.
- OutageMajor incident
Elastic CloudIssue impacting services running in GCP us-central1Event
A major outage impacted Elastic Cloud Hosted and Serverless projects in GCP us-central1 and the Docker Registry service. It started at 2026-09-01 15:18 UTC and was resolved at 2026-09-01 20:05 UTC, lasting 4 h 47 min; Elastic attributed the disruption to an upstream CSP issue.
- OutageCritical incident
DrataMultiple products unavailableEvent
Drata reported a critical outage affecting Trust Center Pages, Trust Center Admin Page, AIQA, and Compliance Monitoring (AI Summary), caused by upstream provider network service degradation. It started at 2026-09-01 15:14 UTC and was resolved at 2026-09-01 19:29 UTC, lasting 4 h 14 min; all impacted services were operational at resolution.
- OutageMajor incident
Pinecone5xx errors on some control plane operationsEvent
Pinecone reported a major incident causing 5xx errors on some control plane operations, affecting Console, Index management, Assistant management, and APIs at api.pinecone.io. It started at 2026-09-01 15:04 UTC and was resolved at 2026-09-01 19:40 UTC, lasting 4 h 36 min. Pinecone said it was likely related to ongoing GCP issues.
- DegradationMajor incident
RevenueCatApple partial outage: intermittent errors while processing purchases
RevenueCat reported a major Apple Receipt Server degradation from 2026-09-01 13:17 UTC to 2026-09-01 13:43 UTC (26 min), with intermittent HTTP 522 responses from its receipts endpoint. Mitigations meant no purchases were being blocked; Apple reported resolution, error rates normalized, and RevenueCat said it was ensuring affected purchases were reprocessed.
- OutageMajor incident
TailscaleFunnel connectivity issues
Tailscale reported a major Funnel incident involving connection errors for some users, starting 2026-09-01 12:47 UTC and resolved at 2026-09-01 16:19 UTC, lasting 3 h 31 min. A fix was deployed at 09-01 14:11 UTC; no cause was stated.
- OutageMajor incident
DynatraceIssue with Dynatrace Platform
Dynatrace reported a major authentication issue affecting service access and potentially causing data processing and extraction errors or delays; ingestion continued. The incident started at 2026-09-01 11:54 UTC and was resolved at 2026-09-03 14:10 UTC, lasting 2 days 2 h, with normal operation verified after extended monitoring.
- OutageMajor incident
Snowflake reported a major incident in which customers in the listed AWS, Azure and GCP regions could be unable to sign in to Snowflake Cowork. It started at 2026-09-01 09:58 UTC and was resolved at 2026-09-01 13:50 UTC. All other Snowflake features were unaffected; Snowflake identified the source but did not specify the cause or fix.
- OutageCritical incident
SupabaseUser unable to log in to Supabase Dashboard
A critical Supabase Dashboard outage prevented login, logged existing users out, and made Dashboard actions unavailable from 2026-09-01 08:45 UTC to 2026-09-01 10:34 UTC (1 h 49 min). Supabase reverted a recent change that affected login; the incident was resolved, and projects and non-Dashboard traffic remained unaffected.
- DegradationMajor incident
Elastic CloudReplication bug causing slow recoveries
Elastic Cloud Hosted reported major degradation from 2026-09-01 08:16 UTC to 2026-09-30 20:44 UTC (29 days 12 h). In Elasticsearch 9.5.0, 9.5.1 and 9.5.2, bulk indexing could cause replica divergence, high disk usage and long-running recoveries. Elastic fixed the bug in 9.5.3 and advised affected customers to upgrade and follow workaround steps.
- OutageMajor incident
SentrySentry requests timing out / 504's
Sentry reported a major outage affecting API, Dashboard, and Integration Pipeline, with requests timing out or returning 504s. It started at 2026-09-01 08:01 UTC and was resolved at 2026-09-01 11:21 UTC, lasting 3 h 20 min. Sentry identified the issue and rolled out a configuration change.
- MajorMajor incident
- MajorMajor incident
- OutageMajor incident
SalesforceMarketing Cloud Disruption: Marketing Cloud Core Service
Salesforce reported a major Marketing Cloud Core Service disruption affecting 1 instance. It started at 2026-09-01 00:27 UTC and was resolved at 2026-09-01 00:38 UTC, lasting 11 min.
Monday, August 31
16 incident changes
- OutageMajor incident
DiscordSome servers and other services (voice calls, activities) not available for some users
Discord reported a major outage that left some users unable to connect to some servers and affected voice calls and activities. It started at 2026-08-31 22:54 UTC and was resolved at 2026-09-01 00:49 UTC, lasting 1 h 55 min; Discord reported remediation steps but gave no specific cause or fix.
- OutageMajor incident
RipplingIssues loading saved payroll reports
Rippling reported a major outage preventing some saved payroll reports from loading when certain payroll fields were included. It started at 2026-08-31 22:37 UTC and lasted 5 h 43 min, resolving at 2026-09-01 04:20 UTC; United States access was restored before European Union access.
- OutageMajor incident
JiraFetching mails from Microsoft accounts producing errors and preventing email based creation of Jira work items
Jira reported a major outage fetching mail from Microsoft accounts, disrupting email-based creation and updates of work items and potentially returning 500 errors. It started at 2026-08-31 18:28 UTC and was resolved at 2026-09-01 05:18 UTC, lasting 10 h 49 min; Atlassian reported full recovery across impacted services.
- DegradationMajor incident
AshbyAll-in-One: Elevated Dropbox Sign Errors
Ashby reported a major degradation affecting All-in-One document uploads and signing through Dropbox Sign, starting 2026-08-31 17:44 UTC and resolved at 2026-08-31 18:11 UTC (27 min). Ashby attributed the disruption to an upstream Dropbox Sign incident and said the provider resolved the issue.
- MajorMajor incident
- OutageCritical incident
Snowflake reported a critical outage in AWS - US East (N. Virginia) affecting sign-in, queries and data operations from 2026-08-31 17:20 UTC to 2026-08-31 19:44 UTC (2 h 24 min). It reverted a problematic change and fixed residual Snowsight access and Snowpipe Streaming impact; an RCA is available on Snowflake Community.
- MajorMajor incident
- DegradationMajor incident
RenderService instability in Singapore
Render reported a major degradation in Singapore affecting deploys and inbound traffic, with unexpected web service restarts or intermittent availability; Free service spin-ups from idle were temporarily disabled. The incident started at 2026-08-31 15:47 UTC and was resolved at 2026-08-31 18:09 UTC, lasting 2 h 21 min. Render implemented a fix but did not specify its details.
- CriticalCritical incident
- CriticalCritical incident
- OutageMajor incident
AsanaAsana full outage for some users (2 hours, 25% outage)
Asana reported a major full outage for some users (25% outage), affecting API, App and Mobile, including US components, from 2026-08-31 15:14 UTC to 2026-08-31 17:18 UTC (2 h 4 min). The postmortem attributed it to infrastructure changes and peak traffic exceeding cache scaling limits; user-facing symptoms recovered after configuration changes and a fix.
- OutageMajor incident
ChatGPTand OpenAIChatGPT Work seeing elevated errors and latencyHN
ChatGPT Work had a major incident with elevated errors and latency, preventing users across multiple subscription plans from starting or continuing tasks; Plus users were particularly impacted, with Work mode unavailable. It started at 2026-08-31 15:04 UTC and resolved at 2026-08-31 20:28 UTC, lasting 5 h 23 min. A mitigation was applied, and services fully recovered.
- CriticalCritical incident
- OutageMajor incident
MiroIntermittent Issues with User Registration and Login
Miro reported a major incident causing intermittent registration and login errors for a small percentage of users, starting 2026-08-31 14:31 UTC and resolved at 2026-08-31 15:57 UTC, lasting 1 h 25 min. Miro implemented a fix and confirmed full recovery; users encountering registration errors were advised to refresh and retry.
- CriticalCritical incident
- OutageMajor incident
BasetenElevated inference 500s for models in a single US-based cluster
Baseten reported a major Dedicated Inference incident with elevated inference 500s for models in a single US-based cluster. It ran from 2026-08-31 06:38 UTC to 2026-08-31 07:02 UTC (24 min); a fix was in place and traffic was back at 06:57 UTC.
Sunday, August 30
2 incident changes
- OutageMajor incident
XeroAustralia: Xero Tax - customers are experiencing issues with prefilling and lodging tax returns to the ATO
Xero reported a major Australian Xero Tax outage preventing some customers from prefilling or lodging tax returns to the ATO, starting 2026-08-30 23:50 UTC and resolved 2026-08-31 01:37 UTC (computed duration: 1 h 46 min). Xero attributed the issue to an underlying product dependency and implemented a fix to restore service.
- OutageMajor incident
XeroAustralia: Xero Tax - customers are experiencing issues with prefilling and lodging tax returns to the ATO
Xero reported a major incident preventing Australian Xero Tax customers from prefilling or lodging tax returns to the ATO. It ran from 2026-08-30 20:21 UTC to 2026-08-30 22:39 UTC, lasting 2 h 18 min. The ATO implemented a fix, and Xero confirmed resolution.