What vendors changed

SingleStoreGCP us-west1 region may be impacted for some customers

SnowflakeAWS - Europe (Zürich): INC0153183

Snowflake reported a major outage in AWS - Europe (Zürich), potentially preventing sign-ins, queries and data management. It started at 2026-03-07 20:05 UTC and was resolved at 2026-03-07 22:20 UTC; the recorded duration was 2 h 14 min. Snowflake identified a third-party cloud platform issue and confirmed service restoration after coordinating a fix with the provider.

SSalesforceCommerce Cloud Regional Service Disruption Managed Runtime: MANAGEDRUNTIMEADMINAPI

SSalesforceService Disruption: MANAGEDRUNTIMEADMINUI

SSalesforceB2 B2 CCommerce Service Disruption: B2 CCore, Cart Service

LLlamaIndexElevated Latency

MMuxvideo clips audio loss

Mux Video - VOD had major audio loss affecting some clips using "basic" or "premium" video_quality, caused by an encoding-change metadata mismatch. It started 2026-03-06 22:57 UTC and was resolved 2026-03-07 01:57 UTC (3 h 0 min); new clips work, but affected clips require re-creation from original assets to restore audio.

Red Hat (incl. Quay.io)Intermittent issues with RHEL 9 and RHUI downloads

GitLabCI/CD pipelines remain stuck in running status

SocketGitHub app reports are stuck not starting

Socket reported a major outage affecting some GitHub app reports not starting, from 2026-03-06 16:15 UTC to 2026-03-07 07:04 UTC, lasting 14 h 48 min. Socket suspected an upstream GitHub webhook problem and advised closing and reopening PRs with stuck checks to trigger another webhook; the incident was resolved.

UpstashRegion ap-northeast-1 outage on Upstash Global

Upstash reported a critical outage affecting Redis Global in Tokyo, Japan (ap-northeast-1), causing elevated latency and connection errors for some databases. The incident ran from 2026-03-06 13:50 UTC to 2026-03-06 14:49 UTC (59 min). A traffic spike increased network utilization and connection load; Upstash mitigated it by scaling regional capacity and redistributing load across additional nodes.

SSemgrepInvestigating issues with pull request checks and repository scans

Semgrep reported a major outage affecting repository scans and GitHub pull request checks: some customers saw scans not starting or checks not appearing. It started at 2026-03-06 12:04 UTC and was resolved at 2026-03-06 16:18 UTC, lasting 4 h 14 min. A fix was rolled out, and scans returned to normal operation.

GitLabGitLab Main Repo Pull Errors

GitLabIntermittent HTTP 50X errors when attempting to access to GitLab.com

BitbucketDisrupted Bitbucket availability

Bitbucket reported a critical outage affecting Website, API, Git via HTTPS, Git via SSH, and Pipelines, leaving affected users unable to access services. It started at 2026-03-06 02:44 UTC and was resolved at 2026-03-06 05:11 UTC, lasting 2 h 27 min. The postmortem attributed the disruption to a hosting-provider regional provisioning API rate limit blocking application workers from handling website traffic.

GitLabCI/CD pipelines intermittently stuck on running status

CCodeiumand WindsurfWe are investigating reports of completions/Tab not working

Codeium reported a major outage affecting Windsurf Tab completions starting 2026-03-05 16:23 UTC, lasting 1 h 22 min. A fix was implemented by 03-05 16:51 UTC, and the incident was resolved at 2026-03-05 17:46 UTC.

SSigma ComputingIssue with Burst email exports are resolved

Sigma Computing reported a major outage of Burst email exports starting 2026-03-05 10:10 UTC, lasting 4 days 7 h until resolution at 2026-03-09 17:31 UTC; standard exports remained operational. Engineers deployed a fix and re-enabled Burst Email Exports at 03-07 01:27 UTC, with no recurring problems observed during subsequent monitoring.

CConfluentMetrics API was experiencing failures from 03:23 UTC to 03:58 UTC

Confluent reported a major Confluent Cloud Metrics API outage, with unavailability from 2026-03-05 03:23 UTC to 2026-03-05 03:58 UTC. The incident record ran from 2026-03-05 04:40 UTC to resolution at 2026-03-05 07:22 UTC (2 h 42 min). Confluent reported mitigation and confirmed normal operation at resolution.

DiscordGuild Unavailability

Some Discord guilds were unavailable in a major-impact incident that started at 2026-03-05 01:37 UTC and was resolved at 2026-03-05 01:58 UTC, lasting 20 min. Discord identified the issue and reported implementing a fix, but did not state a cause.

PPinecone[Serverless][GCP][us-central1] 5xx errors on some read operations for some indexes

Pinecone reported a major incident causing 5xx errors on some read operations for some Serverless indexes in GCP us-central1. It started at 2026-03-04 21:06 UTC and was resolved at 2026-03-04 22:16 UTC, lasting 1 h 10 min. A fix was implemented; affected customers could encounter failed reads during the incident.

GitLabDuo Agentic Chat intermittently fails to respond

CCodeiumand WindsurfWe are investigating reports of completions/Tab not working

Codeium reported a major incident affecting Windsurf Tab completions, starting at 2026-03-04 20:16 UTC and resolved at 2026-03-04 20:54 UTC after 38 min. A fix was implemented at 20:17 UTC; no cause was stated.

AAshbyDelays in generating meeting transcripts

Ashby's AI Notetaker meeting transcript generation was delayed in a major-impact incident starting 2026-03-04 19:59 UTC and resolved at 2026-03-04 20:44 UTC, lasting 44 min. A fix was implemented at 20:31 UTC; no cause was stated.

SSalesforceMule Soft Service Disruption: Exchange

BrexDashboard and mobile app are not loading

Brex’s dashboard and mobile app were not loading during a critical outage that started at 2026-03-04 19:38 UTC and was resolved at 2026-03-04 19:48 UTC, with a reported duration of 9 min. Brex said it identified the issue and applied a fix; no cause was stated.

UUnbounceUnable to Connect Custom Domains

Unbounce reported a major outage preventing custom domain registration, attributed to a Cloudflare outage. It started at 2026-03-04 18:33 UTC and was resolved at 2026-03-05 00:32 UTC, lasting 5 h 59 min; Unbounce said a fix restored registration functionality.

Convexhigh error rates on customer backends

Convex reported a critical incident causing high backend error rates and downtime for some customers, affecting Free & Starter and Live Traffic database, function and Node.js runtimes. It started 2026-03-04 17:28 UTC and lasted 1 h 0 min. Convex remediated the issue and attributed it to a load spike triggering load-shedding and a caching-library panic.

DDevin (Cognition)Sessions slow to start

Windsurfand CCodeiumNetworking issues effecting tab

Windsurf Tab experienced networking issues with major impact starting 2026-03-04 13:49 UTC. The incident lasted 3 h 32 min and was resolved at 2026-03-04 17:22 UTC; no cause or specific fix was stated.

SSalesforceMarketing Cloud Disruption: Advertising Audiences, Analytics Builder, Audience Builder +13 more

GitLabIntermittent HTTP 50X errors when attempting to access to GitLab.com

BrexDashboard Partial Outage

Brex reported a critical Dashboard partial outage starting 2026-03-03 22:14 UTC, lasting 2 h 20 min and resolved at 2026-03-04 00:35 UTC. A fix was in place by 03-03 23:19 UTC; no cause was stated.

LLlamaIndexHigh Job Latency

SSemgrepSemgrep AppSec Platform login page is not working

Semgrep reported a critical AppSec Platform login-page outage affecting Login/SSO; existing sessions remained operative. It started at 2026-03-03 19:23 UTC and was resolved at 2026-03-03 20:05 UTC, lasting 41 min. A fix restored page loading at 19:42 UTC; login and other platform functions were normal at resolution.

SSmartsheetForm Submissions issue

Smartsheet reported a major outage affecting form submissions reaching sheets and some API requests, starting 2026-03-03 17:16 UTC and resolved 2026-03-04 23:42 UTC (30 h 25 min). The vendor cited a code regression, rolled back deployment, and scaled queues; customers were told not to resubmit failed forms because manual replay was planned.

CCodeiumand WindsurfWe are investigating reports of completions/Tab not working

Codeium reported a major outage affecting Windsurf Tab completions, starting at 2026-03-03 17:08 UTC and resolved at 2026-03-03 19:47 UTC, lasting 2 h 38 min. A fix was implemented by 03-03 19:20 UTC; no cause was stated.

GitLabIntermittent 400 errors when logging into GitLab.com

GitLabFlows failing with In Memory Error

OOrbData Processing Delays - Reporting Tools Affected

NeonES-1760167

RenderOhio Services with Disks, Data Persistence failing

Render reported a major outage affecting Ohio application services and data services with persistence due to disk errors. It lasted 19 min, from 2026-03-03 00:41 UTC to 2026-03-03 01:00 UTC; all affected services were migrated to new hosts and were running when resolved.

New RelicData Irregularities

New Relic reported a major degradation starting 2026-03-03 00:19 UTC, resolved at 2026-03-03 02:59 UTC. Some customers in the US and EU regions experienced delayed data in queries, charts, and dashboards, plus delayed or missing alert notifications; later updates identified continuing impact in the US region.

Loopsincreased rate of 500 level responses

LLlamaIndexSystem Outage

MongoDB AtlasMongoDB Atlas: Email notifications may be failing

MongoDB Atlas reported a major-impact MongoDB Cloud incident in which some users may not have received email notifications. It started at 2026-03-02 15:50 UTC and was resolved at 2026-03-02 16:28 UTC, lasting 38 min; MongoDB confirmed email notifications were being sent successfully.