Secomea Outage History

Secomea is up right now

Secomea had 42 outages in the last 2 years totaling 123h 46m of downtime — averaging 1.7 incidents per month.

There were 42 Secomea outages since October 6, 2025 totaling 123h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.secomea.com

Major June 8, 2026

Issue automatically detected on: GateManager 102

Detected by Pingoru
Jun 08, 2026, 04:57 PM UTC
Resolved
Jun 08, 2026, 06:54 PM UTC
Duration
1h 56m
Affected: GateManager 102
Timeline · 3 updates
  1. investigating Jun 08, 2026, 04:57 PM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. identified Jun 08, 2026, 05:06 PM UTC

    The issue has been identified and we are working on a solution

  3. resolved Jun 08, 2026, 06:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 8, 2026

Datacenter Instability

Detected by Pingoru
Jun 08, 2026, 07:34 AM UTC
Resolved
Jun 08, 2026, 12:40 PM UTC
Duration
5h 6m
Affected: Prime PlatformGateManager 01GateManager 02GateManager 03GateManager 04GateManager 06GateManager 08GateManager 10GateManager 14GateManager 101GateManager 102GateManager 103GateManager 104GateManager 105GateManager 107GateManager 108GateManager 109GateManager 110GateManager 111GateManager 112GateManager 114GateManager 200GateManager 201
Timeline · 5 updates
  1. investigating Jun 08, 2026, 07:34 AM UTC

    We are currently experiencing technical difficulties at one of our data centers. As a result, several GateManagers are intermittently stopping or failing to respond. Current Status: Issue: GateManagers dropping connection or responding only briefly. Action: Our technical team is actively investigating the root cause. Next Step: We will provide an update as soon as we have more information. We apologize for any inconvenience caused.

  2. investigating Jun 08, 2026, 10:03 AM UTC

    We are continuing to investigate this issue.

  3. identified Jun 08, 2026, 10:50 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Jun 08, 2026, 12:27 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jun 08, 2026, 12:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 8, 2026

Issue automatically detected on: SEC-GM-14

Detected by Pingoru
Jun 08, 2026, 07:03 AM UTC
Resolved
Jun 08, 2026, 12:39 PM UTC
Duration
5h 36m
Affected: GateManager 14
Timeline · 3 updates
  1. investigating Jun 08, 2026, 07:03 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. monitoring Jun 08, 2026, 12:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 08, 2026, 12:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 8, 2026

Issue automatically detected on: SEC-GM-04

Detected by Pingoru
Jun 08, 2026, 06:10 AM UTC
Resolved
Jun 08, 2026, 12:39 PM UTC
Duration
6h 28m
Affected: GateManager 04
Timeline · 3 updates
  1. investigating Jun 08, 2026, 06:10 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. monitoring Jun 08, 2026, 12:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 08, 2026, 12:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 8, 2026

Issue automatically detected on: SEC-GM-02

Detected by Pingoru
Jun 08, 2026, 05:27 AM UTC
Resolved
Jun 08, 2026, 12:39 PM UTC
Duration
7h 11m
Affected: GateManager 02
Timeline · 5 updates
  1. investigating Jun 08, 2026, 05:27 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. monitoring Jun 08, 2026, 06:03 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jun 08, 2026, 06:49 AM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jun 08, 2026, 08:34 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jun 08, 2026, 12:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 8, 2026

Issue automatically detected on: SEC-GM-06

Detected by Pingoru
Jun 08, 2026, 05:27 AM UTC
Resolved
Jun 08, 2026, 06:25 AM UTC
Duration
57m
Affected: GateManager 06
Timeline · 2 updates
  1. investigating Jun 08, 2026, 05:27 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved Jun 08, 2026, 06:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 8, 2026

Issue automatically detected on: GateManager 105

Detected by Pingoru
Jun 08, 2026, 02:51 AM UTC
Resolved
Jun 08, 2026, 02:56 AM UTC
Duration
4m
Affected: GateManager 105
Timeline · 2 updates
  1. investigating Jun 08, 2026, 02:51 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved Jun 08, 2026, 02:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 8, 2026

Issue automatically detected on: SEC-GM-10

Detected by Pingoru
Jun 08, 2026, 02:28 AM UTC
Resolved
Jun 08, 2026, 02:57 AM UTC
Duration
28m
Affected: GateManager 10
Timeline · 2 updates
  1. investigating Jun 08, 2026, 02:28 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved Jun 08, 2026, 02:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 13, 2026

Issue automatically detected on: Prime Identity

Detected by Pingoru
May 13, 2026, 08:47 AM UTC
Resolved
May 13, 2026, 08:59 AM UTC
Duration
12m
Timeline · 2 updates
  1. investigating May 13, 2026, 08:47 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved May 13, 2026, 08:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 10, 2026

Issue automatically detected on: SEC-GM-52

Detected by Pingoru
May 10, 2026, 10:37 PM UTC
Resolved
May 10, 2026, 10:50 PM UTC
Duration
12m
Affected: GateManager 52
Timeline · 2 updates
  1. investigating May 10, 2026, 10:37 PM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved May 10, 2026, 10:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 20, 2026

Prime Performance

Detected by Pingoru
Apr 20, 2026, 09:04 AM UTC
Resolved
Apr 20, 2026, 11:31 AM UTC
Duration
2h 27m
Affected: Prime Platform
Timeline · 3 updates
  1. investigating Apr 20, 2026, 09:04 AM UTC

    We are correctly experience random performance on the Prime platform. There is a chance that you might be disconnected - GateManagers are not affected We are investigating the issue

  2. monitoring Apr 20, 2026, 10:37 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 20, 2026, 11:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 15, 2026

Issue automatically detected on: SEC-GM-08

Detected by Pingoru
Apr 15, 2026, 10:06 AM UTC
Resolved
Apr 15, 2026, 10:53 AM UTC
Duration
46m
Affected: GateManager 08
Timeline · 2 updates
  1. investigating Apr 15, 2026, 10:06 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved Apr 15, 2026, 10:53 AM UTC

    This was a test issue. to find out if we have statuspage delays, from the automated systems

Read the full incident report →

Major April 15, 2026

Issue automatically detected on: GateManager 08

Detected by Pingoru
Apr 15, 2026, 09:17 AM UTC
Resolved
Apr 15, 2026, 09:39 AM UTC
Duration
22m
Affected: GateManager 08
Timeline · 2 updates
  1. investigating Apr 15, 2026, 09:44 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved Apr 15, 2026, 09:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 26, 2026

Issue automatically detected on: GateManager 107

Detected by Pingoru
Mar 26, 2026, 09:52 AM UTC
Resolved
Mar 26, 2026, 10:47 AM UTC
Duration
55m
Affected: GateManager 107
Timeline · 3 updates
  1. investigating Mar 26, 2026, 09:52 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. monitoring Mar 26, 2026, 10:47 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 26, 2026, 10:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 11, 2026

SMS MFA for US Numbers

Detected by Pingoru
Mar 11, 2026, 03:38 PM UTC
Resolved
Mar 11, 2026, 06:30 PM UTC
Duration
2h 51m
Timeline · 3 updates
  1. identified Mar 11, 2026, 03:38 PM UTC

    Impact on US Only: Our provider is currently experiencing issues with SMS delivery in the US, this includes MFA & alerts from GateManager

  2. identified Mar 11, 2026, 03:38 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Mar 12, 2026, 06:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 24, 2026

Prime issues - Slow and unstable connection

Detected by Pingoru
Feb 24, 2026, 01:27 PM UTC
Resolved
Feb 24, 2026, 03:19 PM UTC
Duration
1h 52m
Affected: Prime Platform
Timeline · 4 updates
  1. investigating Feb 24, 2026, 01:27 PM UTC

    We are currently investigating this issue and trying to resolving the issue.

  2. identified Feb 24, 2026, 02:05 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 24, 2026, 02:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Feb 24, 2026, 03:19 PM UTC

    The issue is now resolved and all systems should be operational.

Read the full incident report →

Major February 4, 2026

Issue automatically detected on: License Portal

Detected by Pingoru
Feb 04, 2026, 03:38 PM UTC
Resolved
Feb 04, 2026, 03:46 PM UTC
Duration
8m
Affected: License Portal
Timeline · 2 updates
  1. investigating Feb 04, 2026, 03:38 PM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved Feb 04, 2026, 03:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 29, 2026

Secomea Prime

Detected by Pingoru
Jan 29, 2026, 06:41 PM UTC
Resolved
Jan 29, 2026, 08:19 PM UTC
Duration
1h 37m
Affected: Prime Platform
Timeline · 2 updates
  1. investigating Jan 29, 2026, 06:41 PM UTC

    Secomea Prime is having login and dashboard issues. we are looking in to it We apologize for any inconvenience. Best, Secomea Team.

  2. resolved Jan 29, 2026, 08:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 16, 2026

Issue automatically detected on: SEC-GM-21

Detected by Pingoru
Jan 16, 2026, 08:46 PM UTC
Resolved
Jan 16, 2026, 10:35 PM UTC
Duration
1h 49m
Affected: GateManager 21
Timeline · 2 updates
  1. investigating Jan 16, 2026, 08:46 PM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved Jan 17, 2026, 07:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 22, 2025

GateManager 52 currently unavailable

Detected by Pingoru
Dec 22, 2025, 08:25 AM UTC
Resolved
Dec 22, 2025, 09:23 AM UTC
Duration
58m
Affected: GateManager 52
Timeline · 2 updates
  1. investigating Dec 22, 2025, 08:25 AM UTC

    GateManager 52 is currently unavailable, we are investigating the issue.

  2. resolved Dec 22, 2025, 09:23 AM UTC

    The issue has now been resolved.

Read the full incident report →

Major December 22, 2025

Prime unavailable

Detected by Pingoru
Dec 22, 2025, 08:23 AM UTC
Resolved
Dec 25, 2025, 10:04 AM UTC
Duration
3d 1h
Affected: Prime Platform
Timeline · 3 updates
  1. investigating Dec 22, 2025, 08:23 AM UTC

    The Prime platform is currently unavailable, we are investigating the issue.

  2. monitoring Dec 22, 2025, 08:54 AM UTC

    The issue has been resolved, we are currently monitoring the issue to ensure optimal performance

  3. resolved Dec 25, 2025, 10:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 3, 2025

License Portal is not generation license

Detected by Pingoru
Dec 03, 2025, 07:58 AM UTC
Resolved
Dec 03, 2025, 02:18 PM UTC
Duration
6h 20m
Affected: License Portal
Timeline · 5 updates
  1. investigating Dec 03, 2025, 07:58 AM UTC

    We are currectly having an issue with our license portal not creating any license. We are investigating the issue.

  2. investigating Dec 03, 2025, 09:30 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Dec 03, 2025, 10:42 AM UTC

    The fix has now been implemented. We are continuing to monitor the service.

  4. monitoring Dec 03, 2025, 12:26 PM UTC

    We are still monitoring the performance and stability of the license portal.

  5. resolved Dec 03, 2025, 02:18 PM UTC

    The issue has now been resolved, all systems should be functional.

Read the full incident report →

Major November 27, 2025

Issue automatically detected on: SEC-GM-12

Detected by Pingoru
Nov 27, 2025, 12:00 AM UTC
Resolved
Nov 27, 2025, 12:04 AM UTC
Duration
3m
Affected: GateManager 12
Timeline · 2 updates
  1. investigating Nov 27, 2025, 12:00 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved Nov 27, 2025, 04:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

General Connection issue

Detected by Pingoru
Oct 20, 2025, 08:44 AM UTC
Resolved
Oct 20, 2025, 09:27 AM UTC
Duration
42m
Affected: GateManager 00Prime PlatformGateManager 01GateManager 02GateManager 03GateManager 04GateManager 06GateManager 08GateManager 10GateManager 11GateManager 12GateManager 14GateManager 16GateManager 21GateManager 22GateManager 23GateManager 41GateManager 51GateManager 52GateManager 100GateManager 101GateManager 102GateManager 103GateManager 104GateManager 105GateManager 106GateManager 107GateManager 108GateManager 109GateManager 110GateManager 111GateManager 112GateManager 114GateManager 200GateManager 201GateManager 203
Timeline · 3 updates
  1. identified Oct 20, 2025, 08:44 AM UTC

    Due to an external provider issue. Secomea GateManagers might not be able to be connected to. The problems appear to be related to an issue at Amazon Web Services (AWS), which offers infrastructure that underpins much of the modern internet.

  2. identified Oct 20, 2025, 09:03 AM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Oct 20, 2025, 09:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

Issue automatically detected on: PrimaPower

Detected by Pingoru
Oct 20, 2025, 08:32 AM UTC
Resolved
Oct 20, 2025, 09:27 AM UTC
Duration
54m
Timeline · 2 updates
  1. investigating Oct 20, 2025, 08:32 AM UTC

    This is an automatic message: our system has automatically detected an anomaly, operations personnel have been informed and are looking into the issue.

  2. resolved Oct 20, 2025, 09:27 AM UTC

    This incident has been resolved.

Read the full incident report →