Vendor Status Watch

← all vendors

Secomea status history

Current state: operational — “All Systems Operational” per https://status.secomea.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

8incidents, last 30 days
13incidents, last 90 days
55incidents on record
Incidents per week, last 12 weeks:

How long do Secomea incidents last?

42 minmedian incident duration55 measured
7.2 h90th percentile1 in 10 ran longer
28 minmedian, major/critical only44 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-16 05:17 UTCIssue automatically detected on: gm102.secomea.comresolvedmajor5 min
2026-09-16 05:17 UTCIssue automatically detected on: gm08.secomea.comresolvedmajor1 min
2026-09-16 05:17 UTCIssue automatically detected on: gm02.secomea.comresolvedmajor4 min
2026-09-16 04:56 UTCSecomea Primeresolvednone5 h 41 min
2026-09-16 02:08 UTCIssue automatically detected on: gm102.secomea.comresolvedmajor8 min
2026-09-02 10:27 UTCIssue automatically detected on: gm02.secomea.comresolvedmajor10 min
2026-08-31 10:08 UTCIssue automatically detected on: equans-fr.secomea.comresolvedminor17 min
2026-08-25 08:32 UTCIssue with SMS from GateManagerresolvedminor3 h 05 min
2026-08-12 11:15 UTCGM52 is not resposive.resolvedcritical28 min
2026-08-09 09:07 UTCIssue automatically detected on: SEC-GM-52resolvedmajor3 h 07 min
2026-07-27 06:42 UTCIssue automatically detected on: SEC-GM-04resolvedmajor3 h 02 min
2026-07-26 08:22 UTCIssue automatically detected on: FTPresolvedmajor3 d 0 h
2026-07-15 18:37 UTCGM52 non responsiveresolvedcritical7 h 28 min
2026-06-08 16:57 UTCIssue automatically detected on: GateManager 102resolvedmajor1 h 56 min
2026-06-08 07:03 UTCIssue automatically detected on: SEC-GM-14resolvedmajor5 h 36 min
2026-06-08 06:10 UTCIssue automatically detected on: SEC-GM-04resolvedmajor6 h 28 min
2026-06-08 05:44 UTCIssue automatically detected on: GateManager 102resolvedmajor6 h 55 min
2026-06-08 05:29 UTCIssue automatically detected on: SEC-GM-14resolvedmajor56 min
2026-06-08 05:27 UTCIssue automatically detected on: SEC-GM-02resolvedmajor7 h 11 min
2026-06-08 05:27 UTCIssue automatically detected on: SEC-GM-06resolvedmajor57 min
2026-06-08 04:00 UTCDatacenter Instabilityresolvedmajor7 d 1 h
2026-06-08 03:26 UTCIssue automatically detected on: SEC-GM-14resolvedmajor2 min
2026-06-08 02:51 UTCIssue automatically detected on: GateManager 105resolvedmajor4 min
2026-06-08 02:45 UTCIssue automatically detected on: GateManager 102resolvedmajor11 min
2026-06-08 02:45 UTCIssue automatically detected on: SEC-GM-14resolvedmajor11 min
2026-06-08 02:28 UTCIssue automatically detected on: SEC-GM-10resolvedmajor28 min
2026-06-08 01:32 UTCIssue automatically detected on: SEC-GM-04resolvedmajor20 min
2026-06-07 18:27 UTCIssue automatically detected on: SEC-GM-06resolvedmajor6 min
2026-06-07 18:20 UTCIssue automatically detected on: SEC-GM-14resolvedmajor14 min
2026-06-07 14:23 UTCIssue automatically detected on: SEC-GM-06resolvedmajor8 min
2026-05-10 22:37 UTCIssue automatically detected on: SEC-GM-52resolvedmajor12 min
2026-05-01 10:40 UTCIssue automatically detected on: Prime Identityresolvednone8 min
2026-04-23 05:17 UTCIssue automatically detected on: SEC-GM-14resolvedmajor1 min
2026-04-20 09:04 UTCPrime Performanceresolvedminor2 h 27 min
2026-04-15 10:06 UTCIssue automatically detected on: SEC-GM-08resolvedmajor46 min
2026-04-15 09:17 UTCIssue automatically detected on: GateManager 08resolvedmajor22 min
2026-03-26 09:52 UTCIssue automatically detected on: GateManager 107resolvedmajor55 min
2026-03-17 16:11 UTCIssue automatically detected on: SEC-GM-06resolvedmajor2 h 04 min
2026-03-11 15:38 UTCSMS MFA for US Numbersresolvedminor2 h 51 min
2026-02-24 13:27 UTCPrime issues - Slow and unstable connectionresolvedminor1 h 52 min
2026-02-04 15:38 UTCIssue automatically detected on: License Portalresolvedmajor8 min
2026-02-04 15:37 UTCIssue automatically detected on: GateManager 102resolvedmajor8 min
2026-01-29 18:41 UTCSecomea Primeresolvednone1 h 37 min
2026-01-16 20:46 UTCIssue automatically detected on: SEC-GM-21resolvedmajor1 h 49 min
2025-12-22 08:25 UTCGateManager 52 currently unavailableresolvedcritical58 min
2025-12-22 08:23 UTCPrime unavailableresolvedmajor3 d 1 h
2025-12-03 07:58 UTCLicense Portal is not generation licenseresolvedminor6 h 20 min
2025-12-01 14:05 UTCIssue automatically detected on: License Portalresolvedmajor20 h 22 min
2025-11-28 11:19 UTCIssue automatically detected on: License Portalresolvedmajor31 min
2025-11-27 00:00 UTCIssue automatically detected on: SEC-GM-12resolvedmajor3 min
2025-11-06 10:18 UTCIssue automatically detected on: SEC-GM-02resolvedmajor21 min
2025-10-24 12:32 UTCIssue automatically detected on: SEC-GM-21resolvedmajor28 min
2025-10-22 12:23 UTCIssue automatically detected on: SEC-GM-06resolvedminor6 min
2025-10-20 08:44 UTCGeneral Connection issueresolvedmajor42 min
2025-10-20 08:32 UTCIssue automatically detected on: PrimaPowerresolvednone54 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
}