Sigfox Outage History
Sigfox is up right nowPingoru has recorded 48 incidents for Sigfox: 2 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 12 of 720 (2%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 23 of 744 (3%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 508 (0%) |
Incidents, newest first
Minor August 17, 2026 Incident S3 CORP-46056 on Sigfox network 23h 10m GUI backend.sigfox.com, Sigfox Services
Started Aug 17, 2026, 07:39 AM UTC· resolved Aug 18, 2026, 06:50 AM UTC
- resolved Aug 17, 2026, 07:39 AM UTC
Please be advised there is an incident on Sigfox network Analysis of the root cause is still on-going and will be communicated to you as soon as possible. Incident reference CORP-30565 Severity S3 Service Impact Emails from the Sigfox backend are no longer delivered. This also concerns the MFA code for the login session. Start Date and Time 08/16/26 01:00 pm CEST End Date and Time 08/17/26 08:50 am CEST Root cause analysis Analysis on-going
Major April 13, 2026 Incident S2 CORP-45409 on Sigfox Network 11h 27m Downlink, Callbacks
Started Apr 13, 2026, 12:45 AM UTC· resolved Apr 13, 2026, 12:13 PM UTC
- investigating Apr 13, 2026, 12:45 AM UTC
Please be advised there is an incident on Sigfox network Analysis of the root cause is still on-going and will be communicated to you as soon as possible. Incident reference CORP-45409 Severity S2 Service Impact Uplink messages capture - UP Uplink message storage and archiving - UP Uplink callbacks dispatch - FAILING Uplink callbacks retrieval ("callback not sent" status) - WILL BE PARTIALLY AVAILABLE FOLLOWING THE INCIDENT Downlink sequences - FAILING Downlink customer platform call backs - FAILING API service - UP backend.sigfox.com access - UP Start Date and Time 04/13/26 02:09 AM CEST Root cause analysis Analysis on-going
- identified Apr 13, 2026, 01:23 AM UTC
The issue has been identified. Callbacks instances have been restarted following a lock of the services. Impact on callbacks success rate seems low due to retry mechanisms, only delayed dispatching. Downlink sequences have been impacted due to this delay. Backend portal is down but does not impact the connectivity services, messages are still processed.
- monitoring Apr 13, 2026, 04:18 AM UTC
The downlink service and the backend have been restored. All services should be nominal. We are still closely monitoring the situation and will continue investigating on the root cause. A Problem Management process will be held, and an Incident Report will be communicated as soon as we have determined the root cause.
- resolved Apr 13, 2026, 12:13 PM UTC
The incident is confirmed as Resolved after the monitoring period. We will continue investigating and proceed to corrective actions, and build a detailed Incident Report
Major June 18, 2025 Incident S2 CORP-43969 on Sigfox network 1h 4m Uplink, API, Downlink, GUI backend.sigfox.com and 1 more
Started Jun 18, 2025, 08:57 AM UTC· resolved Jun 18, 2025, 10:01 AM UTC
- investigating Jun 18, 2025, 08:57 AM UTC
Please be advised there is an incident on Sigfox network Analysis of the root cause is still on-going and will be communicated to you as soon as possible. Incident reference CORP-43969 Severity S2 Service Impact Uplink messages capture - UP Uplink message storage and archiving - UP Uplink callbacks dispatch - DOWN Uplink callbacks retrieval ("callback not sent" status) - WILL BE PARTIALLY AVAILABLE FOLLOWING THE INCIDENT Downlink sequences - FAILING Downlink customer platform call backs - FAILING API service - FAILING backend.sigfox.com access - FAILING Start Date and Time 06/18/25 10:24 am CEST End Date and Time 06/18/25 10:42 am CEST Root cause analysis Analysis on-going
- investigating Jun 18, 2025, 09:07 AM UTC
We are continuing to investigate this issue.
- monitoring Jun 18, 2025, 09:08 AM UTC
Incident is resolved, we are monitoring the situation.
- resolved Jun 18, 2025, 10:01 AM UTC
This incident has been resolved.
Notice November 8, 2024 Incident S2 CORP-42784 on Sigfox network 4h 30m Uplink, Downlink, Callbacks
Started Nov 08, 2024, 02:20 AM UTC· resolved Nov 08, 2024, 06:50 AM UTC
- resolved Nov 08, 2024, 08:49 AM UTC
Please be advised there is an incident on Sigfox network Analysis of the root cause is still on-going and will be communicated to you as soon as possible. Incident reference CORP-42784 Severity S2 Service Impact Uplink callbacks dispatch - DELAYED Downlink sequences - FAILING Start Date and Time 08/11/2024 03:20 am CET End Date and Time 08/11/2024 7:50 am CET Root cause analysis Analysis on-going