What vendors changed

BrexSlow loading of activity logs and audit trail

Brex reported a critical Dashboard incident causing slow loads or timeouts for activity on expenses, bills, users, cards and account audit trails; other product areas were unaffected. It started at 2026-06-04 21:23 UTC and lasted 38 min, resolving at 2026-06-04 22:01 UTC. Brex reported a fix in place at 2026-06-04 21:37 UTC.

NetlifyElevated error rates for a subset of sites using Edge Functions

Netlify reported a major Edge Functions incident causing elevated 504 errors and slow page loads for some sites beginning approximately 17:00 UTC. The recorded incident started at 2026-06-04 20:24 UTC, lasted 34 min, and resolved at 2026-06-04 20:59 UTC. Mitigation restored normal error rates around 20:30 UTC; no customer action was required.

SquarespaceAcuity Scheduling Elevated Errors

Squarespace reported a critical disruption involving Acuity Scheduling elevated errors and Accounts & Billing; all users and services may have been affected. It started at 2026-06-04 18:58 UTC and was resolved at 2026-06-04 19:30 UTC, lasting 31 min. A fix was implemented, but no cause was stated.

DDrataDegraded AIQA Performance

Drata reported a major incident isolated to AIQA, with elevated errors attributed to degraded performance of an upstream provider. It ran from 2026-06-04 16:22 UTC to 2026-06-04 17:29 UTC, lasting 1 h 7 min. Drata reported that the provider stabilized and a fix was implemented before marking the incident resolved.

RetoolRetool Mobile apps cannot be opened in the in-browser preview

Retool Mobile apps failed to load in browser user-mode and editor previews during a major outage starting 2026-06-04 15:13 UTC, resolved at 2026-06-04 19:16 UTC (4 h 2 min). Editing mobile apps and native iOS/Android use were unaffected; Retool reported implementing a fix.

IimgixIncreased errors for new render requests (Rendering & Legacy video APIs)

NNebiusNetwork Connectivity Issues

Elastic CloudCustomers may see delays with creating Azure serverless projects

Elastic Cloud reported a major incident causing delays creating Azure serverless projects and possible temporary unavailability of existing Azure projects. It started at 2026-06-04 01:51 UTC and was resolved at 2026-06-04 09:20 UTC, lasting 7 h 28 min; recovery began during monitoring, but no cause was stated.

SSalesforceField Service Mobile Feature Disruption: Field Service Mobile

Salesforce reported a major Field Service Mobile disruption across 29 instances: customers with performance priming enabled could experience syncing failures. It started 2026-06-03 21:27 UTC and was resolved 2026-06-10 22:49 UTC, lasting 7 days 1 h. Salesforce identified a recent deployment as the technical trigger and restored syncing by completing rollbacks.

LLaunchDarklyFlag dashboard is failing to load

LaunchDarkly’s flag dashboard failed to load in a major-impact outage affecting flag targeting, from 2026-06-03 19:31 UTC to 2026-06-03 20:26 UTC (55 min). A fix was implemented, and LaunchDarkly confirmed the dashboard was successfully loading when the incident was resolved.

Box[Critical] Issues with Multiple Box Services

Box reported a critical outage affecting Login, All Files, Notes, Uploads and Box API. It started and was marked resolved at 2026-06-03 17:53 UTC (computed duration: 0 min). Box said its systems automatically detected and corrected the underlying issue, with no current impact.

KKlaviyoShopify API Outage

Klaviyo’s major Shopify API outage caused integration setup errors and data-sync delays from 2026-06-03 14:23 UTC to 2026-06-03 17:16 UTC, lasting 2 h 52 min. Klaviyo attributed it to a partial upstream-service outage; syncing returned to normal, with automated retries clearing backlogs and failed integration states. Customers whose new integration setup failed can retry.

LLlamaIndexIncreased parse latency

AAmplitudeAmplitude Platform Unavailability

Amplitude reported a critical outage affecting application access and interface loading across Analytics, Audiences, Data, Experiment, Guides & Surveys, and Session Replay. It started at 2026-06-03 13:13 UTC and was resolved at 2026-06-03 13:26 UTC, lasting 13 min. Amplitude implemented a fix and expected no data loss.

AAmplitudeAmplitude Platform Unavailability

Amplitude’s critical platform outage prevented application access or caused significant interface errors, with issues reported since 11:58 AM UTC. The incident was recorded from 2026-06-03 12:25 UTC to 2026-06-03 12:52 UTC (27 min), when normal service was restored. Amplitude expected no data loss and said no customer action was needed.

RRunwayIssues with Seedance and Seedream generations

Runway reported a major incident with increased error rates for Seedance and Seedream generations across App, Backend, and Public API. It started at 2026-06-03 08:04 UTC and was resolved at 2026-06-03 08:23 UTC; the computed duration was 18 min. Tasks were recovering by 08:18 UTC; no cause or fix was stated.

Red Hat (incl. Quay.io)repository.jboss.org - Outage

SSvix[EU] Elevated response times and error rates affecting some customers.

MongoDB AtlasInvestigating connection issues to ADFA in GCP

A major outage affected connections and queries to MongoDB Atlas Data Federation and Online Archive instances in GCP regions from 2026-06-02 23:00 UTC to 2026-06-03 00:11 UTC, lasting 1 h 11 min. MongoDB identified a networking issue in GCP regions and reported mitigation, with connections working at resolution.

DDevin (Cognition)Sessions Stuck

GGrainBot Recording Failures

Grain Recorder had a major outage causing delayed bot joins and recording failures due to an upstream provider outage. It started at 2026-06-02 15:20 UTC and was resolved at 2026-06-03 16:49 UTC, lasting 25 h 29 min. Recordings stuck in processing required manual recovery; Grain confirmed all successfully captured recordings were recovered.

OOptimizelyInvestigating – Content Recommendation Service Degradation in EMEA region

Optimizely’s Content Recommendations API in EMEA could not serve recommendations during a major-impact incident from 2026-06-02 07:48 UTC to 2026-06-02 12:25 UTC, lasting 4 h 36 min. Users could see missing or unavailable recommendations across the platform. Optimizely reported an API disruption, implemented a fix at 08:51 UTC, and confirmed resolution.

LLogRocketDashboard instability

LogRocket reported a major Dashboard incident involving slow and failing dashboard queries, starting 2026-06-02 05:23 UTC and resolved at 2026-06-02 06:10 UTC, lasting 46 min. The vendor identified the problem and reported rolling out a fix at 05:41 UTC; no cause was stated.

XeroGlobal: Invoicing - some customers may be experiencing issues with accessing invoicing in Xero.

Xero reported a major global invoicing outage affecting some customers, starting 2026-06-01 23:55 UTC and resolved 2026-06-02 01:00 UTC, lasting 1 h 4 min. A product release made invoicing unavailable; Xero implemented a fix and confirmed resolution.

MMaven Centralsearch.maven.org is down

RenderUnable to load metrics for some services in Oregon

Render reported a major incident preventing metrics from loading for some services in Oregon; logs were unaffected. It started at 2026-06-01 21:25 UTC and was resolved at 2026-06-01 21:45 UTC, lasting 20 min.

TTeleportNew Trials Fail to Provision

Bunny.netInvestigating Issues with Magic Containers and Databases

Bunny.net reported major degradation affecting Magic Containers and Bunny Database from 2026-06-01 16:02 UTC to 2026-06-01 20:18 UTC (4 h 16 min). Magic Containers workloads may have experienced processing delays, intermittent timeouts or reduced availability due to a hosting-provider network connectivity issue; service was reported restored at 06-01 17:24 UTC.

NeonIssue with project or branch operations in eu-central-1

Neon reported a major outage in eu-central-1 affecting project/branch creation and deletion and connections to new databases from approximately 10:30 UTC on June 01, 2026; existing database connectivity was unaffected. The incident record started at 2026-06-01 11:24 UTC and lasted 52 min, resolving at 2026-06-01 12:16 UTC. Neon stated the issue was fully resolved.

NeonIssue with project or branch operations is us-east-1

Neon reported a major outage affecting project/branch creation and deletion and new database connections in us-east-1; existing database connectivity was unaffected. Recorded from 2026-06-01 10:54 UTC to 2026-06-01 12:08 UTC (1 h 14 min), the incident was fully resolved; Neon reported customer impact between 10:22 UTC and 11:32 UTC.

Red Hat (incl. Quay.io)Quay.io Push/Pull Degraded

JiraFor Jira-software viewIssues and viewBoard are degraded

Jira Software, Jira Service Management, and Jira Work Management had major degradation in Europe, blocking issues, boards, and backlogs and causing transition, comment, and navigation errors. Recorded from 2026-06-01 07:40 UTC to 2026-06-01 13:23 UTC (5 h 42 min), the incident involved caching infrastructure autoscaling failure; Atlassian deployed a fix to prevent recurrence.

Bunny.netIncreased Optimizer Errors

Bunny.net’s Optimizer served 5XX errors in a critical-impact incident that started at 2026-06-01 07:24 UTC and was resolved at 2026-06-01 10:38 UTC, lasting 3 h 14 min. No cause or specific fix was stated.

AAshbyAshby Unavailable

Ashby reported a major outage starting 2026-06-01 06:33 UTC, resolved at 2026-06-01 09:04 UTC; the recorded duration was 2 h 30 min. Its postmortem says the main application was slow and approximately 50% of user actions displayed errors during the affected period. AI features were re-enabled and accumulated work was being processed.

Box[Medium] Issues with Box AI

Box AI and Box Web Application - Box AI experienced a major-impact incident involving errors, failed AI responses or degraded performance. It started at 2026-06-01 00:58 UTC and was resolved at 2026-06-01 02:25 UTC, lasting 1 h 27 min; Box reported remediation and restored full functionality without specifying the cause or fix.

ExpoEAS Outage

Expo reported a major EAS Build, EAS Submit and EAS Workflows outage affecting iOS build and submission jobs and macOS CI/CD workflows, caused by a macOS data center networking outage. It started 2026-05-31 20:38 UTC and was resolved 2026-06-01 03:47 UTC, lasting 7 h 8 min. Network recovery restored services; paid jobs cleared, but free jobs remained backlogged.

LLlamaIndexService Degradation and High Latency

HootsuiteHootsuite login difficulties

Hootsuite reported a critical login outage affecting its Mobile Application and Web Application, potentially preventing dashboard access. The incident started at 2026-05-29 18:23 UTC and was resolved at 2026-05-29 19:05 UTC, lasting 42 min; no cause or specific fix was stated.

Elastic CloudIssue creating new projects in AWS ap-southeast-2

Elastic Cloud reported a major incident preventing creation of Serverless projects in AWS ap-southeast-2. It started at 2026-05-29 18:00 UTC and was resolved at 2026-05-29 18:36 UTC, with a computed duration of 35 min; no cause or specific fix was stated.

GitLabIssues with GitLab Duo in merge requests

GitLab reported a critical incident causing access errors for `@GitLabDuo` mentions in merge requests across GitLab.com, Dedicated, and Self-Managed. It started at 2026-05-29 12:50 UTC and lasted 10 h 51 min, resolving at 2026-05-29 23:41 UTC. A fix was deployed, and GitLab reported no related errors remaining in logs.

PPendoPendo Academy Currently Inaccessible

Pendo Academy was inaccessible in all environments, showing “unauthorized” errors unrelated to user credentials. Pendo rated the incident critical; it started at 2026-05-29 12:40 UTC and was resolved at 2026-05-29 15:32 UTC, lasting 2 h 51 min. Pendo reported access restored across all regions but did not state a cause or fix.

CCoralogixRUM (Real User Monitoring) Data Ingestion Unavailable in EU2

Coralogix reported a major outage affecting RUM data ingestion in EU2, starting at 2026-05-29 10:14 UTC and resolved at 2026-05-29 11:02 UTC (48 min). A fix was implemented, and all previously affected RUM data was available within the system after resolution.

CConfluentElevated error rates and latencies in Azure westus2 region

Confluent Cloud had a major outage with elevated errors and latencies in Azure westus2, linked to Azure network connectivity degradation. The incident ran from 2026-05-29 06:47 UTC to 2026-05-29 21:47 UTC (15 h 0 min), though Confluent reported symptoms beginning around 05:10 UTC. Azure’s degradation was mitigated and Confluent Cloud returned to normal.

SnowflakeAzure - West US 2 (Washington): INC0157956

Snowflake reported a major outage in Azure - West US 2 (Washington): customers could be unable to start, resume, or manage virtual warehouses. Recorded from 2026-05-29 06:47 UTC to 2026-05-29 22:28 UTC (15 h 41 min), it involved a third-party cloud platform issue. The provider implemented a fix; lingering latency and degradation were resolved.

Elastic CloudUpstream Azure Outage Causing Service Degradation

An upstream Azure outage caused major degradation in Azure West US 2 (azure-westus2), limited to westus2-2, including Elastic Serverless projects. Non-high-availability deployments experienced connectivity errors, degraded performance and deployment-operation delays. The incident lasted 2 days 15 h, from 2026-05-29 06:32 UTC to 2026-05-31 21:33 UTC, with remediation and case-by-case support before resolution.

DDevin (Cognition)Devin's machines are failing to start or resume

TTeleportNew Trials Fail to Provision Certificates

CCanvaSome users may have issues accessing Canva

Some Canva users experienced payment issues affecting Billing and subscriptions in an incident rated major. It started at 2026-05-29 01:46 UTC and lasted 26 min, resolving at 2026-05-29 02:12 UTC; Canva reported implementing a fix and restoring normal billing and payment functionality.

BuildkiteDelayed notifications

Buildkite reported a major incident delaying build and job notifications for a subset of customers, affecting email, GitHub commit status, Slack and webhooks. It started at 2026-05-28 20:20 UTC and was resolved at 2026-05-28 21:18 UTC; the computed duration was 57 min. Delayed notifications also delayed downstream CI, merge or deployment workflows for some customers.

FFront[office365] Office channels offline preventing emails being sent or received

Front reported a major O365 outage affecting a subset of customers, with offline channels preventing email sending or receiving. It started at 2026-05-28 18:24 UTC and was resolved at 2026-06-01 23:35 UTC, lasting 4 days 5 h. Front added automatic channel recovery while continuing to investigate remaining sync failures with Microsoft.