Notable SaaS vendor changes, page 22

Sanity reported major query performance degradation affecting a small subset of customers, with increased latency and intermittent timeouts. The recorded start, 2026-06-26 09:53 UTC, is after the recorded resolution, 2026-06-25 20:30 UTC; duration is unknown. Engineering implemented mitigations and restored normal query performance.

Gusto reported a major outage affecting the Gusto.com website, Gusto Mobile, Payroll, Benefits, and HR. It started at 2026-06-25 22:06 UTC and was resolved at 2026-06-25 22:27 UTC, lasting 21 min; no cause or specific fix was stated.

Semgrep reported a major incident causing widespread exit code 7 scan failures in Managed Scans and Scans and CI/CD from 2026-06-25 21:32 UTC to 2026-06-25 22:27 UTC (55 min). A bad AI skills rules release caused the failures; Semgrep removed "skills.behavioral.skill-destructive-commands.skill-destructive-commands" and confirmed scans were running normally.

Box reported a major ZIP download incident affecting folder downloads in its web application, with failures or delays for users routed through one US region. It started at 2026-06-25 19:29 UTC and was resolved at 2026-06-25 21:47 UTC, lasting 2 h 18 min. Box attributed the issue to a network component update affecting a regional backend service.

Brex reported a critical incident involving missing transactions in feeds to Quickbooks, Expensify and other partners, from 2026-06-25 18:59 UTC to 2026-06-26 03:28 UTC (8 h 28 min). Syncing was restored; most missing transactions were expected to appear automatically within 24 hours, with rare cases requiring additional action and direct outreach.

Confluent reported a major Confluent Cloud Metrics API incident starting 2026-06-25 15:59 UTC, resolved at 2026-06-25 17:53 UTC after 1 h 54 min. The vendor reported increased error rates from 2026-06-25 15:15 UTC to 2026-06-25 15:55 UTC and said the incident was mitigated and systems recovered.

AssemblyAI reported a major US Asynchronous API outage starting 2026-06-25 15:37 UTC (reported impact began 15:00 UTC), resolved at 2026-06-25 16:48 UTC; computed duration: 1 h 10 min. Speaker diarization failures caused timeouts for speaker-labeled files under 2 minutes, with backlog delays and timeouts affecting other requests; a fix was released and processing recovered.

Upstash Redis and Redis Global experienced a major partial service disruption in eu-central-1, us-east-1 and us-west-1 from 2026-06-25 15:23 UTC to 2026-06-25 16:36 UTC, lasting 1 h 12 min. Upstash reported implementing a fix at 06-25 15:31 UTC; no cause was stated, and an RCA was promised.

Vercel reported a major Workflow degradation: some recently deployed projects had runs stuck as pending and queued messages were not delivered. The incident lasted 5 h 58 min, from 2026-06-25 07:45 UTC to 2026-06-25 13:43 UTC. A fix was fully rolled out; the interim workaround was rollback to a working deployment created before Jun 24 21:00 UTC.

A major Workflow degradation left some recently deployed projects stuck pending and not delivering queued messages from 2026-06-25 07:45 UTC to 2026-06-25 13:43 UTC, lasting 5 h 58 min. A fix was rolled out; the interim workaround was an instant rollback to a working deployment created before Jun 24 21:00 UTC to resume new runs.

Major Dropbox Sign incident: Ashby could not process inbound data starting at 4:30PM (UTC); e-signature requests were sent, but status updates were not recorded. Tracked from 2026-06-24 21:16 UTC until resolution at 2026-06-24 22:21 UTC (1 h 4 min), after a fix was implemented and data recovery began.

Parts of the Rippling App were degraded and not loading in a major-impact incident starting 2026-06-24 19:18 UTC. Site access returned to normal at 19:31 UTC; Rippling reported mitigation fixes at 20:10 UTC and resolved the incident at 2026-06-24 20:56 UTC, after 1 h 38 min.

Honeycomb reported a major US and EU ingest outage starting 2026-06-24 18:14 UTC, resolved at 19:04 UTC after 50 min. Impact was primarily US: some telemetry was lost, triggers may not have fired, and SLO evaluations and Service Maps were delayed. Honeycomb rolled back a recent deploy; the postmortem reports telemetry gaps up to half an hour.

Snowflake reported a critical outage in AWS - US East (N. Virginia), affecting Snowsight access and potentially sign-in, queries and data management. It ran from 2026-06-24 15:38 UTC to 2026-06-24 17:22 UTC (1 h 44 min). Snowflake implemented a fix, confirmed recovery through monitoring and published an RCA link on Snowflake Community.

AssemblyAI reported a critical degradation affecting only EU pre-recorded audio transcription traffic for Universal-3-Pro and Universal-3-5-Pro. It started at 2026-06-24 09:13 UTC and was resolved at 2026-06-24 10:40 UTC, lasting 1 h 26 min. A fix was implemented at 10:05 UTC; all systems were operating normally at resolution.

SurveyMonkey reported a major incident preventing users from logging in, starting at 2026-06-23 20:08 UTC and resolved at 2026-06-23 20:55 UTC, with a computed duration of 46 min. A fix was implemented by 2026-06-23 20:43 UTC.

Hootsuite reported a major incident affecting Analytics and Planner Calendar, causing slow loading or an "unexpected error occurred" message. It started at 2026-06-23 19:03 UTC and was resolved at 2026-06-23 20:34 UTC, lasting 1 h 30 min. A fix was released at 19:32 UTC, reducing errors.

CircleCI reported a major Docker Jobs incident from 2026-06-23 18:34 UTC to 2026-06-23 19:58 UTC (1 h 23 min), with jobs queuing or stuck in "preparing environment." A fix restored normal starts while the backlog cleared; the postmortem identified a single Docker job cluster operating below expected performance.

Some Gusto customers were unable to run payroll during an incident rated critical, with Payroll, Benefits, HR listed as affected components. It started at 2026-06-23 18:20 UTC and was resolved at 2026-06-23 19:16 UTC, lasting 55 min; no cause or fix was stated.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.