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, May 7
1 incident change
- OutageMajor incident
CanvaUsers in some countries may experience issues trying to access Canva
Canva reported a major outage affecting users in some countries, with issues viewing media in the Canva Editor and accessing Canva. It started at 2026-05-07 00:03 UTC and was resolved at 2026-05-07 00:59 UTC, lasting 55 min. A fix was implemented, followed by monitoring.
Wednesday, May 6
7 incident changes
- OutageMajor incident
Pinecone[AWS][us-east-1] 5xx errors for some requests on some indexes
Pinecone reported a major incident affecting AWS us-east-1 Serverless Indexes, with 5xx errors for some requests on some indexes. It started at 2026-05-06 20:02 UTC and was resolved at 2026-05-06 20:30 UTC, lasting 27 min. A fix was implemented by 05-06 20:14 UTC; no cause was stated.
- OutageMajor incident
- OutageMajor incident
PandaDocGlobal application issues: document access, sending, upload and download
PandaDoc reported a major outage affecting document access, sending, upload and download, with API, integrations and other US & Global services also listed as affected. It started at 2026-05-06 19:27 UTC and was resolved at 2026-05-06 20:03 UTC, lasting 36 min; PandaDoc confirmed normal operation but stated no cause or fix.
- DegradationMajor incident
GitLabIntermittent errors observed on GitLab Next
GitLab Next (Canary) experienced intermittent errors with major impact from 2026-05-06 19:01 UTC to 2026-05-06 20:46 UTC, lasting 1 h 45 min. GitLab said a configuration update may cause the errors and recommended GitLab - Current as a workaround; it applied a fix and confirmed resolution.
- DegradationMajor incident
- OutageMajor incident
XeroGlobal: Xero- some customers may be experiencing issues in Xero
Xero reported a major global outage affecting Xero Platform and Settings: some customers encountered errors accessing or navigating Xero. The incident started at 2026-05-06 03:54 UTC and was resolved at 2026-05-06 04:25 UTC, lasting 31 min; Xero did not specify the cause or fix.
- OutageMajor incident
JiraJira users unable to log time while on business board
Jira users were unable to log time on business boards in a major incident affecting Create and edit. It started at 2026-05-06 03:18 UTC and lasted 3 h 21 min, ending at 2026-05-06 06:39 UTC. Jira deployed a fix and confirmed normal service for all affected customers.
Tuesday, May 5
6 incident changes
- OutageMajor incident
RetoolFront-end assets from retool-edge.com failing to load for some customers
Retool reported a major outage preventing some customers’ Apps from loading because Comcast Business and Optimum (Altice USA / Cabelvision) blocked retool-edge.com. It began at 2026-05-05 23:59 UTC and lasted 2 days 15 h, resolving at 2026-05-08 15:38 UTC after all affected ISPs confirmed the domain was no longer blocked.
- OutageCritical incident
KlaviyoKlaviyo Service Disruption
A critical Klaviyo disruption affected klaviyo.com, APIs, message sending and event processing, potentially preventing logins and campaigns or flows. It started 2026-05-05 21:24 UTC and was resolved 2026-05-07 23:02 UTC (2 days 1 h). Services were restored by 2026-05-06 15:59 UTC; subsequent background recovery did not affect platform use.
- OutageCritical incident
NetlifyAgent Runner failures on new projects
Netlify reported a critical Agent Runners outage affecting builds for some newly created projects, starting 2026-05-05 20:53 UTC and lasting 2 h 19 min. A fix was implemented by 2026-05-05 21:58 UTC, and the incident was resolved at 2026-05-05 23:12 UTC.
- DegradationMajor incident
WorkOSWebhook delivery delayed
WorkOS reported a major incident delaying Authkit webhook delivery from 2026-05-05 16:45 UTC to 2026-05-05 19:48 UTC, lasting 3 h 3 min. Delivery was recovering by 05-05 18:51 UTC, and WorkOS confirmed recovery from all delivery delays at resolution.
- OutageMajor incident
- OutageMajor incident
SalesforceTableau Service Disruption: Analytics Cloud, Sign In
Salesforce reported a major Tableau Cloud disruption affecting MFA sign-ins across 21 instances, impacting Analytics Cloud and Sign In, from 2026-05-05 03:10 UTC to 2026-05-05 05:57 UTC (2 h 47 min). Backend verification requests failed with authorization errors; rolling restarts restored service. Customers using direct links or without MFA did not appear affected.
Monday, May 4
4 incident changes
- OutageMajor incident
SalesforceHeroku Feature Disruption: Apps
Salesforce reported a major Heroku Apps disruption starting 2026-05-04 23:44 UTC, resolved at 2026-05-05 15:48 UTC after 16 h 4 min. Some customers’ Heroku Pipelines review apps stalled in "Creating review app" without build logs; running apps were unaffected. Salesforce increased worker capacity and restarted affected backend workers, restoring review app creation.
- OutageCritical incident
1PasswordSaaS Manager workflows and integrations are failing
1Password reported a critical SaaS Manager outage starting 2026-05-04 17:59 UTC, resolved at 2026-05-04 18:34 UTC (35 min). Workflows and integrations failed, stopping automatic onboarding and off-boarding; their pages also failed to load. A fix was implemented; failed workflows required manual re-runs, while failed integrations would re-run automatically within 24 hours, likely sooner.
- OutageMajor incident
SalesforceService Disruption: Core Service
Salesforce reported a critical Core Service disruption affecting 1 instance, starting at 2026-05-04 14:41 UTC and resolved at 2026-05-04 15:56 UTC. The disruption lasted 1 h 15 min; no cause or fix was stated.
- OutageMajor incident
ContentfulSome customers are experiencing issues logging in
Contentful reported a major Website incident affecting some customers’ logins and email delivery, including invitations and password resets, starting 2026-05-04 13:20 UTC and lasting 3 h 10 min until resolution at 2026-05-04 16:30 UTC. SSO login issues were resolved and most emails were sending again by 14:06 UTC; all issues were reported resolved at 14:08 UTC, with monitoring continuing.
Saturday, May 2
5 incident changes
- OutageMajor incident
DiscordMessage Sends affected on certain channels
Discord reported a major API incident affecting message sends on certain channels, starting at 2026-05-02 17:03 UTC and resolved at 2026-05-02 17:29 UTC, with a computed duration of 25 min. Discord said messaging should be functional after resolution; no cause was stated.
- OutageMajor incident
SalesforceCc Storefront SAnd Or Business Manager Unavailable: B2 CCore
Salesforce reported a major B2 CCore outage affecting storefront and/or Business Manager availability for a subset of customers on 1 instance. It started at 2026-05-02 03:36 UTC and resolved at 2026-05-02 08:14 UTC, lasting 4 h 38 min; Salesforce confirmed resolution after validation and health checks.
- OutageCritical incident
BrexQuickbooks bank feeds connected by Pro Access firms to their clients are...
Brex reported a critical outage of Quickbooks bank feeds connected by Pro Access firms for clients, affecting Partner API and Partner Integrations. It started at 2026-05-02 02:02 UTC and lasted 2 h 7 min, resolving at 2026-05-02 04:09 UTC. Brex rolled out a fix and confirmed successful syncing.
- DegradationMajor incident
StatsigConfig Propagation Delay and Increased Error Rates for Console API
Statsig reported a major incident involving elevated Console API error rates and delayed configuration propagation across Asia Southeast 1, Europe West 1, US East 1, US East 5, and US West 1. It started at 2026-05-02 01:01 UTC and was resolved at 2026-05-02 03:15 UTC, lasting 2 h 14 min.
- OutageCritical incident
JiraThe Work Item view experience of Jira is restored
A critical Jira outage caused work-item error pages and degraded editing across all Jira and Jira Service Management Cloud tenants; Jira boards and support-ticket access were also affected. Recorded from 2026-05-02 00:55 UTC to 2026-05-02 02:48 UTC (1 h 52 min), service was restored. The postmortem cited schema incompatibility.
Friday, May 1
10 incident changes
- OutageCritical incident
- OutageMajor incident
RipplingUS Payroll Runs Not Visible
Rippling reported a major outage in the Rippling App: some Payroll customers could not see upcoming runs. It started 2026-05-01 19:09 UTC and was resolved 2026-05-01 20:54 UTC, lasting 1 h 45 min, after a fix was implemented. Runs with an approval deadline of 5/1/2026 had that deadline moved to 5:30pmPT.
- OutageMajor incident
HoneycombQuery interuption due to database failover in the EU region
Honeycomb reported a major EU-region query outage after an automated database failover at 12:50 UTC affected query engine connection pools; queries failed for roughly 10 minutes before self-resolving. The listed start is 2026-05-01 13:22 UTC and resolution is 2026-05-01 12:30 UTC; computed duration is unknown.
- OutageMajor incident
SanitySanity MCP Server Unavailability
Sanity’s MCP server (mcp.sanity.io) returned 500 errors, disrupting access through tools such as Claude and Cursor in a major-impact outage. It started at 2026-05-01 12:00 UTC and was resolved at 2026-05-01 13:19 UTC; the reported duration was 1 h 18 min. Sanity implemented a fix and monitored results before resolution.
- OutageMajor incident
VantaEU Region Degraded Performance
Vanta reported a major EU-region incident causing elevated errors, degraded performance and possible inability to access the platform; US and AUS regions were unaffected. It started at 2026-05-01 10:25 UTC and was resolved at 2026-05-02 12:43 UTC, lasting 26 h 18 min; Vanta said EU infrastructure recovery took longer than expected.
- OutageCritical incident
- OutageMajor incident
PipedreamBuilding new Python code steps temporarily disabled
Pipedream disabled editing and building new Python code steps in its UI due to a downstream AWS issue. The vendor rated the incident major; it started at 2026-05-01 03:53 UTC and was resolved at 2026-05-03 19:15 UTC, lasting 2 days 15 h.
- OutageMajor incident
SalesforceMarketing Cloud Disruption: Marketing Cloud Core Service
Salesforce reported a major Marketing Cloud Core Service disruption affecting 1 instance, from 2026-05-01 03:03 UTC to 2026-05-01 03:22 UTC (19 min). The incident was resolved; no cause or fix was stated.
- OutageMajor incident
BuildkiteBuildkite service disruption
Buildkite reported a major disruption starting 2026-05-01 02:41 UTC, lasting 49 min. The postmortem says the dashboard, Agent API, REST API and GraphQL were severely degraded for most customers between 02:29 and 02:48 UTC, preventing reliable dashboard access and causing agent communication errors. Buildkite identified a service change, announced a rollback, and subsequently reported normal service restored.
- OutageMajor incident
DatadogElevated Error Rates for Metrics Queries
Datadog reported a major incident affecting Metrics Queries, with some users seeing errors in metrics graphs on the web application or API. It lasted 34 min, from 2026-05-01 00:45 UTC to 2026-05-01 01:19 UTC; Datadog deployed a fix at 01:09 UTC and subsequently confirmed resolution.
Thursday, April 30
3 incident changes
- DegradationMajor incident
Elastic CloudDelayed AutoOps Metrics in AWS us-east-1
Elastic Cloud reported a major degradation causing delayed AutoOps metrics for customers in AWS us-east-1, starting 2026-04-30 21:46 UTC and lasting 50 min until resolution at 2026-04-30 22:36 UTC. The vendor reported the issue fixed and under monitoring at 04-30 22:18 UTC; no cause or specific fix was stated.
- OutageMajor incident
Bunny.netIsolated 502s for Magic Containers
Major isolated 502s affected North American CDN endpoints using Magic Containers and Databases, starting 2026-04-30 10:12 UTC and resolved 2026-05-26 08:23 UTC (25 days 22 h). Database routing adjustments restored service; Bunny.net later fixed delayed endpoint synchronization between Magic Containers and CDN routing, linked to slow sticky session invalidation that left stale endpoint data in use.
- OutageMajor incident
AirtablePartial unavailability for 0.45% bases
Airtable reported a major backend issue affecting availability of up to 0.45% of bases, starting 2026-04-30 09:01 UTC and resolved at 2026-04-30 11:19 UTC (2 h 18 min). After mitigation, bases were back online by 2026-04-30 10:50 UTC; automations remained disabled until full recovery and were re-enabled by resolution.
Wednesday, April 29
6 incident changes
- OutageMajor incident
CanvaSome users may have issues accessing Canva
Some users had issues accessing Canva’s Home page in a major-impact incident from 2026-04-29 23:01 UTC to 2026-04-29 23:26 UTC, lasting 25 min. Canva reported a fix had been implemented at the start of monitoring and later confirmed resolution.
- OutageMajor incident
- OutageMajor incident
- OutageMajor incident
- OutageCritical incident
SnowflakeAzure - UK South (London): INC0156355
Snowflake reported a critical outage in Azure - UK South (London) from 2026-04-29 03:23 UTC to 2026-04-29 04:44 UTC (1 h 21 min), affecting Snowpark Container Services connectivity, Openflow runtime access and connector data transfers. Restarting unhealthy infrastructure restored service; a postmortem RCA is available on Snowflake Community.
- OutageCritical incident
CanvaUsers should be able to access Canva, we are monitoring the fix.
Canva reported a critical access incident starting at 2026-04-29 00:21 UTC, lasting 40 min and resolved at 2026-04-29 01:02 UTC. A fix was implemented and being monitored by 04-29 00:35 UTC; no cause was stated.
Tuesday, April 28
8 incident changes
- OutageMajor incident
CanvaSome users may have issues accessing Canva
Some users had issues accessing Canva in a major-impact incident that started at 2026-04-28 23:24 UTC and was resolved at 2026-04-29 00:35 UTC, lasting 1 h 11 min. Canva did not state a cause or specific fix.
- OutageMajor incident
VantaNew Private and Partner Integrations
Vanta reported a major outage affecting connections to new private and partner integrations, starting at 2026-04-28 21:57 UTC and resolved at 2026-04-29 01:01 UTC after 3 h 4 min. Vanta applied a fix and confirmed services were working as expected again.
- OutageMajor incident
AmplitudeAmplitude web application not loading
Amplitude’s US web application was inaccessible in a major incident attributed to a misconfigured feature flag. The recorded start is 2026-04-28 18:50 UTC, but resolution is listed earlier at 2026-04-28 17:00 UTC; computed duration is unknown, while the vendor reported 10 minutes of impact and confirmed resolution.
- OutageMajor incident
- DegradationMajor incident
DrataCompleted Security Trainings Not Reflected Properly in Personnel Records
Drata reported a major incident where completed Security Awareness Trainings were not properly reflected in Personnel Records, starting 2026-04-28 17:09 UTC and lasting 6 days 2 h. Drata mitigated the issue and resolved it at 2026-05-04 19:19 UTC after syncing trainings and updating corresponding compliance checks.
- DegradationMajor incident
Elastic CloudMissing Metrics in Cloud Console — US East (us-east-1)
Elastic Cloud reported a major degradation in US East (us-east-1): disrupted metric data ingestion left some users missing recent metrics in Cloud console charts and monitoring views. It started at 2026-04-28 14:46 UTC and was resolved at 2026-04-28 18:40 UTC, lasting 3 h 53 min; the system recovered and functionality returned to normal.
- OutageMajor incident
- DegradationCritical incident