Live  /  Secomea  /  Incident

Secomea: Secomea Prime

Secomea · secomea.comResolved2026-09-16 07:31 UTC
Public — what happened

Summary

Secomea reported an incident affecting its Secomea Prime service that began on 2026-09-16 at 04:56 UTC. The company said a fix had been put in place and that processing of data was working through a backlog, so users might still notice small delays in the data shown to them. Secomea did not describe a cause, and it said it was watching system performance, with the incident marked resolved at 10:43 the same day.

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 Secomea 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 Secomea: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Secomea report →

More from Secomea

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

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

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