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, May 20
8 incident changes
- 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.
- OutageMajor incident
SquarespaceConnectivity Issues
Squarespace reported a major connectivity incident affecting Site Editing and Site Loading, with connectivity issues and 503 errors on sites. It started at 2026-05-20 17:45 UTC and was resolved at 2026-05-20 18:15 UTC, lasting 29 min. A fix was implemented by 2026-05-20 18:07 UTC; no cause was stated.
- OutageMajor incident
SemgrepLogins are failing for users via GitHub auth
Semgrep reported a major outage affecting GitHub-auth logins starting 2026-05-20 17:34 UTC; SSO logins were unaffected. A fix was rolled out at 17:49 UTC, restoring logins, and the incident was resolved at 2026-05-20 18:18 UTC after 44 min.
- DegradationMajor incident
BuildkiteDelayed notifications
Buildkite reported a major incident affecting a subset of customers, with delayed email, GitHub commit status, Slack and webhook notifications; the postmortem also noted build dispatch and metrics latency. It started at 2026-05-20 16:40 UTC and resolved at 2026-05-20 17:39 UTC, lasting 59 min. Buildkite applied mitigations and monitored recovery.
- DegradationMajor incident
ChargebeeIntermittent API Failures - EU Region
Chargebee reported major-impact intermittent API request timeouts in the EU region between 15:02 UTC and 15:16 UTC. The incident record started and resolved at 2026-05-20 16:09 UTC (computed duration: 0 min); Chargebee said the issue was resolved and services were operating normally.
- OutageCritical incident
OptimizelyFlags permission issue.
Optimizely reported a critical flags permission issue affecting Application UI and Optimizely REST API, including Feature Experimentation. It started at 2026-05-20 09:42 UTC and was resolved at 2026-05-20 11:30 UTC, lasting 1 h 48 min; a fix was implemented at 10:10 UTC, but no cause or specific customer impact was stated.
- OutageMajor incident
HootsuiteLinkedIn Authentication Issues
A major LinkedIn authentication outage affected Hootsuite Web Application and Hootsuite Mobile Application, causing some connections and reconnections for LinkedIn Profiles and LinkedIn Company Pages to fail. Hootsuite attributed this to LinkedIn internal API instability affecting the authorization profile-information endpoint. It started at 2026-05-20 09:34 UTC and was resolved at 2026-05-20 16:22 UTC; reported duration: 6 h 47 min.
- DegradationMajor incident
Tuesday, May 19
9 incident changes
- DegradationMajor incident
WorkOS reported major delays delivering a subset of webhooks starting at 2026-05-19 21:43 UTC, delaying affected webhook delivery for 16 min. The incident was resolved at 2026-05-19 22:00 UTC after the webhook queue backlog was delivered.
- DegradationCritical incident
NetlifyElevated response times affecting origin services
Netlify reported a critical incident affecting Build Pipeline, Netlify Application UI, and Netlify Functions, with latency, errors, intermittent site unavailability, and builds failing to start or delayed. It started at 2026-05-19 21:08 UTC and was resolved at 2026-05-19 23:04 UTC, lasting 1 h 55 min. Netlify implemented mitigation and confirmed normal operation.
- DegradationMajor incident
SemgrepScheduling delays for Semgrep Managed Scanning (SMS)
Semgrep reported major scheduling delays in Semgrep Managed Scanning (SMS), with some scans failing to execute. Recorded start: 2026-05-19 18:54 UTC, with reported onset approximately 18:30 UTC; resolved: 2026-05-19 21:33 UTC; duration: 2 h 38 min. After a system change was deployed, scheduling queues and scan success rates began recovering.
- OutageMajor incident
SquarespaceAcuity Scheduling Service Disruption
Squarespace reported a major Acuity Scheduling disruption that prevented existing users from creating new Acuity trials; it warned all users and services may be affected. The incident started at 2026-05-19 17:06 UTC and was resolved at 2026-05-19 17:35 UTC, lasting 29 min. Engineering identified the root cause and reported implementing a fix, without specifying details.
- OutageCritical incident
PendoGuide Delivery Outage - US1 Region
Pendo reported a critical guide delivery outage in the US1 environment (us1.app.pendo.io): guides were not loading for end users. The incident ran from 2026-05-19 16:50 UTC to 2026-05-19 19:06 UTC, lasting 2 h 16 min. Mitigation changes partially restored service; guides were loading normally by 17:33 UTC, with full resolution confirmed at 19:06 UTC.
- OutageMajor incident
AircallWorkspace App - Error loading conversations
Aircall reported a major outage affecting conversation loading in Aircall Workspace on Desktop and Web, starting 2026-05-19 15:48 UTC and resolved at 2026-05-19 17:15 UTC, lasting 1 h 26 min. A fix restored conversation loading by 16:35 UTC; no cause was stated.
- DegradationMajor incident
LaunchDarklyEvent Ingestion Delays
LaunchDarkly reported major event-ingestion delays affecting Experimentation results and Guarded Rollouts, starting 2026-05-19 14:49 UTC and resolving 2026-05-19 14:54 UTC (5 min). No data was lost; the vendor said it identified the root cause and was releasing a fix, then confirmed normal ingestion and full restoration.
- OutageMajor incident
SalesforceMarketing Cloud Disruption: Marketing Cloud Core Service
Salesforce reported a major outage affecting Marketing Cloud Core Service on 1 instance, starting 2026-05-19 11:09 UTC and resolved at 2026-05-19 11:17 UTC, lasting 8 min. No cause or fix was stated.
- DegradationCritical incident
BrexIntermittent Dashboard Errors
Brex reported a critical Dashboard incident in which some requests were blocked with a misleading error message. It started and was resolved at 2026-05-19 00:15 UTC, with a computed duration of 0 min; no cause or specific fix was stated.
Monday, May 18
5 incident changes
- OutageCritical incident
- OutageMajor incident
SalesforceService Disruption: Core Service
Salesforce reported a critical Core Service disruption affecting 1 instance, starting at 2026-05-18 17:53 UTC and resolved at 2026-05-18 18:02 UTC after 9 min. No cause or fix was stated.
- DegradationMajor incident
ChargebeeAPI Service Degradation
Chargebee reported major API degradation across AU, EU and US, with intermittent 5xx errors caused by an internal change; reverting it restored stability. The stated impact window was 10:06 UTC to 10:17 UTC on 2026-05-18, while recorded start and resolution were both 2026-05-18 11:05 UTC (computed duration: 0 min).
- DegradationMajor incident
GitLabJobs not being picked up/stuck pending
GitLab reported a major CI/CD degradation: some jobs remained pending because of runner pool exhaustion, affecting hosted runners for community contributions, Linux, macOS and Windows. It started at 2026-05-18 11:03 UTC and was resolved at 2026-05-18 12:41 UTC, lasting 1 h 38 min; additional runners restored normal queueing.
- OutageMajor incident
OptimizelyCMP: Some Home Page Sections & Requests Module Displaying No Data
Optimizely reported a major CMP outage: Requests and the Home Page’s My Work, My Team’s Work, and Watching sections appeared empty for a subset of customers. It started at 2026-05-18 09:20 UTC and resolved at 2026-05-18 10:54 UTC, lasting 1 h 33 min. A fix was implemented at 09:41 UTC; no cause was stated.
Saturday, May 16
3 incident changes
- DegradationMajor incident
- OutageMajor incident
1PasswordSaaS Manager performance is degraded
1Password’s SaaS Manager had a major incident in the US and EU regions affecting file uploads/downloads, image and page loading, and some integrations and workflows. It started at 2026-05-16 15:51 UTC and was resolved at 2026-05-16 20:36 UTC, lasting 4 h 44 min; image-loading issues persisted after other functions recovered.
- OutageCritical incident
DatadogAzure Metrics Reporting
Datadog reported a critical Azure metrics submission issue affecting Metrics and Infra Monitoring from 2026-05-16 02:17 UTC to 2026-05-16 03:43 UTC, lasting 1 h 25 min. A fix was implemented, and Azure metrics were reporting as expected when the incident was resolved.
Friday, May 15
6 incident changes
- OutageCritical incident
GrammarlySome Grammarly and Superhuman users may be unable to log in
Some Grammarly and Superhuman users could not log in or reset passwords during a vendor-rated critical incident starting 2026-05-15 16:33 UTC. A fix was implemented at 16:43 UTC, and the incident was resolved at 16:45 UTC after 12 min.
- DegradationMajor incident
GitLabDegraded performance affecting Duo features
GitLab reported major degradation in Duo Agent Platform workflows on GitLab.com and GitLab Dedicated: some code review and custom flows failed or showed “Session failed.” The incident ran from 2026-05-15 15:37 UTC to 2026-05-15 18:11 UTC (2 h 34 min), resolving after a revert restored normal error rates and running flows.
- OutageMajor incident
SalesforceCc Storefront SAnd Or Business Manager Unavailable: B2 CCore
Salesforce reported a major B2 CCore outage affecting some Commerce Cloud Storefronts: customers could not access Storefronts, and pages and prices failed to load. It ran from 2026-05-15 12:26 UTC to 2026-05-15 15:01 UTC (2 h 35 min). Salesforce identified a potential routing and utility infrastructure trigger and restored services through failover and manual data synchronization.
- OutageCritical incident
- OutageMajor incident
DigitalOceanAnthropic reported outage that's impacting access to their Serverless Inference models
DigitalOcean reported a major Serverless Inference outage affecting all users of Sonnet 4.6 and Opus 4.7, with Agent Runtime and Gradient AI listed as affected components. It started at 2026-05-15 01:21 UTC and was resolved at 2026-05-15 02:00 UTC, lasting 38 min. DigitalOcean attributed the disruption to an Anthropic outage and confirmed service restoration after Anthropic resolved it.
- OutageMajor incident
New RelicUI and Data Irregularities - US Region
New Relic’s major US-region outage disrupted UI loading and delayed data in queries, charts, and dashboards; data ingest and alerts were unaffected. Recorded start: 2026-05-15 00:06 UTC; resolved: 2026-05-15 01:45 UTC (computed duration: 1 h 38 min). The vendor reported impact between 22:30 UTC on May 14th and 01:00 UTC on May 15th, 2026.
Thursday, May 14
9 incident changes
- DegradationMajor incident
Box[Medium] Degradation of Enterprise Events API
Box reported a major-impact degradation affecting customers using the streaming Enterprise Events API. The recorded start was 2026-05-14 19:30 UTC, with a computed duration of 0 min; Box said its systems detected and corrected the underlying issue and there was no current impact.
- DegradationMajor incident
UpstashUpstash Redis – intermittent connection issues in some regions
Upstash Redis had a major incident causing intermittent connection timeouts or elevated error rates in us-east-1, us-west-1, ap-southeast-2, and ap-south-1 from 2026-05-14 15:47 UTC to 2026-05-14 17:31 UTC, lasting 1 h 44 min. Upstash attributed it to unexpected proxy load and applied workarounds to relieve pressure; the incident was resolved.
- OutageMajor incident
- DegradationCritical incident
RootlySlack-dependent features degraded due to ongoing upstream Slack incident
Rootly’s Slack-dependent features were degraded by an upstream Slack incident, rated critical, starting 2026-05-14 14:01 UTC and lasting 1 h 58 min. On-Call, Mobile, and Web Platform remained fully operational; Rootly marked the incident resolved at 2026-05-14 16:00 UTC after the issue was resolved on Slack’s side.
- OutageCritical incident
DrataUS Public API unavailable
Drata’s US Public API was unavailable in a critical incident starting 2026-05-14 10:54 UTC, resolved at 2026-05-14 13:36 UTC after 2 h 42 min. Drata reported deploying updates that restored availability at 12:35 UTC and confirmed stability after monitoring; it identified but did not disclose the root cause.
- OutageCritical incident
JiraUsers experiencing issues accessing multiple Atlassian products
Jira reported a critical outage affecting access to multiple Atlassian Cloud products, including Jira Cloud and Confluence, starting 2026-05-14 06:41 UTC and lasting 6 min. Atlassian reported full recovery at 2026-05-14 06:48 UTC; its postmortem cited a deployment-orchestration race condition during a core identity service rollback in us-east.
- OutageCritical incident
TrelloUsers experiencing issues accessing multiple Atlassian products
Trello.com, API and Atlassian support services experienced a critical login/access outage starting 2026-05-14 05:24 UTC, resolved at 2026-05-14 06:48 UTC (1 h 23 min). Atlassian attributed the disruption to a race condition in its internal deployment orchestration platform during a routine rollback of a core identity service in us-east; all impacted services recovered.
- OutageCritical incident
BitbucketUsers experiencing issues accessing multiple Atlassian products
Bitbucket reported a critical outage affecting access, authentication, APIs, Git and Pipelines from 2026-05-14 05:03 UTC to 2026-05-14 06:48 UTC (1 h 44 min). Atlassian attributed the disruption to a race condition during a core identity service rollback in us-east; all affected products and services were reported recovered.
- OutageCritical incident
ConfluenceUsers experiencing issues accessing multiple Atlassian products
A critical outage disrupted access for many Confluence and Jira Cloud customers, starting 2026-05-14 04:54 UTC and resolving 2026-05-14 06:48 UTC; the recorded duration was 1 h 53 min. Atlassian attributed the disruption to a race condition in its internal deployment orchestration platform during a core identity service rollback in the us-east region.
Wednesday, May 13
7 incident changes
- OutageCritical incident
- OutageMajor incident
Pinecone[AWS][us-east-1] 5xx errors on read and write operations for some indexes
Some Pinecone indexes in AWS us-east-1 experienced 5xx errors on read and write operations, affecting Serverless Indexes. Pinecone rated the incident major; it started at 2026-05-13 20:14 UTC and was resolved at 2026-05-13 21:15 UTC, lasting 1 h 1 min. Pinecone reported identifying the issue and implementing a fix but gave no cause or fix details.
- OutageMajor incident
SalesforceTableau Service Disruption: Analytics Cloud
Salesforce reported a major Tableau service disruption affecting Analytics Cloud on 1 instance. It started at 2026-05-13 17:10 UTC and was resolved at 2026-05-13 18:05 UTC, lasting 55 min.
- DegradationMajor incident
MakeScenarios execution degraded - eu2.make.com
Make reported a major degradation on eu2.make.com that could affect scenario executions and credits, starting 2026-05-13 10:49 UTC and resolved at 2026-05-13 18:08 UTC, lasting 7 h 18 min. The vendor identified the cause of zone overload and applied mitigations, reporting the zone operational again at 14:10 UTC.
- OutageMajor incident
RunwayWe've identified a problem and are working on a fix
Runway reported a major outage affecting Kling tasks across App, Backend, and Public API, starting 2026-05-13 09:11 UTC and resolved at 2026-05-13 13:32 UTC, lasting 4 h 20 min. A fix released at 05-13 12:29 UTC improved service, and previously failed submissions could be retried.
- OutageMajor incident
SalesforceService Disruption: Core Service
Salesforce reported a critical Core Service disruption affecting 1 instance from 2026-05-13 01:52 UTC to 2026-05-13 02:43 UTC (51 min). Users may have experienced errors, high average page times (APIs), or inability to access services; Salesforce addressed an impacted node and reported users out of impact at 02:41 UTC.
- DegradationMajor incident
JiraAutomations within Jira, Jira Service Management and JSM Assist experiencing delays for some users
Jira reported major automation delays for some Jira, Jira Service Management and JSM Assist users, starting 2026-05-13 01:37 UTC and lasting 8 h 21 min. Services were fully operational and all delayed automation events processed at 2026-05-13 09:59 UTC; the postmortem cited a latent bug in the event processing pipeline.
Tuesday, May 12
3 incident changes
- OutageCritical incident
IterableIterable Web Application Outage - US and EU Regions
Iterable reported a critical US and EU web application outage from 2026-05-12 23:31 UTC to 2026-05-13 00:08 UTC, lasting 37 min. Customers could not log in and experienced slow page loads; email sends, API traffic, webhooks, and journeys remained unaffected. Engineering deployed a fix in both regions and confirmed normal service.
- OutageMajor incident
RenderLogs unavailable for some services in all regions
Render reported major log unavailability for some services in all regions between approximately 19:45 UTC and 20:30 UTC; affected logs were unavailable in the Dashboard and not streamed to third-party logging providers. Recorded start: 2026-05-12 22:29 UTC; marked resolved: 2026-05-12 20:00 UTC. Duration is unknown.
- OutageMajor incident
GitLabElevated 5xx Errors on GitLab.com
GitLab.com experienced elevated 5xx errors affecting CI/CD, Git Operations and Website, with major impact, from 2026-05-12 21:04 UTC to 2026-05-12 21:33 UTC (29 min). GitLab identified a frozen Gitaly node; the incident was resolved and error rates returned to normal.