Live / Medius / Incident
Medius: Degraded Performance in Reporting (US)
Medius · mediusflow.comMajor incidentResolved2026-09-14 20:47 UTC
Public — what happened
Summary
Medius reported a major incident affecting its Reporting service in the US region, starting on 2026-09-14 at 20:47 UTC. The company said customers there might see slow responses or timeouts when generating or opening reports. Medius attributed the problem to a confirmed issue with Azure Databricks SQL in the US region and said it was tracking the situation while Databricks worked on a fix. The incident was marked resolved at 21:38, though the last posted status still read as investigating.
Timeline
- Started — 2026-09-14 20:47 UTC
- Resolved — 2026-09-14 21:38 UTC · 52 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Medius against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Medius: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Medius report →
More from Medius
Covered in The Squid’s Ink, Week 39, 2026, our weekly internet health report.