Live  /  Cirium  /  Incident

Cirium: Elevated API Errors affecting the Emissions API

Cirium · cirium.comMajor incidentResolved2026-10-06 13:00 UTC
Public — what happened

Summary

Cirium reported a major incident on 6 October 2026 in which its Emissions API endpoints were returning a higher-than-normal number of errors. The company said it began looking into the problem at 12:34 UTC and that its team was working to bring performance back to normal. Cirium did not name a cause in its update, and the incident was marked as resolved at 13:00.

Affected

Cirium Sky™ APIs

As listed on Cirium’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Cirium against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Cirium: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Cirium report →

More from Cirium

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Cirium status & history page.

Related: Cirium status & history. SquidGrid is not affiliated with Cirium.