What vendors changed

TrelloTrello is slow or unavailable for some users

Trello reported a major degradation affecting API, Trello.com, and web/mobile apps; some users could not view boards or cards. It started at 2025-05-05 15:08 UTC and resolved at 2025-05-05 17:37 UTC (2 h 28 min). An infrastructure management tooling error deployed incorrect database DNS configuration; Trello mitigated the issue and reported no further impact.

CodecovTest Analytics Outage

Codecov reported major Test Analytics downtime affecting Codecov Backend and Codecov Frontend. The incident was recorded from 2025-05-02 00:07 UTC to 2025-05-02 00:39 UTC (32 min), although the vendor said downtime began at 2025-05-01 22:03 UTC. Test Analytics was fully operational at resolution; no cause or fix was specified.

CCerebrasIdentified - Caused by Internal Depencency

SSmartsheetSmartsheet access issues and unexpected errors

Smartsheet reported a major outage causing unexpected errors with login, asset access, navigation, premium apps and API use. The incident ran from 2025-04-30 05:37 UTC to 2025-04-30 08:34 UTC, lasting 2 h 56 min. Engineers identified a load balancer issue and took mitigative action; a fix was implemented and the incident resolved.

FFront2025-04-29 Application unavailable for some customers

Front reported a critical App outage affecting roughly 3% of users, a subset of US-based customers in us-west-1, from 2025-04-29 23:54 UTC to 2025-04-30 05:43 UTC (5 h 49 min). Human error during planned maintenance made one database shard unrecoverable; Front restored it from an up-to-date backup and caught up missed messages.

PulumiHigh error rate running program updates

Pulumi reported a major API incident causing a high error rate running program updates, starting at 2025-04-29 18:41 UTC and resolved at 2025-04-29 19:09 UTC (27 min). A fix was implemented by 19:06 UTC; no cause was stated.

SubstackIncreased error rates

Substack reported a major incident with increased error rates and system-wide performance degradation affecting publications, writer dashboards, Substack.com, the app, and post editor. It started at 2025-04-29 18:15 UTC and was resolved at 2025-04-29 19:16 UTC, lasting 1 h 1 min; full recovery was reported at 18:41 UTC.

LLlamaIndexLLamaIndex Sparse Retrieval Outage

OOmni AnalyticsSlow response times in US Region

Omni Analytics reported a major degradation causing slow responses in the US region (EastUsa), from 2025-04-29 16:39 UTC to 2025-04-29 22:10 UTC, lasting 5 h 30 min. A model validation process repeatedly called an inefficient library function, exhausting memory in some US East infrastructure; the deployed fix removed those calls and was validated to resolve the memory exhaustion.

TrelloTrello is slow or unavailable

Trello reported a critical outage affecting web and mobile apps, starting at 2025-04-25 18:39 UTC and resolved at 2025-04-25 19:12 UTC (computed duration: 32 min). Its postmortem separately identifies service interruptions between 18:18 and 18:33 UTC, caused by reduced capacity after a rollback deployment; scaling up mitigated the issue.

HHexInputs not reacting on some published apps

Hex reported a major Main site incident where inputs were not reacting on some published apps using the pre-run cells in the background feature. It started at 2025-04-25 13:20 UTC and lasted 2 h 55 min, resolving at 2025-04-25 16:15 UTC; a fix was implemented at 04-25 15:35 UTC.

PyPI (Python Infrastructure)PyPI Elevated Error Rates

RRetell AIRetell LLM API incident

CCriblLogin loop when logging into cribl.cloud

PPandaDocDocument search results are not loaded

PandaDoc reported a major outage affecting document search results and the Pipedrive integration, starting 2025-04-23 14:30 UTC and resolved 2025-04-23 22:18 UTC (7 h 48 min). Pipedrive was reported restored at 15:17 UTC, with reconnection advised if issues persisted; document search remained under investigation until full resolution.

IIterableQueries to data stored on C120 cluster are failing

Iterable reported a major C120 outage starting 2025-04-23 06:50 UTC, lasting 40 h 26 min and resolved at 2025-04-24 23:17 UTC. A cluster formation problem caused query failures, campaign impacts and ingestion lag; users triggering journeys via custom events, system events or profile updates did not enter journeys. Engineering restored data and cut over to Cluster 141.

LoopsIncreased 500 status codes

SingleStoreDatabases not reachable from SQL editor

TypeformTypeform OAuth Service degraded - Login with Microsoft Social login

Typeform reported a major OAuth/Login degradation affecting Microsoft Social Login from 2025-04-21 10:30 UTC to 2025-04-21 10:59 UTC, lasting 28 min. Email/password, SSO and Google Social Login were unaffected. Typeform implemented a fix and resolved the incident; no cause was stated.

SSambaNovaAccess to Deepseek, Llama 405B, QwQ,Mistral, and Whisper interrupted

UUnbounceAdding or Editing New Page Level Scripts and Style Sheets Not Working

Unbounce reported a major Web Application incident preventing customers from adding, editing or viewing page-level Scripts and Stylesheets. It started at 2025-04-17 19:03 UTC and was resolved at 2025-04-17 19:07 UTC, lasting 4 min; published pages functioned normally, and Script Manager scripts appeared unaffected.

SSambaNovaTemporary Disruption In Service

CCriblCribl.cloud Authentication Slowness

DDialpadSome customers in Australia and New Zealand may be experiencing issues with calls or meetings

Dialpad reported a major incident affecting calls or meetings for some customers in Australia and New Zealand, including inbound and outbound calls. It started at 2025-04-11 06:26 UTC and was resolved at 2025-04-11 07:11 UTC; the computed duration was 44 min. A fix was implemented, but no cause was stated.

DDopplerExtended Maintenance

Doppler reported critical downtime affecting API (api.doppler.com) and Dashboard (dashboard.doppler.com) due to extended database maintenance. The incident started at 2025-04-11 02:15 UTC and was resolved at 2025-04-11 02:33 UTC, lasting 17 min.

LLlamaIndexIssue creating new index

DDailyElevated SIP/PSTN error rates

WasabiSystem Errors in AP-NORTHEAST-2 Region

Wasabi recorded a major outage in AP-Northeast-2 (Osaka), starting 2025-04-08 14:41 UTC and resolved at 2025-04-08 15:23 UTC (42 min). Its postmortem separately reported service unavailability on 08 April 2025 from 14:13 UTC to approximately 14:39 UTC, caused by an internal routing issue that impaired processing of incoming customer requests.

PyPI (Python Infrastructure)PyPI Simple and JSON API Outage

CCerebrasPartial Service Disruption

CCerebrasService Unavailable

npmIssues publishing and installing packages

CCensusSync might be failing with mismatch errors

Census reported a major Sync Engine incident where some syncs failed with mismatch errors, starting 2025-04-04 22:40 UTC and resolved 2025-04-05 16:23 UTC (17 h 42 min). Census attributed failures to a performance issue, said errors could appear after the problem was resolved, and advised customers to rerun affected syncs.

GrammarlySome Grammarly users may be unable to log in

Some users were unable to log in to Grammarly for Mac during a major-impact outage starting 2025-04-04 10:02 UTC. Grammarly implemented a fix and resolved the incident at 2025-04-04 10:41 UTC; it lasted 39 min.

DDremioUnable to run queries in Dremio Cloud

Dremio Cloud queries could not complete due to a configuration change, in an incident rated major. It started and was resolved at 2025-04-02 18:24 UTC (computed duration: 0 min); Dremio reverted the change and reported queries operational again.

MMetabase Cloudand MetabaseSome Metabase Cloud customers hosted in the EU are reporting their site is down or slowness

Some EU-hosted Metabase Cloud instances were down or slow in a major incident from 2025-04-02 13:00 UTC to 2025-04-02 21:34 UTC, lasting 8 h 33 min. Metabase reported service restored at 13:46 UTC and added monitoring while continuing work on the root-cause fix.

PulumiUpdate logs aren't appearing

Pulumi reported a major API incident in which update logs weren't being saved or displayed, starting at 2025-03-28 09:45 UTC. A fix was being prepared at 03-28 10:50 UTC; the incident was resolved at 2025-03-28 11:29 UTC after 1 h 44 min.

FFireboltUnable to Start Engines in 2.0

Firebolt reported a major outage affecting engine starts in FB 2.0 across all regions, with difficulties reported as of 19:00 UTC on 2025-03-26. The incident was logged from 2025-03-26 19:15 UTC to 2025-03-26 19:18 UTC (3 min); a rollback restored engine starts, with the resolution update stating service was restored at 19:15 UTC.

SSprout SocialSprout Social Outage - March 26th

Sprout Social reported a critical Web Application outage starting 2025-03-26 15:50 UTC, with temporary unavailability, navigation delays and login issues. A fix was implemented at 03-26 16:17 UTC; the incident was resolved at 2025-03-26 19:10 UTC, lasting 3 h 19 min.

FFireboltLogin flow experiencing interruption in some regions

Firebolt reported a major login interruption in some regions due to an Auth0 incident, affecting users with expired tokens and possibly service accounts; V1 authentication was not expected to be affected. The incident started at 2025-03-25 18:21 UTC and was resolved at 2025-03-25 21:57 UTC, lasting 3 h 36 min; uninterrupted authentication was reported restored at 19:20 UTC.

SSambaNovaAuthentication to SambaNova Cloud portal and SambaNova Developer Community Impacted

RootlyIntermittent Latency in Web Application

Rootly’s Web Platform experienced intermittent web application latency with major impact from 2025-03-25 17:42 UTC to 2025-03-25 18:00 UTC, lasting 18 min. Rootly confirmed that on-call and incident creation were working as expected; the issue was resolved without a stated cause or fix.

SubstackErrors loading notes feed

Users could not load the notes feed on Substack.com during a major-impact incident that started at 2025-03-24 23:41 UTC and lasted 28 min, resolving at 2025-03-25 00:09 UTC. Substack reported implementing a fix and monitoring the results before resolution.

BitbucketBitbucket has degraded performance

Bitbucket Cloud reported a major incident involving intermittent errors and degraded performance across API, authentication, Git via HTTPS/SSH, Pipelines, Webhooks and Website. It started at 2025-03-21 20:10 UTC and resolved at 2025-03-22 00:32 UTC, lasting 4 h 21 min. A fix was implemented; no cause was stated.

FFront[us-west-2] [by_company_00008] Customers may experience slowness in app loading

Front reported major app-loading slowness in us-west-2 affecting by_company_00008, starting at 2025-03-19 17:24 UTC and lasting 35 min until resolution at 2025-03-19 17:59 UTC. A fix was implemented by 2025-03-19 17:42 UTC; no cause was stated.

GGrainHigh Rate of Recorder Failure

Grain Recorder experienced a major outage starting 2025-03-19 17:22 UTC, with failures scheduling and booting new recorders; some meetings may not have been captured. Mitigation initially stabilized recording, but errors rose again. The incident was resolved at 2025-05-29 16:24 UTC, with a recorded duration of 70 days 23 h.

FFullStorySlow or failure to load Fullstory

FullStory reported a major degradation causing slow loading or failure to load, affecting its web application and web/native mobile data capture. The incident started at 2025-03-18 20:29 UTC and was resolved at 2025-03-19 00:09 UTC, lasting 3 h 39 min. FullStory rolled back recent changes and implemented a fix; the underlying cause remained under investigation.

New RelicData Irregularities in the EU Region

New Relic reported a major EU-region data-ingest incident starting 2025-03-18 18:50 UTC, resolved at 2025-03-18 19:36 UTC (45 min). Some customers experienced data-sending errors, real-time visibility issues, and delayed or missing alerts; the final update placed customer impact between 18:28 UTC and 18:58 UTC. New Relic reported implementing a fix and subsequently restoring normal operations.

GrammarlyGrammarly is experiencing a service interruption

Grammarly reported a major service interruption affecting suggestions for some users, with components including Writing Suggestions, Generative AI assistance, and Plagiarism Detection listed as affected. It started at 2025-03-18 18:01 UTC and was resolved at 2025-03-18 21:14 UTC, lasting 3 h 12 min. Grammarly reported implementing a fix but did not disclose the root cause.