Notable SaaS vendor changes, page 23

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.

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.

Box reported a major-impact outage causing intermittent failures loading the "All files" page and subfolders, affecting customers’ ability to browse content. It started at 2026-06-17 19:34 UTC and was resolved at 2026-06-17 20:28 UTC, lasting 54 min. Box reported improvement after remediation steps and confirmed full Webapp functionality was restored.

Wiz reported major intermittent login failures affecting Authentication and Portal from 2026-06-17 17:30 UTC to 2026-06-17 17:58 UTC, lasting 28 min. A fix was implemented at 17:43 UTC, and the incident was resolved at 17:58 UTC.

Elastic Cloud reported a major outage affecting deployment creation/updates in AWS eu-central-1, eu-west-2, us-west-1, us-east-2; Azure azure-southafricanorth, azure-eastus2; and GCP europe-west4. It started at 2026-06-17 15:52 UTC and resolved at 2026-06-17 17:35 UTC, lasting 1 h 42 min. A fix was deployed by 06-17 16:53 UTC.

Optimizely reported a major degradation dropping some email campaign messages in the NA Region from 2026-06-17 14:00 UTC to 2026-06-20 17:41 UTC, lasting 3 days 3 h. Optimizely cited a likely SendGrid header-processing incompatibility and deployed a fix; it lacked records identifying which recipients received messages, complicating decisions about rerunning affected campaigns.

Greenhouse reported a major degradation delaying Business Intelligence Connector (BIC) data delivery across all silos, affecting customers’ access to updated data. It started at 2026-06-17 12:55 UTC and was resolved at 2026-06-18 07:57 UTC, lasting 19 h 2 min; Greenhouse identified the issue and worked on a fix but provided no cause or fix details.

RudderStack reported a major Control Plane instability incident in US, EU and IN, increasing event delivery latency across customers; ingestion was unaffected. It started at 2026-06-17 12:45 UTC and resolved at 2026-06-17 13:14 UTC, lasting 28 min. RudderStack identified the issue and monitored the system but stated no specific cause or fix.

Canva reported a major incident affecting design creation and login on its iOS and iPad apps in Australia and New Zealand. It started at 2026-06-17 02:53 UTC and was resolved at 2026-06-17 03:54 UTC, lasting 1 h 1 min; Canva implemented a fix but did not state a cause.

Elastic Cloud reported a major ingestion outage affecting Managed OTLP (mOTLP) and Managed Intake Service (.amp) endpoints in Azure Australia East. It started at 2026-06-16 22:54 UTC and was resolved at 2026-06-17 00:59 UTC, lasting 2 h 4 min; upstream providers were working to resolve it, but no specific cause or fix was stated.

A major Kibana authentication outage affected Deployments and Projects: the "Log in with Elastic Cloud" button failed. It started at 2026-06-16 10:57 UTC and was resolved at 2026-06-16 11:36 UTC, lasting 38 min. Customers could use the Kibana link inside the Elastic Cloud console as a workaround; Elastic reported identifying the root cause and mitigating the issue.

Snowflake reported a major outage from 2026-06-16 10:29 UTC to 2026-06-16 20:20 UTC: customers in the listed AWS, Azure and GCP regions could be unable to use Git repository functionality in Workspaces, including pulling changes. Snowflake identified a recent release issue and reported rolling back the affected release.

Optimizely reported a major CMP outage making Plan, Requests, Library / DAM and Analytics inaccessible to customers. It started at 2026-06-16 07:04 UTC and was resolved at 2026-06-16 08:52 UTC, lasting 1 h 48 min; a fix was implemented by 07:32 UTC.

Convex reported a major outage with high error rates across all deployments except some D1024s, affecting Business, Free & Starter, Professional and their Live Traffic components. It started at 2026-06-15 22:23 UTC and was resolved at 2026-06-15 22:35 UTC, lasting 12 min; a fix reduced error rates.

Some Canva users had access issues and intermittent problems downloading designs in a major-impact outage starting 2026-06-15 20:20 UTC. Canva marked it resolved at 2026-06-15 21:03 UTC; the recorded duration was 42 min. No cause or specific fix was stated.

Elastic Cloud reported a major incident in AWS us-east-1 that could intermittently make Elastic Cloud Serverless projects unavailable or prevent new project creation. It ran from 2026-06-15 17:31 UTC to 2026-06-15 19:13 UTC, lasting 1 h 42 min; Elastic reported mitigation at 18:00 UTC and subsequent resolution.

A major outage prevented Safari and iOS users from viewing or applying to jobs on embedded and Ashby-hosted job boards. The incident ran from 2026-06-15 16:59 UTC to 2026-06-15 19:15 UTC (2 h 16 min). Ashby implemented a fix; affected users needed to refresh links from jobs.ashbyhq.com or you.ashbyhq.com.

A critical Snowsight outage in Azure - East US 2 (Virginia) left customers potentially unable to access Snowflake services and features, with intermittent degradation later reported. It started 2026-06-15 14:30 UTC and was resolved 2026-06-16 21:15 UTC; the recorded duration was 30 h 44 min. Snowflake validated its third-party provider’s infrastructure fix and confirmed service restoration.

Some Canva users experienced errors exporting video in a major-impact incident starting 2026-06-15 11:01 UTC. Engineers identified the issue, and the incident was resolved at 2026-06-15 11:22 UTC after 21 min; no cause or specific fix was stated.

Lightdash Cloud (EU) was unavailable, with possible server errors for customers in Europe, during a critical incident starting 2026-06-15 09:25 UTC. A fix was implemented at 09:33 UTC, and the incident was resolved at 2026-06-15 09:44 UTC after 19 min.

Sanity reported a major query-performance degradation affecting some customers across apicdn.sanity.io, api.sanity.io, and GraphQL, increasing content-query latency. It started at 2026-06-15 06:15 UTC and was resolved at 2026-06-15 10:24 UTC, lasting 4 h 9 min; a fix was implemented and monitored.

A major incident caused elevated latency and errors in FRA1 (Frankfurt, Germany), affecting the region and its CDN. It started at 2026-06-14 21:03 UTC and was resolved at 2026-06-15 01:24 UTC, lasting 4 h 20 min. Traffic was rerouted to CDG1 to mitigate impact, then fully restored to FRA1.

Vercel reported major elevated latency and errors affecting FRA1 (Frankfurt, Germany), including its CDN. The incident lasted 4 h 20 min, from 2026-06-14 21:03 UTC to 2026-06-15 01:24 UTC. Vercel mitigated impact by rerouting traffic to CDG1, then reported the issue fixed and all traffic restored to FRA1.

Brex reported a critical outage affecting Dashboard, Partner API and Partner Integrations: database maintenance caused HTTP 500 errors and disrupted some card and transaction operations. Recorded from 2026-06-14 05:11 UTC to 2026-06-14 05:29 UTC (18 min), it was resolved after maintenance completed; failed API calls could be retried.

Brex reported a critical incident affecting the Team API and Dashboard, starting 2026-06-13 15:10 UTC and resolved at 2026-06-13 15:17 UTC (7 min). Database maintenance caused HTTP 500 errors for some Team API requests and temporarily unavailable user information that could prevent Dashboard loading. Maintenance completed; failed API calls could be retried successfully.

Brex Travel experienced a critical outage preventing customers from booking and managing trips from 2026-06-13 05:21 UTC to 2026-06-13 07:53 UTC, lasting 2 h 32 min. Brex reported the issue resolved and said users could resume using Brex Travel; no cause or specific fix was stated.

Klaviyo reported a major outage affecting WhatsApp messaging, Meta integrations, and Instagram connectivity from 2026-06-12 14:49 UTC to 2026-06-12 17:30 UTC (2 h 40 min), caused by an upstream provider disruption. Services returned to normal; failed messages were reprocessed, but a small number that never reached Klaviyo could not be recovered.

Gorgias reported a major outage affecting outbound Facebook, WhatsApp and Instagram messages, attributed to an outage on Meta’s side. It started at 2026-06-12 14:27 UTC and was resolved at 2026-06-12 18:29 UTC, lasting 4 h 2 min.

Hootsuite reported a major Meta-related incident affecting Facebook, Instagram, and Threads functionality, including publishing, analytics, and Inbox messaging. It started at 2026-06-12 14:01 UTC and lasted 4 h 17 min, resolving at 2026-06-12 18:18 UTC when Meta assets were fully accessible again in the Hootsuite dashboard.

Lightdash reported a major outage affecting dashboard chart queries for app.lightdash.cloud users on Lightdash Cloud (US), with errors stating "Invalid timezone: project_timezone". It started at 2026-06-12 10:19 UTC and was resolved at 2026-06-12 10:44 UTC, lasting 24 min; a fix was applied and monitored.

Confluent Cloud reported major intermittent inter-region connectivity degradation affecting AWS us-west-2, causing delays or errors with Cluster Linking, Flink processing, and UI log access. Recorded start: 2026-06-12 07:42 UTC; the vendor later stated approximately 04:00 UTC. A mitigation was deployed; resolution was recorded at 2026-06-12 11:55 UTC, with a computed duration of 4 h 12 min.

LaunchDarkly reported major elevated errors affecting some application requests, with authentication, experiment management, flag targeting, progressive rollouts and the web app listed as affected. The incident started at 2026-06-12 04:23 UTC and resolved at 2026-06-12 04:58 UTC (35 min); monitoring confirmed no further impact beyond the initially reported error window.

Buildkite reported a major incident involving increased REST and GraphQL API latency for all customers, starting 2026-06-11 23:18 UTC and resolved 2026-06-12 00:16 UTC (57 min). Buildkite attributed the issue to elevated REST API service load and confirmed recovery after mitigation; the agent and stacks API were unaffected.

Chargebee reported a critical email service degradation affecting Email Notifications in AU, EU and US, delaying system notifications due to an email-provider issue. It started at 2026-06-11 23:15 UTC and was resolved at 2026-06-12 02:12 UTC, lasting 2 h 57 min. New notifications resumed, and Chargebee said it would reprocess queued emails.

Some Grain local captures were stuck processing in a major Recording Processing incident from 2026-06-11 23:12 UTC to 2026-06-23 16:14 UTC, lasting 11 days 17 h. Grain resolved the incident and reported that all hung local captures were recovered.

1Password reported a critical Device Trust Authentication Service incident affecting USA/Global, with authentication failures, timeouts and 503 errors. It started at 2026-06-11 21:49 UTC and was resolved at 2026-06-12 23:18 UTC, lasting 25 h 29 min. Authentication services were reported recovered at 06-11 22:32 UTC; the vendor later reported identifying a cause and taking relief steps without specifying details.

Gorgias reported major delays in HTTP integrations for some accounts from 2026-06-11 21:44 UTC to 2026-06-11 22:18 UTC, lasting 34 min. A fix was implemented at 2026-06-11 22:14 UTC, and the incident was subsequently resolved.

Grain reported a major Grain Recorder outage starting 2026-06-11 15:18 UTC, with scheduled bots delayed in joining and ad-hoc bot failures caused by an upstream provider outage. The incident lasted 6 h 6 min and was resolved at 2026-06-11 21:24 UTC, with no further bot-service degradation observed.

DigitalOcean reported a major outage affecting Gradient AI DeepSeek V4 Pro, which returned HTTP 429 "Rate limit exceeded" errors in Agentic Inference Cloud - Model Services and Model Services. It started at 2026-06-11 14:24 UTC and was resolved at 2026-06-11 17:42 UTC, lasting 3 h 17 min; DigitalOcean identified the issue and implemented a fix without specifying details.

FullStory reported major Guides & Surveys degradation in its NA data center: guides, tours, surveys, and smart tips could display incorrectly, with interaction data delayed. The incident ran from 2026-06-11 13:58 UTC to 2026-06-11 17:08 UTC (3 h 10 min). Resource exhaustion caused the issue; delivery returned to normal, and additional safeguards are being implemented.

Box reported major degradation affecting API authentication, Login/SSO, Box Sign, and Box Edit / Tools, potentially disrupting access and work in Box. The incident ran from 2026-06-11 00:34 UTC to 2026-06-11 02:01 UTC (1 h 26 min). Box applied remediation and confirmed full functionality was restored.

Snowflake reported a critical outage affecting access to multiple core services in Azure - East US (Virginia) - Applications. It started and resolved at 2026-06-11 00:30 UTC, with a recorded duration of 0 min; Snowflake reverted a misconfigured change and confirmed service restoration. A completed postmortem links to an RCA on Snowflake Community.