What vendors changed

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.

MezmoUnable to view the logs

Mezmo reported a major outage preventing customers from viewing logs in Log Analysis - Search, Log Analysis - Web App, Search, and Web App. It started at 2025-03-18 13:33 UTC and was resolved at 2025-03-18 14:29 UTC, lasting 56 min; Mezmo implemented a fix and reported processing lag before recent logs became available.

MailgunErrors connecting to smtp.eu.mailgun.org

Mailgun reported a major outage involving connection errors to smtp.eu.mailgun.org, starting 2025-03-17 09:20 UTC and resolved 2025-03-17 19:44 UTC, lasting 10 h 24 min. A mitigation restored SMTP and inbound email processing in the EU region to full working behavior at 15:02 UTC.

PrismaAccelerate intermittent errors provisioning new query engines

FFrontErrors sending and receiving mail for [Office365] channels

Front reported a critical outage causing errors sending and receiving email for Office365 channels, starting 2025-03-14 21:49 UTC and resolved 2025-03-15 00:28 UTC, lasting 2 h 39 min. Front deployed a fix and monitored service before confirming resolution; no specific cause was disclosed.

SSprout SocialSprout Social Loading Issue

Sprout Social reported a major loading issue affecting multiple product areas in the Sprout Social Web Application, starting 2025-03-14 20:23 UTC. A fix was implemented, and the incident was resolved at 2025-03-14 21:24 UTC; the computed duration was 1 h 0 min.

ngrokSites unavailable

IIterableIngestion Delay on Clusters 100 and Above

Iterable reported a critical Global API Ingestion delay on Clusters 100 and above from 2025-03-14 16:56 UTC to 2025-03-14 21:13 UTC, lasting 4 h 16 min. User updates, list uploads, user deletion and event processing were delayed; email sends and journey processing could also be affected. Engineering deployed a fix and confirmed recovery; no data was dropped.

MapboxIncreased latency and errors on Tile APIs

Mapbox reported a critical incident causing increased latency and errors on vector tile endpoints, affecting API and Maps - API. It started at 2025-03-13 12:40 UTC and was resolved at 2025-03-14 12:33 UTC, lasting 23 h 52 min. Mapbox reported successful mitigation at 03-13 21:06 UTC and monitored service stability afterward.

BitbucketBitbucket website and git operations down for some customers

Bitbucket’s major outage affected some Cloud customers’ website, API and git access. It started at 2025-03-11 23:34 UTC and resolved at 2025-03-12 00:28 UTC (53 min); the vendor separately reported customer impact from 11/Mar/25 23:02 UTC to 11/Mar/25 23:59 UTC. Bitbucket monitored an identified fix and said it mitigated the problem.

PyPI (Python Infrastructure)Download file corruption

BBrazeCurrents and CDI latency impacting EU-01 and EU-02

Braze reported major Currents and CDI latency in EU-01 and EU-02 due to an infrastructure problem, starting 2025-03-10 15:47 UTC and resolved at 2025-03-10 22:21 UTC (6 h 33 min). New events and CDI syncs returned to normal, but the Currents event backlog was still being processed; outbound messaging operated normally.

SSprout SocialTwitter/X Outage on March 10th

A critical Twitter/X outage affected Sprout Social’s Smart Inbox, Publishing, Reporting, and Listening, causing missing messages, reply issues, failed posts, and reports not loading. The incident started 2025-03-10 14:26 UTC and was resolved 2025-03-11 15:47 UTC, lasting 25 h 20 min; Twitter/X service was operational by 03-11 08:35 UTC.

PrismaPlatform Console is unavailable

IIterableJourneys are having issues fetching, creating and saving journeys.

Iterable reported a major Global Web Application incident affecting fetching, creating and saving Journeys, causing delays or unexpected behavior. It started at 2025-03-07 09:57 UTC and was resolved at 2025-03-07 18:35 UTC, lasting 8 h 38 min. A fix was deployed by 10:32 UTC, restoring normal Journey function; Iterable later confirmed no further journey-edit errors.

KeeperVault Login errors - resolved

Keeper reported a critical incident involving login errors affecting Keeper Admin Console (US) and Keeper Web Vault (US) in its US Data Center. It started at 2025-03-06 18:23 UTC and was resolved at 2025-03-06 18:25 UTC, lasting 2 min; no cause or specific fix was stated.

AAptibleDelayed Operations

PPandaDocDocuments creation issue

PandaDoc reported a major incident affecting document creation from existing templates and loading template and CLI lists in US & Global, from 2025-03-05 13:53 UTC to 2025-03-05 17:16 UTC (3 h 23 min). Template search was disabled during remediation; all affected services were operational at resolution.

JFrogJFrog Cloud Platform Unavailable (UI only) For Some Customers Due to Login Issues

JFrog reported a critical UI-login outage for some customers in APAC - SouthEast1 (Singapore) - AWS, Europe - West2 (London) - GCP, and US - West (California) - Azure. It started 2025-03-05 13:49 UTC and was resolved at 2025-03-05 14:42 UTC (52 min); JFrog reported implementing a fix.

OpsgenieEU OpsGenie API calls having intermittent routing issues

Opsgenie reported a major degradation: some calls to api.opsgenie.com/eu intermittently returned 404 errors ('no Route matched with those values'). It started at 2025-03-05 06:34 UTC and was resolved at 2025-03-05 07:24 UTC, lasting 50 min; api.eu.opsgenie.com and api.opsgenie.com (without /eu) were unaffected.

RRudderStackData loss of small percentage of warehouse events on free tier

RudderStack reported major-impact loss of a small percentage of free-tier warehouse events from 2025-03-03 09:00 UTC to 2025-03-03 10:00 UTC, lasting 1 h 0 min. The vendor attributed degraded performance, failing health checks and increased service restarts to custom configurations not restored during an internal database migration; it reported implementing a fix and resolved the incident.

FFrontElevated error rates for [office365] channels

Front reported a major Office 365 channel outage from 2025-03-01 21:14 UTC to 2025-03-01 22:32 UTC, lasting 1 h 17 min. An Office365 outage prevented user login and Front from sending and importing messages; Front later reported that Office appeared to have resolved the issue and was processing an import backlog before marking the incident resolved.

DDremioDremio Cloud (US) is inaccessible

Dremio Cloud (US) was inaccessible during a critical outage from 2025-02-28 00:39 UTC to 2025-02-28 08:49 UTC, lasting 8 h 10 min. Dremio attributed the outage to an infrastructure issue affecting core services; all services were restored, with successful recovery of users’ projects reported.

DagsterDagster UI down for multiple users

Dagster reported a major Dagster Cloud UI outage affecting multiple users, starting 2025-02-27 10:52 UTC and resolved at 2025-02-27 11:29 UTC (37 min). A compute log download fault caused web-server timeouts; a fix restored access, while STDOUT/STDERR tabs remained temporarily disabled before later restoration. Agents, runs, and automations were unaffected.

SSambaNovaPlayground and API access temporarily unavailable

RootlySlack Outage (3rd Party) Impacting Rootly Slack App

A critical Slack outage disrupted Rootly Slack App slash commands, messaging and button interactions from 2025-02-26 16:06 UTC until resolution at 2025-02-26 20:42 UTC (4 h 35 min). Rootly modified retry logic; /rootly recovered, with scattered channel-creation delays remaining. Rootly On-Call and Web Platform were unaffected.

UUnbouncePopups and Sticky Bars Not Loading

Unbounce’s Popups and Sticky Bars failed to appear when triggered during a major outage from 2025-02-26 00:40 UTC to 2025-02-26 02:51 UTC (2 h 10 min). Unbounce recommended pausing dependent campaigns; a fix was implemented and the cache cleared, with no further customer action needed after resolution.

GrammarlyGrammarly suggestions aren't available.

Grammarly suggestions were unavailable in a vendor-rated critical outage affecting the Editor, browser extension, and listed mobile and desktop integrations. It started at 2025-02-25 23:00 UTC and was resolved at 2025-02-26 00:00 UTC; the computed duration was 59 min. Grammarly reported implementing a fix and monitoring results, but did not state a cause.

TTwingateTemporary Disruption in DNS Activity Reports

KeeperKeeper vault login errors - resolved

Keeper reported critical US-region login errors affecting Keeper Admin Console and Keeper Web Vault from 2025-02-24 04:48 UTC to 2025-02-24 05:05 UTC (16 min), recommending “work offline.” A backend API and resulting database query triggered high database load; service was resolved, with a permanent fix planned for Monday, Feb 24.

KeeperLogin errors in US region

Keeper reported a major incident involving login errors in the US region, affecting Keeper Admin Console (US) and Keeper Web Vault (US). It started at 2025-02-24 03:54 UTC and was resolved at 2025-02-24 04:28 UTC, lasting 34 min; no cause or specific fix was stated.

SSambaNovaRegional issues accessing UI and API

OOmni AnalyticsIntermittent page errors on embedded dashboards

Omni Analytics reported a major incident in EastUsa: some customers saw error pages on a subset of embedded dashboards from 2025-02-22 00:28 UTC to 2025-02-22 01:50 UTC, lasting 1 h 22 min. A new route was not enabled in embedded contexts; Omni rolled back the change and noted a page refresh might be required.

FFullStoryFullstory unavailable for some users

FullStory reported a major Fullstory Web Application outage affecting some users from 2025-02-20 21:05 UTC to 2025-02-20 21:22 UTC, lasting 17 min. Session capture was unaffected; FullStory rolled back changes it said caused the outage and confirmed normal operations.

TTeleportDegraded Connectivity

CCriblSome Cribl Cloud Control Plane features are degraded

GrammarlyIssues with writing suggestions and generative AI

Grammarly reported a major outage affecting some writing suggestions and generative AI features across Grammarly for Mac, Grammarly for Windows, and Grammarly's Browser Extension. It started at 2025-02-19 17:17 UTC and resolved at 2025-02-19 18:55 UTC, lasting 1 h 37 min. A fix was implemented at 18:34 UTC; no cause was stated.

LLeverData API Unavailable

Lever reported a major Data API outage starting 2025-02-18 22:48 UTC, resolved at 2025-02-22 01:17 UTC (3 days 2 h). A short-term fix left intermittent issues; normal API use was reported on 02-19 17:22 UTC. The postmortem cited database replica issues and Lever Hire inaccessibility for approximately 50% of customers for a few hours.

LLeverIntermittent issues impacting Lever Hire

Lever reported a critical incident affecting Lever Hire and the Lever API, with intermittent 500 errors and higher latency; database unavailability and replica issues made Hire inaccessible for approximately 50% of customers for a few hours. The incident started 2025-02-18 22:20 UTC and was resolved 2025-02-22 01:16 UTC, lasting 3 days 2 h.

LLever500 Error when accessing Lever platform

Lever reported a major outage affecting most North America customers, with 500 errors blocking access to Lever Hire from 2025-02-18 15:12 UTC until 2025-02-18 21:09 UTC (5 h 57 min). Lever implemented a fix; its postmortem cited an unavailable database instance and compounding database-replica issues.

OOmni AnalyticsIntermittent errors

Omni Analytics reported a major incident affecting EastUsa, with intermittent errors in the web application and query execution from 2025-02-14 21:58 UTC to 2025-02-14 22:10 UTC (11 min). A network component upgrade caused intermittent connectivity problems; the change was rolled back and the incident resolved.

LLatticeLattice pages are not loading

Lattice reported a major incident in which the application home page temporarily failed to load. It started at 2025-02-14 17:33 UTC and was resolved at 2025-02-14 17:41 UTC, lasting 8 min; Lattice stated that a fix was implemented.

AAptibleOperations blocked - Route 53 propagation delaysEvent

SingleStoreAWS outage in Stockholm region causing connectivity issuesEvent

PrismaAccelerate elevated 500 responses

PPipedreamElevated Error Rates

Pipedream reported major elevated error rates affecting HTTP and Timer event sources and workflows, including backend components. The incident started at 2025-02-12 04:41 UTC and was resolved at 2025-02-12 06:44 UTC, lasting 2 h 2 min; no cause or specific fix was stated.