Secomea status history
Current state: operational — “All Systems Operational” per https://status.secomea.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Secomea incidents last?
From 55 incidents with a vendor-posted start and resolve time. Longest on record: Datacenter Instability — 7.1 days (2026-06-08 04:00 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (55)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-16 05:17 UTC | Issue automatically detected on: gm102.secomea.com | resolved | major | 5 min |
| 2026-09-16 05:17 UTC | Issue automatically detected on: gm08.secomea.com | resolved | major | 1 min |
| 2026-09-16 05:17 UTC | Issue automatically detected on: gm02.secomea.com | resolved | major | 4 min |
| 2026-09-16 04:56 UTC | Secomea Prime | resolved | none | 5 h 41 min |
| 2026-09-16 02:08 UTC | Issue automatically detected on: gm102.secomea.com | resolved | major | 8 min |
| 2026-09-02 10:27 UTC | Issue automatically detected on: gm02.secomea.com | resolved | major | 10 min |
| 2026-08-31 10:08 UTC | Issue automatically detected on: equans-fr.secomea.com | resolved | minor | 17 min |
| 2026-08-25 08:32 UTC | Issue with SMS from GateManager | resolved | minor | 3 h 05 min |
| 2026-08-12 11:15 UTC | GM52 is not resposive. | resolved | critical | 28 min |
| 2026-08-09 09:07 UTC | Issue automatically detected on: SEC-GM-52 | resolved | major | 3 h 07 min |
| 2026-07-27 06:42 UTC | Issue automatically detected on: SEC-GM-04 | resolved | major | 3 h 02 min |
| 2026-07-26 08:22 UTC | Issue automatically detected on: FTP | resolved | major | 3 d 0 h |
| 2026-07-15 18:37 UTC | GM52 non responsive | resolved | critical | 7 h 28 min |
| 2026-06-08 16:57 UTC | Issue automatically detected on: GateManager 102 | resolved | major | 1 h 56 min |
| 2026-06-08 07:03 UTC | Issue automatically detected on: SEC-GM-14 | resolved | major | 5 h 36 min |
| 2026-06-08 06:10 UTC | Issue automatically detected on: SEC-GM-04 | resolved | major | 6 h 28 min |
| 2026-06-08 05:44 UTC | Issue automatically detected on: GateManager 102 | resolved | major | 6 h 55 min |
| 2026-06-08 05:29 UTC | Issue automatically detected on: SEC-GM-14 | resolved | major | 56 min |
| 2026-06-08 05:27 UTC | Issue automatically detected on: SEC-GM-02 | resolved | major | 7 h 11 min |
| 2026-06-08 05:27 UTC | Issue automatically detected on: SEC-GM-06 | resolved | major | 57 min |
| 2026-06-08 04:00 UTC | Datacenter Instability | resolved | major | 7 d 1 h |
| 2026-06-08 03:26 UTC | Issue automatically detected on: SEC-GM-14 | resolved | major | 2 min |
| 2026-06-08 02:51 UTC | Issue automatically detected on: GateManager 105 | resolved | major | 4 min |
| 2026-06-08 02:45 UTC | Issue automatically detected on: GateManager 102 | resolved | major | 11 min |
| 2026-06-08 02:45 UTC | Issue automatically detected on: SEC-GM-14 | resolved | major | 11 min |
| 2026-06-08 02:28 UTC | Issue automatically detected on: SEC-GM-10 | resolved | major | 28 min |
| 2026-06-08 01:32 UTC | Issue automatically detected on: SEC-GM-04 | resolved | major | 20 min |
| 2026-06-07 18:27 UTC | Issue automatically detected on: SEC-GM-06 | resolved | major | 6 min |
| 2026-06-07 18:20 UTC | Issue automatically detected on: SEC-GM-14 | resolved | major | 14 min |
| 2026-06-07 14:23 UTC | Issue automatically detected on: SEC-GM-06 | resolved | major | 8 min |
| 2026-05-10 22:37 UTC | Issue automatically detected on: SEC-GM-52 | resolved | major | 12 min |
| 2026-05-01 10:40 UTC | Issue automatically detected on: Prime Identity | resolved | none | 8 min |
| 2026-04-23 05:17 UTC | Issue automatically detected on: SEC-GM-14 | resolved | major | 1 min |
| 2026-04-20 09:04 UTC | Prime Performance | resolved | minor | 2 h 27 min |
| 2026-04-15 10:06 UTC | Issue automatically detected on: SEC-GM-08 | resolved | major | 46 min |
| 2026-04-15 09:17 UTC | Issue automatically detected on: GateManager 08 | resolved | major | 22 min |
| 2026-03-26 09:52 UTC | Issue automatically detected on: GateManager 107 | resolved | major | 55 min |
| 2026-03-17 16:11 UTC | Issue automatically detected on: SEC-GM-06 | resolved | major | 2 h 04 min |
| 2026-03-11 15:38 UTC | SMS MFA for US Numbers | resolved | minor | 2 h 51 min |
| 2026-02-24 13:27 UTC | Prime issues - Slow and unstable connection | resolved | minor | 1 h 52 min |
| 2026-02-04 15:38 UTC | Issue automatically detected on: License Portal | resolved | major | 8 min |
| 2026-02-04 15:37 UTC | Issue automatically detected on: GateManager 102 | resolved | major | 8 min |
| 2026-01-29 18:41 UTC | Secomea Prime | resolved | none | 1 h 37 min |
| 2026-01-16 20:46 UTC | Issue automatically detected on: SEC-GM-21 | resolved | major | 1 h 49 min |
| 2025-12-22 08:25 UTC | GateManager 52 currently unavailable | resolved | critical | 58 min |
| 2025-12-22 08:23 UTC | Prime unavailable | resolved | major | 3 d 1 h |
| 2025-12-03 07:58 UTC | License Portal is not generation license | resolved | minor | 6 h 20 min |
| 2025-12-01 14:05 UTC | Issue automatically detected on: License Portal | resolved | major | 20 h 22 min |
| 2025-11-28 11:19 UTC | Issue automatically detected on: License Portal | resolved | major | 31 min |
| 2025-11-27 00:00 UTC | Issue automatically detected on: SEC-GM-12 | resolved | major | 3 min |
| 2025-11-06 10:18 UTC | Issue automatically detected on: SEC-GM-02 | resolved | major | 21 min |
| 2025-10-24 12:32 UTC | Issue automatically detected on: SEC-GM-21 | resolved | major | 28 min |
| 2025-10-22 12:23 UTC | Issue automatically detected on: SEC-GM-06 | resolved | minor | 6 min |
| 2025-10-20 08:44 UTC | General Connection issue | resolved | major | 42 min |
| 2025-10-20 08:32 UTC | Issue automatically detected on: PrimaPower | resolved | none | 54 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Secomea with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"secomea"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}