Live  /  Secomea  /  Incident

Secomea: Issue automatically detected on: gm102.secomea.com

Secomea · secomea.comMajor incidentResolved2026-11-03 09:04 UTC
Public — what happened

Summary

Secomea reported a major-severity issue that its monitoring system flagged automatically on the server gm102.secomea.com, starting at 08:58 UTC on 2026-11-03. The company said its operations staff were notified and began looking into it. Secomea marked the incident resolved at 09:04, about six minutes later, and its posted text did not name a cause.

Affected

GateManager 102

As listed on Secomea’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 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 46, 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.