Live / Secomea / Incident
Secomea: Issue automatically detected on: gm102.secomea.com
Secomea · secomea.comMajor incidentResolved2026-11-05 13:43 UTC
Public — what happened
Summary
Secomea said its monitoring system automatically flagged a problem on the server gm102.secomea.com, which it classed as a major issue. The company reported that it began at 09:40 UTC on 2026-11-03 and that its operations staff were alerted and began investigating. Secomea did not name a cause in the text provided, and the incident was marked resolved at 13:43 the same day.
Affected
GateManager 102
Timeline
- Started — 2026-11-03 09:40 UTC
- Investigating — 2026-11-03 09:40 UTC
- Resolved — 2026-11-03 13:43 UTC · 4h 03m 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 46, 2026, our weekly internet health report.