Live / Secomea / Incident
Secomea: Issue automatically detected on: gm102.secomea.com
Secomea · secomea.comMajor incidentResolved2026-10-21 05:36 UTC
Public — what happened
Summary
Secomea said its monitoring system automatically picked up a problem on the server gm102.secomea.com at 05:12 UTC on 2026-10-21, and rated it as major. The company said its operations staff were notified and began looking into it. Secomea marked the incident resolved at 05:36, and its posted text did not describe a cause or say what was done to fix it.
Affected
GateManager 102
Timeline
- Started — 2026-10-21 05:12 UTC
- Investigating — 2026-10-21 05:12 UTC
- Resolved — 2026-10-21 05:36 UTC · 24 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 Secomea 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 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 44, 2026, our weekly internet health report.