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.
Thursday, May 28
5 incident changes
- OutageMajor incident
GreenhouseAdobe Acrobat Sign experiencing issues sending for signature
Greenhouse reported a major Adobe Acrobat Sign incident: some customers encountered errors sending offers for signature. It started at 2026-05-28 16:23 UTC and was resolved at 2026-05-28 18:29 UTC, lasting 2 h 5 min. Greenhouse stated Adobe was experiencing an issue and investigating; no specific cause or fix was provided.
- OutageMajor incident
Rippling reported a major app and SSO outage from 2026-05-28 16:16 UTC to 2026-05-28 19:52 UTC, lasting 3 h 35 min. Database load caused the issues; Rippling scaled down contributing async jobs before re-enabling them. Supergroup membership latency delayed some access changes; Rippling reported all access and functionality restored and group memberships refreshed.
- OutageCritical incident
- DegradationCritical incident
- OutageMajor incident
SurveyMonkeySurveyMonkey Help Center is Down
SurveyMonkey’s Help Center was down for most users in a major-impact outage starting 2026-05-28 05:03 UTC and resolved at 2026-05-28 05:13 UTC (reported duration: 9 min). SurveyMonkey identified the issue and implemented a fix; the Help Center should now load normally.
Wednesday, May 27
8 incident changes
- DegradationMajor incident
GorgiasAI Agent degraded performance
Gorgias reported a major degradation affecting AI Agent and Ticket Translation, with higher latency caused by a third-party LLM provider outage. It started at 2026-05-27 15:28 UTC and was resolved at 2026-05-28 06:07 UTC, lasting 14 h 38 min. Gorgias switched LLM providers and reported gradual improvement before resolution.
- OutageMajor incident
GreenhouseReadMe - Harvest API Docs outage
Greenhouse’s Harvest API documentation site experienced a major outage starting 2026-05-27 15:08 UTC, leaving customers unable to access the documentation. It lasted 20 h 26 min and was resolved at 2026-05-28 11:34 UTC; Greenhouse said its documentation vendor was working to fix the issue.
- DegradationMajor incident
GorgiasAI Agent - Too many handovers
Gorgias reported a major AI Agent degradation causing some conversations to be handed over due to a confirmed partial degradation of OpenAI's API. It started at 2026-05-27 14:20 UTC and was resolved at 2026-05-27 18:02 UTC, lasting 3 h 41 min.
- OutageMajor incident
Rippling reported a major incident degrading Single Sign-on (SSO) and related identity flows, starting at 2026-05-27 14:01 UTC and resolved at 2026-05-27 14:12 UTC (11 min). A fix was deployed, successful SSO logins were confirmed, and error rates fell.
- OutageMajor incident
NetlifyFailed & delayed builds due to Github incident
Netlify’s Build Pipeline experienced delayed and failed builds due to a GitHub incident, with impact rated major. The incident ran from 2026-05-27 12:13 UTC to 2026-05-27 14:17 UTC, lasting 2 h 4 min; Netlify reported builds had returned to normal.
- OutageCritical incident
- OutageMajor incident
GitLab reported a major Git Operations outage with Git operation errors from 2026-05-27 07:31 UTC to 2026-05-27 09:55 UTC, lasting 2 h 24 min. Mitigation rules reduced errors, and GitLab confirmed resolution with metrics back to normal; no cause was confirmed.
- OutageMajor incident
ConfluenceUsers facing errors when attempting to view Calendars in Confluence
Confluence reported a major View Content incident: users received errors viewing Calendars on Confluence Cloud pages, starting 2026-05-27 06:03 UTC and resolved at 2026-05-27 07:48 UTC (1 h 45 min). Its final update reported user impact between 00:50 UTC and 07:30 UTC on 27 May 2026; engineers identified and resolved the underlying issue.
Tuesday, May 26
6 incident changes
- OutageMajor incident
RunwayIssues affecting Aleph 2.0 generations
Runway reported a major incident affecting Aleph 2.0 generations, now resolved. The recorded start was 2026-05-26 22:10 UTC and resolution was 2026-05-26 19:30 UTC; these timestamps conflict, and the computed duration is unknown. Runway stated that the incident lasted approximately 2 hours.
- OutageMajor incident
Elastic CloudMissing Metrics in Cloud Console - Azure Southeast Asia
Some users experienced missing metrics visualizations in the Elastic Cloud console for deployments in Azure Southeast Asia due to disrupted metric data ingestion. Elastic rated the impact major and reported the situation stabilized; the incident started and was resolved at 2026-05-26 21:35 UTC, with a recorded duration of 0 min.
- DegradationMajor incident
- OutageCritical incident
StatsigStatsig Console temporarily down
Statsig Console (console.statsig.com) was down in a vendor-rated critical incident from 2026-05-26 18:01 UTC to 2026-05-26 18:25 UTC, lasting 24 min. No flag checks or SDK calls were affected; Statsig marked it resolved and said it had determined the root cause, without disclosing the cause or fix.
- DegradationMajor incident
GitLabDelays in CI job processing by runners
GitLab reported a major degradation affecting CI/CD - Hosted runners on Linux, leaving some users’ CI jobs pending while waiting for runners. The incident started at 2026-05-26 16:16 UTC and lasted 1 h 5 min, resolving at 2026-05-26 17:21 UTC after a deployed fix restored normal job pickup.
- OutageCritical incident
GitLabGitLab Duo "Quota exceeded" Errors
GitLab’s critical Duo Agent Platform (DAP) incident blocked access for some customers with “Usage quota exceeded” errors from 2026-05-26 12:50 UTC to 2026-05-26 14:25 UTC (1 h 35 min). GitLab identified a Customers Portal feature flag as the likely cause, disabled it, and confirmed full resolution after cache refreshes.
Monday, May 25
7 incident changes
- OutageMajor incident
- OutageMajor incident
NetlifySupport Communication Delivery Issues
Netlify reported a major outbound email delivery outage affecting some services, including Netlify Helpdesk support communications, from 2026-05-25 15:31 UTC to 2026-05-25 17:32 UTC (2 h 0 min). Delivery was restored at 15:53 UTC, though queued emails could still be delayed; Netlify worked with its email provider during recovery.
- DegradationMajor incident
UnbounceService Disruption Affecting Some Integrations
Unbounce reported a major Third-Party Integrations disruption causing delayed or failed integration events and notifications, starting 2026-05-25 14:33 UTC and resolved 2026-05-27 00:18 UTC (33 h 45 min). Engineers implemented a fix, cleared the backlog, backfilled affected events, and synced integration errors to the UI.
- OutageMajor incident
Pinecone[Serverless][AWS][us-west-2] 5xx errors and longer response times on upsert requests for some indexes.
Pinecone reported a major incident causing 5xx errors and longer response times for upsert requests on some Serverless indexes in AWS us-west-2. It started at 2026-05-25 13:41 UTC and was resolved at 2026-05-25 15:00 UTC, lasting 1 h 18 min. A fix was implemented, but no cause was stated.
- OutageCritical incident
- OutageMajor incident
RetoolElevated 504 Errors Impacting Cloud Users
Retool reported a major incident involving elevated 504 errors for cloud users, affecting Classic web app and Web Application and APIs. It started at 2026-05-25 12:39 UTC and was resolved at 2026-05-25 12:52 UTC, lasting 13 min; Retool reported implementing a fix and monitoring results.
- DegradationCritical incident
Mailgun reported critical delayed sending in the EU affecting API and Outbound Delivery services, starting 2026-05-25 12:18 UTC and resolved at 2026-05-25 15:55 UTC, with a reported duration of 3 h 36 min. A fix was implemented and monitored; no cause was stated.
Saturday, May 23
1 incident change
- DegradationMajor incident
Elastic CloudMissing Metrics in Cloud Console - Azure North Europe
Elastic Cloud reported a major degradation in Azure North Europe: disrupted metric data ingestion left some users missing recent metrics in Cloud console charts and monitoring views. It started at 2026-05-23 21:42 UTC and lasted 44 min, resolving at 2026-05-23 22:26 UTC when the system recovered and functionality returned to normal.
Friday, May 22
12 incident changes
- OutageMajor incident
DrataSome service users and auditors unable to access their own tenant
Some Drata users with service user and auditor accounts could not access their own tenant in a major-impact outage. It started at 2026-05-22 16:56 UTC and was resolved at 2026-05-29 14:27 UTC, lasting 6 days 21 h; Drata reported testing a fix but stated no cause.
- DegradationMajor incident
RenderUpstream provider outage causing delays provisioning custom domains
Render reported a major incident delaying Custom Domains provisioning from 2026-05-22 15:53 UTC to 2026-05-22 16:37 UTC, lasting 44 min. An upstream provider outage caused the delays; the provider deployed a fix, and Render confirmed provisioning had recovered.
- OutageCritical incident
Greenhouse Recruiting had a critical outage on Silos 7, 8, and 9 starting 2026-05-22 15:49 UTC, resolved at 2026-05-22 16:25 UTC (36 min). A planned migration hit a core infrastructure scaling limit, dropping customer traffic and causing a full outage for affected customers; Greenhouse rolled back the migration in all customer environments.
- OutageMajor incident
MakeLogin into make.com doesn't work
Make reported a major login outage affecting make.com and EU/US zones from 2026-05-22 09:57 UTC to 2026-05-22 12:47 UTC, lasting 2 h 50 min; executions were unaffected. Make said it identified the root cause and applied remediations, but did not specify the cause; the incident was resolved.
- OutageMajor incident
Box[Medium] Issues with Box Drive
Box Drive logins experienced errors or timeouts in an incident rated major, starting 2026-05-22 08:46 UTC and resolved at 2026-05-22 09:18 UTC (32 min). Box recommended the Box Web Application as a temporary workaround; its postmortem also noted issues affecting Single Sign-On (SSO) configuration.
- DegradationMajor incident
Sumo LogicProblem with Data Indexing in North America 1 (US1)
Sumo Logic reported a major Data Indexing degradation in North America 1 (US1), causing latency in processing and displaying log data. It started at 2026-05-22 08:33 UTC and was resolved at 2026-05-22 10:26 UTC, lasting 1 h 52 min; normal operation was restored.
- OutageMajor incident
ConvexHTTP Action Outage Affecting Some Deployments
Convex reported a major HTTP action outage affecting some Free & Starter and Professional deployments, starting 2026-05-22 06:11 UTC and resolved 2026-05-22 10:09 UTC (3 h 57 min). Convex reverted a change and advised customers to redeploy; by resolution, all deployments had been automatically repaired and HTTP actions were working across its cloud.
- DegradationMajor incident
Elastic CloudDelayed Execution For Synthetic Monitors in Europe Germany
Some Synthetics browser monitors in Europe-Germany (GCP europe-west3) had delayed execution results or stopped, affecting Elastic Cloud Hosted and Elastic Cloud Serverless; other regions were unaffected. Elastic Cloud marked the impact major, with start and resolution both at 2026-05-22 04:54 UTC (computed duration: 0 min).
- DegradationMajor incident
CanvaSome users might experience intermittent errors in Canva
Some Canva users experienced intermittent errors in an incident rated major, from 2026-05-22 03:34 UTC to 2026-05-22 04:41 UTC, lasting 1 h 7 min. Canva implemented a fix and monitored the results before marking the incident resolved; no cause was stated.
- OutageCritical incident
CodaDocument search is unavailable
Coda’s document search was unavailable in a critical-impact incident affecting Search, starting 2026-05-22 02:11 UTC and resolved at 2026-05-24 04:52 UTC. The outage lasted 2 days 2 h; Coda stated no cause or specific fix.
- OutageMajor incident
DiscordAPI errors affecting message sends, session starts, and billing operations
Discord reported a major API outage affecting message sends, session starts, and billing operations for a subset of users. It started at 2026-05-22 01:55 UTC and was resolved at 2026-05-22 03:39 UTC, lasting 1 h 44 min. Discord said it applied a fix and was seeing recovery across its systems.
- OutageMajor incident
ConfluentConnection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2
Confluent Cloud reported major connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2, starting 20:26 UTC May 21, 2026. Confluent stated full mitigation by 23:56 UTC May 21, 2026, with service operating normally. The resolved incident record’s computed duration was 1 min.
Thursday, May 21
8 incident changes
- OutageMajor incident
SalesforceHeroku Retroactive Feature Disruption: Dashboard
Salesforce reported a major Heroku Dashboard disruption affecting 1 instance, starting at 2026-05-21 22:45 UTC and resolved at 2026-05-22 14:15 UTC after 15 h 30 min. No cause or fix was stated.
- OutageMajor incident
SalesforceService Disruption: Core Service
Salesforce reported a critical Core Service disruption across 81 instances; USA East Region customers could not log in via login.salesforce.com or test.salesforce.com. It started 2026-05-21 20:00 UTC and lasted 5 h 37 min, resolving 2026-05-22 01:37 UTC. Salesforce identified storage and system resource exhaustion causing instability and said it cleared affected systems.
- OutageMajor incident
Bunny.netDNS issues with bunny.net
Bunny.net reported a major DNS outage affecting most services from 2026-05-21 16:39 UTC to 2026-05-21 18:21 UTC, lasting 1 h 41 min. An internal domain-management process failure led to bunny.net being temporarily suspended; Bunny.net worked with its registrar to restore the domain, with affected services recovering as DNS changes propagated globally.
- OutageCritical incident
PandaDocIntegrations are not responding; PDF won't download
PandaDoc reported a critical outage affecting integrations and PDF downloads, with document creation, editing and uploads also listed as affected in US & Global components. The incident started at 2026-05-21 15:07 UTC and was resolved at 2026-05-21 16:04 UTC, lasting 57 min; PandaDoc confirmed normal operation but stated no cause or specific fix.
- DegradationMajor incident
GorgiasSome merchands are reporting orders missing from the widgets / search
Some merchants reported orders missing from Gorgias widgets/search, affecting the Shopify integration. The vendor rated the incident major; it lasted 1 h 39 min, from 2026-05-21 14:24 UTC to 2026-05-21 16:03 UTC. Gorgias reported redeploying a previous Helpdesk version as a fix and stated no data was lost.
- OutageMajor incident
GitLabElevated error ratio for web service
GitLab reported a major incident involving elevated webservice error rates starting 2026-05-21 09:42 UTC, lasting 47 min and marked resolved at 2026-05-21 10:29 UTC. GitLab identified impact as limited to gitlab-org, with no impact observed outside it, and moved the ongoing investigation to a confidential internal incident; no cause or fix was stated.
- DegradationMajor incident
GorgiasTicket Search is delaying on one of the helpdesk cluster
Ticket Search was delayed on Helpdesk Clusters - europe-west4-e7f4 in a major-impact incident from 2026-05-21 07:21 UTC to 2026-05-21 08:41 UTC, lasting 1 h 19 min. Gorgias implemented a fix at 2026-05-21 08:12 UTC and subsequently marked the incident resolved.
- OutageCritical incident
JFrogJFrog Cloud Platform outage affecting subset of customers in AWS US East region
JFrog reported a critical Cloud Platform outage affecting a subset of customers in AWS US East, citing an infrastructure issue. It started at 2026-05-21 06:04 UTC and was resolved at 2026-05-21 06:35 UTC, lasting 31 min; JFrog confirmed all regional services were fully operational and engineers continued monitoring.
Wednesday, May 20
3 incident changes
- OutageMajor incident
- OutageMajor incident
DialpadSome customers may be experiencing issues with IVR
Dialpad reported a major Omnichannel incident affecting IVR for some customers, starting 2026-05-20 18:58 UTC and resolved 2026-05-21 00:26 UTC, lasting 5 h 28 min. A fix was implemented and monitored; no cause was stated.
- OutageMajor incident
Drata reported a major tenant access outage affecting a subset of customers working with managed security service providers (MSSPs), starting 2026-05-20 17:56 UTC. A fix was implemented, and the incident was resolved at 2026-05-22 19:07 UTC after 2 days 1 h.