Secomea Outage History

Secomea is up right now

Secomea had 52 outages in the last 2 years totaling 121h 57m of downtime — averaging 2.1 incidents per month.

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

Source: https://status.secomea.com

Major September 22, 2026

Issue automatically detected on: elopak.gatemanager.dk

Detected by Pingoru
Sep 22, 2026, 08:33 AM UTC
Resolved
Sep 22, 2026, 08:58 AM UTC
Duration
24m
Timeline · 2 updates
  1. investigating Sep 22, 2026, 08:33 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 Sep 22, 2026, 08:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 16, 2026

Issue automatically detected on: gm102.secomea.com

Detected by Pingoru
Sep 16, 2026, 05:17 AM UTC
Resolved
Sep 16, 2026, 05:23 AM UTC
Duration
5m
Affected: GateManager 102
Timeline · 2 updates
  1. investigating Sep 16, 2026, 05:17 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 Sep 16, 2026, 05:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 16, 2026

Issue automatically detected on: gm08.secomea.com

Detected by Pingoru
Sep 16, 2026, 05:17 AM UTC
Resolved
Sep 16, 2026, 05:19 AM UTC
Duration
1m
Affected: GateManager 08
Timeline · 2 updates
  1. investigating Sep 16, 2026, 05:17 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 Sep 16, 2026, 05:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 16, 2026

Issue automatically detected on: gm02.secomea.com

Detected by Pingoru
Sep 16, 2026, 05:17 AM UTC
Resolved
Sep 16, 2026, 05:22 AM UTC
Duration
4m
Affected: GateManager 02
Timeline · 2 updates
  1. investigating Sep 16, 2026, 05:17 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 Sep 16, 2026, 05:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 16, 2026

Secomea Prime

Detected by Pingoru
Sep 16, 2026, 04:56 AM UTC
Resolved
Sep 16, 2026, 10:38 AM UTC
Duration
5h 41m
Affected: Prime Platform
Timeline · 3 updates
  1. investigating Sep 16, 2026, 04:56 AM UTC

    We are currently experiencing a delay in the displayed data within Prime. Our engineering team is actively investigating the issue to restore normal data flow as quickly as possible. We will provide further updates here as soon as more information becomes available. We apologize for any inconvenience. Best, Secomea Team.

  2. monitoring Sep 16, 2026, 07:31 AM UTC

    A fix has been implemented, and data processing is now catching up. You may still experience minor delays in displayed data while the remaining backlog is cleared. Our team is actively monitoring system performance to ensure full stability. We apologize for any inconvenience. Best, Secomea Team.

  3. resolved Sep 16, 2026, 10:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 31, 2026

Issue automatically detected on: equans-fr.secomea.com

Detected by Pingoru
Aug 31, 2026, 10:08 AM UTC
Resolved
Aug 31, 2026, 10:26 AM UTC
Duration
17m
Timeline · 2 updates
  1. investigating Aug 31, 2026, 10:08 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 Aug 31, 2026, 10:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 25, 2026

Issue with SMS from GateManager

Detected by Pingoru
Aug 25, 2026, 08:32 AM UTC
Resolved
Aug 25, 2026, 11:37 AM UTC
Duration
3h 5m
Affected: GateManager 00GateManager 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 202GateManager 203
Timeline · 4 updates
  1. investigating Aug 25, 2026, 08:32 AM UTC

    Due to some limitation on our sms provider. There is an issue with sending SMS from the GateManager at the moment. We are already working closely with the provider to resolve this issue SMS might have been lost due to this error

  2. identified Aug 25, 2026, 08:32 AM UTC

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

  3. monitoring Aug 25, 2026, 08:48 AM UTC

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

  4. resolved Aug 25, 2026, 11:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 12, 2026

GM52 is not resposive.

Detected by Pingoru
Aug 12, 2026, 11:15 AM UTC
Resolved
Aug 12, 2026, 11:43 AM UTC
Duration
28m
Affected: GateManager 52
Timeline · 2 updates
  1. investigating Aug 12, 2026, 11:15 AM UTC

    We are currently investigating this issue.

  2. resolved Aug 12, 2026, 11:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 9, 2026

Issue automatically detected on: SEC-GM-52

Detected by Pingoru
Aug 09, 2026, 09:07 AM UTC
Resolved
Aug 09, 2026, 12:14 PM UTC
Duration
3h 7m
Affected: GateManager 52
Timeline · 3 updates
  1. investigating Aug 09, 2026, 09:07 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. investigating Aug 09, 2026, 12:14 PM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 09, 2026, 12:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 27, 2026

Issue automatically detected on: SEC-GM-04

Detected by Pingoru
Jul 27, 2026, 06:42 AM UTC
Resolved
Jul 27, 2026, 09:44 AM UTC
Duration
3h 2m
Affected: GateManager 04
Timeline · 2 updates
  1. investigating Jul 27, 2026, 06:42 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 Jul 27, 2026, 09:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 26, 2026

Issue automatically detected on: FTP

Detected by Pingoru
Jul 26, 2026, 08:22 AM UTC
Resolved
Jul 29, 2026, 08:26 AM UTC
Duration
3d
Affected: FTP
Timeline · 3 updates
  1. investigating Jul 26, 2026, 08:22 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 Jul 26, 2026, 04:04 PM UTC

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

  3. resolved Jul 29, 2026, 08:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 16, 2026

GM52 not responsive

Detected by Pingoru
Jul 16, 2026, 06:42 AM UTC
Resolved
Jul 15, 2026, 06:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 16, 2026, 06:42 AM UTC

    GM52 was unable to be reached.

Read the full incident report →

Critical July 15, 2026

GM52 non responsive

Detected by Pingoru
Jul 15, 2026, 06:37 PM UTC
Resolved
Jul 16, 2026, 02:05 AM UTC
Duration
7h 28m
Affected: GateManager 52
Timeline · 4 updates
  1. investigating Jul 16, 2026, 06:50 AM UTC

    We are currently investigating this issue.

  2. identified Jul 16, 2026, 06:58 AM UTC

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

  3. monitoring Jul 16, 2026, 06:59 AM UTC

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

  4. resolved Jul 16, 2026, 07:00 AM UTC

    This incident has been resolved.

Read the full incident report →

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-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 →

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 →