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.
Tuesday, June 23
6 incident changes
- OutageMajor incident
GitLabErrors interacting with git via SSH
GitLab reported a major incident causing errors in repository operations via SSH; HTTPS did not appear impacted. It started at 2026-06-23 17:33 UTC and was resolved at 2026-06-23 19:52 UTC, lasting 2 h 19 min. GitLab identified a problematic change and reported successful SSH interactions after implementing mitigating changes.
- OutageMajor incident
ExpoApple Developer API outage
Expo reported a major Apple Developer API outage affecting App Store Connect API interactions, including signing in and generating credentials. It started at 2026-06-23 17:28 UTC and was resolved at 2026-06-23 19:45 UTC, lasting 2 h 16 min.
- OutageMajor incident
Snowflake’s major outage affected Streamlit apps, Notebooks and other Snowpark Container Services in AWS - US West (Oregon). Customer impact began at 15:20 UTC June 23, 2026; the recorded incident ran from 2026-06-23 17:01 UTC to 2026-06-24 07:30 UTC (14 h 29 min). Restarting affected infrastructure restored remaining services.
- OutageCritical incident
WixRESOLVED: Issues with Stores Product Catalog
Wix reported a critical outage affecting Stores Product Catalog, Checkout, Storefront and Store Management from 2026-06-23 09:16 UTC to 2026-06-23 09:56 UTC, lasting 40 min. Wix identified a DB issue, worked to revert the changes that caused it, and confirmed a fix before resolving the incident.
- OutageMajor incident
BigCommerce reported a major Analytics outage preventing shopper-event capture; Control Panel Analytics Reports and Facebook Conversions API (FBCAPI) data for the affected window remain degraded or missing. It started and was resolved at 2026-06-23 03:57 UTC (computed duration: 0 min); engineers resolved the issue, and current events are processing normally.
- OutageMajor incident
Snowflake reported a major outage in AWS - Europe (London), preventing Snowpark Container Services access and intermittently blocking Snowsight sign-ins with HTTP 500 errors. The stated impact began at 22:38 UTC June 22, 2026; recorded duration was 1 h 29 min, with resolution at 2026-06-23 02:35 UTC after reverting a recent configuration change.
Monday, June 22
17 incident changes
- DegradationMajor incident
SnykDegraded Performance SNYK-US-01
Snyk reported major performance degradation in SNYK-US-01 (app.snyk.io), with increased UI, API, CLI, SCM project and PR Check latency; some tests could time out and fail. It started 2026-06-22 22:21 UTC and was resolved 2026-06-24 21:34 UTC, lasting 47 h 13 min. Mitigation improved success rates and latency and reduced the backlog.
- DegradationMajor incident
Segment(US West 2) Partial degradation of Linked Audiences, Linked Events, Reverse ETL, and Profile Sync due to external Snowflake Outage
Segment reported major degradation in US West 2 affecting Linked Audiences, Linked Events, Reverse ETL, and Profile Sync; syncs and data processing could fail due to an upstream Snowflake outage. It started at 2026-06-22 22:14 UTC and resolved at 2026-06-23 00:22 UTC, lasting 2 h 7 min. Functionality recovered after Snowflake’s outage resolved; no customer action was required.
- DegradationMajor incident
WorkOSDegraded performance for Directory Provisioning for Authkit
WorkOS reported a major Directory Provisioning for AuthKit degradation starting 2026-06-22 21:36 UTC, lasting 2 days 7 h and resolved at 2026-06-25 05:12 UTC. Directories created before June 22, 21:36:17 UTC had delayed downstream user and organization membership changes. WorkOS attributed the issue to an internal production data migration; remaining out-of-sync user records were restored.
- DegradationMajor incident
Datadog reported a major incident causing elevated latency on metrics queries in Metrics and Infra Monitoring, slowing customer queries. It started at 2026-06-22 21:27 UTC and was resolved at 2026-06-22 22:41 UTC, lasting 1 h 13 min; Datadog reported implementing a fix but did not specify the cause.
- OutageCritical incident
SnowflakeAWS - US West (Oregon): INC0159680
Snowflake reported a critical outage in AWS - US West (Oregon) from 2026-06-22 20:35 UTC to 2026-06-23 00:26 UTC, lasting 3 h 51 min. Customers may have been unable to sign in, execute queries, or manage data. Snowflake improved processing efficiency on affected infrastructure and confirmed service restoration.
- OutageMajor incident
DrataBulk Actions on Personnel Degraded
Drata temporarily disabled the 'Bulk Actions' button on the Personnel page, preventing customers from using that functionality. The vendor rated the incident major; it began 2026-06-22 18:01 UTC and lasted 4 days 3 h, resolving at 2026-06-26 21:18 UTC. Drata reported an edge case during validation and deployed a fix before resolution.
- CriticalCritical incident
- OutageCritical incident
GorgiasChat are not working properlyEvent
Gorgias reported a critical incident affecting Helpdesk Integrations - Live Chat and Live Chat, which were not working properly from 2026-06-22 14:50 UTC to 2026-06-22 15:22 UTC (32 min). A fix was implemented, and Gorgias confirmed chat was stable at resolution.
- CriticalCritical incident
- MajorMajor incident
- CriticalCritical incident
- CriticalCritical incident
- CriticalCritical incident
- CriticalCritical incident
- CriticalCritical incident
- OutageMajor incident
CanvaSome users may experience errors while accessing Canva Design Agent
Some users experienced errors accessing Canva Design Agent in a major-impact incident from 2026-06-22 04:16 UTC to 2026-06-22 07:28 UTC, lasting 3 h 12 min. Canva reported identifying the issue and implementing a fix, then marked the incident resolved.
- CriticalCritical incident
Sunday, June 21
1 incident change
- CriticalCritical incident
Friday, June 19
16 incident changes
- OutageMajor incident
JiraJira : Incoming emails partial outage
Jira reported a major outage affecting Jira and JSM customers using Microsoft OAuth to create tickets from email: incoming email could not be read. It started at 2026-06-19 22:46 UTC and was resolved at 2026-06-26 05:13 UTC, lasting 6 days 6 h. New email processing was fixed; affected customers were instructed to re-authorize their Microsoft mail server.
- OutageMajor incident
Certain Rippling app pages, including the hiring flow and employee profiles, crashed in a major-impact incident from 2026-06-19 20:03 UTC to 2026-06-19 20:27 UTC, lasting 24 min. Rippling disabled the feature flag causing the issue and reported the app operational again at 20:07 UTC.
- OutageMajor incident
GreenhouseMicrosoft 365 Delivery Issues
Greenhouse reported a major incident in which emails might not be sent for customers using custom SMTP routes with Microsoft 365. It started at 2026-06-19 17:24 UTC and resolved at 2026-06-19 22:24 UTC, lasting 4 h 59 min. A fix was implemented by 06-19 21:49 UTC.
- OutageMajor incident
SalesforceSalesforce Data Cloud Feature Disruption: Customer360 Audiences
Salesforce’s major Customer360 Audiences disruption affected 3 instances, with Tableau Next Data Source (TDS) users potentially unable to access the Tableau Next Analytics Agent. It lasted 8 h 45 min, from 2026-06-19 16:45 UTC to 2026-06-20 01:30 UTC. Salesforce mitigated service instability, identified dependent-service connectivity failures, and reported restored stability and performance.
- DegradationMajor incident
CountDegraded AI and API operations
Count reported major degradation of AI, private/public APIs and query execution across EU and US components, starting 2026-06-19 15:32 UTC and resolved at 2026-06-19 15:45 UTC (12 min). Count suspected private GCP endpoint access issues, identified a potentially responsible infrastructure update and rolled back to a last-known-good state.
- CriticalCritical incident
- OutageMajor incident
MakeLogin to make.com UI not working
Make reported a major outage preventing login to the make.com user interface, starting 2026-06-19 14:08 UTC and resolved at 2026-06-19 15:11 UTC (1 h 2 min). Login was restored to all zones at 14:50 UTC; scenario executions and webhooks were unaffected.
- OutageMajor incident
SalesforceHeroku Retroactive Service Disruption: Platform API
Heroku Platform API experienced a major disruption in all regions starting 2026-06-19 13:23 UTC, lasting 4 h 8 min until resolution at 2026-06-19 17:31 UTC. Customers may have encountered broken ‘pipelines/:id/latest-builds’ API calls and problems viewing the pipeline dashboard. Salesforce attributed the incident to a recently deployed change and reverted it to resolve the issue.
- MajorMajor incident
- OutageMajor incident
PostmanElevated error rates for Agent Mode
Postman reported elevated error rates for Agent Mode, with some service disruptions expected, affecting Europe - Postman API. The vendor rated the impact major; the incident started at 2026-06-19 12:17 UTC and was resolved at 2026-06-19 12:48 UTC, with a computed duration of 30 min. No cause or fix was stated.
- DegradationMajor incident
AircallAnalytics Dashboards Not Loading
Aircall reported a major incident affecting Analytics dashboards and Call History loading from 2026-06-19 10:43 UTC to 2026-06-19 19:29 UTC, lasting 8 h 46 min. Performance returned to normal following work by its third-party provider; the root cause was still being investigated before resolution.
- CriticalCritical incident
- OutageMajor incident
UpstashQStash Service Disruption in the EU Region
Upstash reported a major QStash EU outage starting 2026-06-19 09:11 UTC; computed duration: 0 min. Its postmortem says a networking configuration change degraded outbound connectivity between 09:11 and 09:45 UTC, potentially failing initial message dispatches and causing some servers to use IPs outside the advertised outbound range. Upstash said the issue was resolved.
- OutageMajor incident
ExpoEnvironment variables page shows an error
Expo’s Environment variables page showed an error in a major Website incident starting 2026-06-19 09:02 UTC and lasting 10 min. It was resolved at 2026-06-19 09:13 UTC after a fix was deployed; customers should refresh the pages to restore access.
- CriticalCritical incident
- DegradationMajor incident
Ashby reported a major integration degradation caused by an infrastructure issue, affecting Google Workspace integration (including sending via Gmail), ATS syncs, autocomplete for candidate resumes/locations, and some AI features. It started and was marked resolved at 2026-06-19 06:30 UTC, with a recorded duration of 0 min.
Thursday, June 18
9 incident changes
- DegradationMajor incident
BigCommerceStorefront Search Issues for Subset of AU Stores
BigCommerce reported a major incident affecting storefront search availability and latency for a subset of stores in Australia. It started at 2026-06-18 22:20 UTC and was resolved at 2026-06-18 22:29 UTC, with a reported duration of 8 min; no cause or fix was stated.
- OutageMajor incident
Honeycomb reported a major incident affecting EU1 Enhance and US1 Enhance, with enhance-related requests failing to complete beginning June 17th. The incident record started and resolved at 2026-06-18 19:10 UTC (computed duration: 0 min); Honeycomb said it deployed a fix and Enhance was fully operational.
- MajorMajor incident
- OutageCritical incident
MatillionConnectivity Issues in AU1 Production
Matillion reported a critical AU1 production outage affecting Agent Manager and Agents: cloud-agent-service could not authenticate with secure credential storage, preventing startup. It began at 2026-06-18 13:43 UTC and was resolved at 2026-06-18 15:05 UTC, lasting 1 h 21 min; Matillion reported implementing a fix before resolution.
- DegradationMajor incident
GreenhouseBIC: Delays in delivering data for Silo 1
Greenhouse reported a major delay in Business Intelligence Connector (BIC) data delivery for Silo 1, affecting customers awaiting that data. The incident started at 2026-06-18 12:35 UTC and was resolved at 2026-06-18 13:02 UTC, lasting 27 min; no cause or fix was stated.
- OutageMajor incident
MuxIncreased error in Video Live and VOD
Mux reported a major incident affecting Live and VOD delivery in Europe regions, starting 2026-06-18 10:16 UTC and resolved at 2026-06-18 13:18 UTC (3 h 2 min). Mux identified an issue with a CDN provider and said delivery returned to normal, with the actual impacted window reported as 9:30 - 10:30 UTC.
- DegradationMajor incident
BuildkiteIncreased latency and error rates
Buildkite reported a major degradation affecting the REST API’s builds create API for a subset of tenants, with increased latency and error rates. It started at 2026-06-18 08:05 UTC and lasted 1 h 37 min, resolving at 2026-06-18 09:43 UTC; a fix was deployed and full recovery confirmed.
- MajorMajor incident
- OutageMajor incident
SalesforceCc Storefront SAnd Or Business Manager Unavailable: B2 CCore
Salesforce reported a major B2C Commerce Cloud outage on POD372 starting 2026-06-18 00:17 UTC, blocking Storefronts and other services. The recorded duration was 2 h 23 min; a brief recurrence at 02:40 UTC ended with full restoration at 03:43 UTC. Salesforce attributed the outage to an infrastructure configuration issue preventing environments from completing a planned update.