What vendors changed

Webflow[RESOLVED] Reports of form notification emails not being delivered

Webflow reported a critical outage affecting form notification emails for some customers, starting 2026-02-10 16:11 UTC and resolved 2026-02-11 17:05 UTC (24 h 54 min). An upstream provider issue disrupted email processing; delivery was restored, while form submissions remained successfully processed and accessible via the Forms tab in Site Settings.

RRunwayIssues with Nano Banana Pro generations

Runway reported a major incident with increased failure rates for Nano Banana Pro generations affecting App, Backend, and Public API. It started at 2026-02-10 13:26 UTC and was marked resolved at 2026-02-10 15:46 UTC, lasting 2 h 20 min, although the final update still said investigation was ongoing; no cause or fix was stated.

Red Hat (incl. Quay.io)Hybrid Cloud Console Notifications partial outage

CloudinarySearch API and Media Library Issues

Cloudinary reported a major incident affecting Search API functionality and visibility of newly uploaded assets in Media Library, listing AP, EU and US Admin API components. Symptoms started around 04:30 UTC; the incident record ran from 2026-02-10 08:21 UTC to resolution at 2026-02-10 12:02 UTC (recorded duration: 3 h 41 min).

ConvexSome custom domains not working

Convex reported a major incident affecting many custom domains, which failed with TLS errors due to a misconfiguration; listed components were Free & Starter, Live Traffic - Database Services, and Live Traffic - Function Runtime. It lasted 35 min, from 2026-02-10 01:26 UTC to 2026-02-10 02:01 UTC; all hostnames were reconfigured before resolution.

Red Hat (incl. Quay.io)Quay.io UI Could Not Be Loaded

RRunwayIssues with Nano Banana Pro generations

Runway reported increased errors in Nano Banana Pro generations affecting App, Backend, and Public API, with major impact. The incident started at 2026-02-09 15:39 UTC and was resolved at 2026-02-09 17:57 UTC, lasting 2 h 17 min; no cause or fix was stated.

RRunwayIssues with Gemini 3 Pro (Nano Banana Pro) generations

Runway reported a major Backend incident causing increased error rates for Gemini 3 Pro (Nano Banana Pro) generations. It started at 2026-02-09 10:52 UTC and was resolved at 2026-02-09 12:11 UTC, lasting 1 h 19 min; Runway said it was no longer seeing high error rates for the model.

CockroachDBConnectivity issues to Standard and Basic clusters on AWS

CockroachDB reported a major incident affecting connectivity to Standard and Basic clusters on AWS, starting 2026-02-09 03:04 UTC and resolved at 2026-02-09 15:20 UTC (12 h 16 min). The vendor resolved an internal misconfiguration and reported normal cluster operation at 04:15 UTC, then monitored until resolution.

SSalesforceService Disruption: Core Service

JFrogPartial outage in JFrog Cloud Platform affecting services on Azure US West

JFrog reported a major partial outage affecting Azure US West customers, including Artifactory, Distribution, Pipelines, security services, Webhook and Web UI, caused by Azure infrastructure compute issues. It started at 2026-02-07 08:33 UTC and lasted 6 h 52 min; JFrog reported full restoration at 2026-02-07 15:26 UTC after the upstream outage was resolved.

ConvexConvex Dashboard Availability

Convex reported a major incident causing intermittent Dashboard and CLI errors on Free & Starter, starting 2026-02-07 02:50 UTC and resolved at 2026-02-07 03:06 UTC (15 min). An overloaded database was identified, and Convex reported scaling it; live traffic to Convex deployments was unaffected.

JiraDisrupted JIRA and JSM availability

Jira reported a critical outage affecting Jira and JSM access for some users in us-east-1, with connection failures and unavailable services. It started at 2026-02-06 20:24 UTC and was resolved at 2026-02-07 05:38 UTC, lasting 9 h 13 min; mitigation efforts included initiating a point-in-time recovery.

GrammarlyThe AI-powered Docs is not working as expected

Grammarly reported a critical interruption in Grammarly Editor that prevented access to AI-powered Docs and made some documents inaccessible. It started at 2026-02-06 20:09 UTC and was resolved at 2026-02-06 20:52 UTC, lasting 42 min. A fix was implemented at 20:36 UTC; no cause was stated.

SSalesforceMarketing Cloud Disruption: Marketing Cloud Core Service

GrammarlySome agents may be unavailable or work intermittently

Grammarly reported a major outage affecting Superhuman Go & Agents: Gmail, Outlook, Salesforce, and Jira agents could be unavailable or intermittent in Grammarly, Superhuman, and Coda. It started at 2026-02-06 15:02 UTC and was resolved at 2026-02-06 15:49 UTC, lasting 46 min; the vendor said functionality should be restored.

ContentstackContentstack – Azure NA – CMA Performance and Publishing Degradation

WasabiSystem Errors in US-WEST-1 Region

Wasabi reported a major outage affecting S3 services in US-West-1 (Oregon), disrupting customer access and operations. The incident started at 2026-02-06 08:45 UTC and was resolved at 2026-02-06 12:28 UTC, lasting 3 h 42 min. Wasabi attributed the disruption to a partial datacenter power issue affecting multiple racks.

DDevin (Cognition)Starting Devin sessions degraded

DatadogDelays in Monitor Evaluations

Datadog reported a major incident involving delays in monitor evaluations, starting 2026-02-05 15:24 UTC and resolved at 2026-02-05 17:43 UTC, lasting 2 h 18 min. Customers could experience delayed monitor evaluations across the listed services; Datadog reported full monitor recovery at 17:23 UTC but provided no specific cause or fix.

JiraSome users in us-east-1 region unable to access Jira and JSM.

A critical outage prevented some users in us-east-1 from accessing Jira and JSM, starting 2026-02-05 14:13 UTC and resolving 2026-02-05 21:38 UTC, lasting 7 h 25 min. Jira placed affected sites in maintenance mode to expedite resolution; services returned to normal for all affected customers.

PPendoInvestigating Issues with Guides and Resource Center

A major incident affected Guide statuses and access/editing of Resource Center Guide Modules across AU, EU, JPN, US1 and US environments. It ran from 2026-02-05 12:21 UTC to 2026-02-08 14:57 UTC (3 days 2 h); Pendo rolled out a fix and confirmed resolution after monitoring and reviewing guide statuses.

PlivoOutbound call failures in India region for 160 series

Red Hat (incl. Quay.io)ROSA [Classic & HCP] Y-Stream Upgrades Blocked

PPendoGuides using segments are non-operational in Production and Staging Environments

Pendo reported a critical outage affecting guides using segments in Production and Staging Environments, including Visual Design Studio failures and nonfunctional Resource Center Guide Modules. The incident started at 2026-02-05 01:20 UTC and was resolved at 2026-02-05 04:45 UTC; Pendo reported full restoration and no guide content lost.

RetoolOutage

Retool reported a major partial outage across many product surfaces, recorded as starting and resolving at 2026-02-04 22:46 UTC (computed duration: 0 min). The vendor described the actual impact window as between 12:00pm and 12:08pm UTC, with no expected impact outside that timeframe.

SSalesforceB2 B2 CCommerce Service Disruption: B2 CCore

PrismaAccelerate degraded operation

CCerebrasPartial Service Disruption Qwen 235BEvent

SanityContent Agent and Canvas elevated error rate

Sanity reported a major incident affecting Content Agent and Canvas from 2026-02-04 10:23 UTC to 2026-02-04 11:17 UTC, lasting 53 min; some requests failed, though retries sometimes succeeded. The upstream AI provider implemented a fix and recovered, returning error rates to normal.

Red Hat (incl. Quay.io)Customer Portal Downloads Timeouts

PulumiErrors when creating new Pulumi Neo tasks

Creating new Pulumi Neo tasks produced errors during a major-impact incident starting 2026-02-03 23:26 UTC and resolved at 2026-02-03 23:33 UTC, lasting 6 min. Pulumi identified and rolled back the change that caused the issue.

DDNSimpleDelay in Zone Updates

CConfluentConfluent Cloud Service Outage

Confluent reported a major Confluent Cloud outage starting 2026-02-03 21:33 UTC, resolved 2026-02-04 00:48 UTC (3 h 14 min). A networking configuration change in us-west-2 caused intermittent client connectivity and disruptions affecting Kafka, Flink, Metrics API, Logging, Provisioning, and Authentication; Confluent reverted the change and reported normal operations.

DDrataDrata app not loading correctly

Drata reported a critical outage preventing access across all app functionality, starting 2026-02-03 19:06 UTC and resolved 2026-02-04 00:04 UTC (4 h 57 min). Drata attributed elevated error rates to upstream Cloudflare incidents; functionality was briefly reported restored before errors returned.

SanityContent Agent and Canvas experiencing elevated error rates

Sanity reported a major incident affecting Content Agent and Canvas from 2026-02-03 15:54 UTC to 2026-02-03 16:08 UTC, lasting 14 min. Elevated error rates caused some requests to fail, though retries sometimes succeeded. Sanity identified an upstream AI provider issue; a provider-level fix restored normal error rates.

BBrazeUS02 Dashboard and SDK increased errors

Braze reported a critical incident affecting the US02 Dashboard and SDK Data Collection, with increased errors and possible Dashboard timeouts. The incident started at 2026-02-03 15:41 UTC and was resolved at 2026-02-03 16:02 UTC, lasting 21 min. Services were restored; the SDK automatically retries failed requests, and no action is required.

Jupyter (Anaconda)Anaconda.org performance impacted

Anaconda.org experienced a major performance degradation affecting its database, front-end web service and conda.anaconda.org repository service, from 2026-02-03 13:45 UTC to 2026-02-03 15:05 UTC, lasting 1 h 19 min. A fix was implemented by 14:40 UTC; the incident was resolved, with no cause stated.

GitLabGitLab Duo is unavailable on VSC and Web UI

GitLabDegraded performance for pipelines on gitlab.com

SquarespaceIssues with editing some Squarespace 7.0 sites

Some Squarespace 7.0 sites experienced editing issues in a major-impact Site Editing outage starting 2026-02-03 10:32 UTC and lasting 2 h 27 min. A fix was implemented by 02-03 11:04 UTC, and the incident was resolved at 2026-02-03 13:00 UTC.

SingleStoreAzure VM availability impacted in East US region

SSalesforceService Disruption: Core Service

LLatticeIssue with upstream provider

Lattice reported a major incident affecting email-link redirects and delaying all product notifications via email, MS Teams, or Slack because of an upstream Courier issue. It ran from 2026-02-02 21:34 UTC to 2026-02-02 22:29 UTC (54 min). Courier implemented a fix; redirects recovered and all delayed notifications were delivered, some up to one day late.

StatuspageIssues displaying system metrics

Statuspage reported a critical incident affecting System Metrics displays from 2026-02-02 21:22 UTC to 2026-02-23 10:00 UTC, lasting 20 days 12 h. Underlying chart data could cause display errors on customer Statuspages, prompting Statuspage to disable System Metrics temporarily; a new implementation was enabled for all customers by resolution.

DDrataNotification outage

SafeBase could not send emails, Slack, or MS Teams messages because its third-party notification provider was offline; Drata rated the impact major. The incident started at 2026-02-02 21:10 UTC and was resolved at 2026-02-02 22:05 UTC, lasting 54 min. The provider returned online and normal sending resumed; the vendor said previously unsent messages would be sent.

CCourierCourier Multi Service Outage

CockroachDBAdvanced cluster creation on AWS taking longer than expected

CockroachDB Advanced cluster creation on AWS took longer than usual in a major-impact incident starting 2026-02-02 16:56 UTC and resolved at 2026-02-02 19:46 UTC, lasting 2 h 49 min. CockroachDB deployed and verified a fix, restoring normal cluster creation times.

StatuspageStatuspage API Access Issues

Statuspage reported a major API incident starting 2026-02-02 10:56 UTC, lasting 5 h 44 min until resolution at 2026-02-02 16:40 UTC. A planned old-key cleanup unintentionally disabled new keys, causing authorization errors in some customers’ API integrations; UI and core functions remained available. Customers could generate replacement keys; Statuspage restored affected keys from a point-in-time database backup.

SSalesforceService Disruption: Core Service