Sigfox 장애 기록

1. 2026년 8월 17일 AM 7:39 UTCresolved

   백엔드의 이메일 서비스는 복원되었습니다. 모든 서비스는 nominal이어야 합니다. 우리는 여전히 상황을 모니터링하고 뿌리 원인에 대한 조사를 계속합니다. Incident 참고 사이트맵 더 보기 사이트맵 서비스 충격 Sigfox 백엔드의 이메일은 더 이상 전달되지 않았습니다. 로그인 세션에 대한 MFA 코드도 우려. 시작일 및 시간 08/16/26 01:00 오후 사이트맵 종료일 및 시간 08/17/26 08:50 오전 시험 뿌리 원인 분석 연구분야

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 4월 13일 AM 12:45 UTCinvestigating

   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

2. 2026년 4월 13일 AM 1:23 UTCidentified

   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.

3. 2026년 4월 13일 AM 4:18 UTCmonitoring

   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.

4. 2026년 4월 13일 PM 12:13 UTCresolved

   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

1. 2025년 6월 18일 AM 8:57 UTCinvestigating

   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

2. 2025년 6월 18일 AM 9:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 6월 18일 AM 9:08 UTCmonitoring

   Incident is resolved, we are monitoring the situation.

4. 2025년 6월 18일 AM 10:01 UTCresolved

   This incident has been resolved.

1. 2024년 11월 8일 AM 8:49 UTCresolved

   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

1. 2024년 7월 20일 PM 1:09 UTCmonitoring

   Please be advised that there was 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-42160 Severity S3 Service Impact Uplink messages capture - DELAYED Uplink message storage and archiving - UP Uplink callbacks dispatch - DELAYED Downlink sequences - DEGRADED Downlink customer platform call backs - DEGRADED API service - DEGRADED backend.sigfox.com access - DEGRADED Start Date and Time 20/07/24 14:25 PM CET End Date and Time 20/07/24 14:50 PM CET Root cause analysis An incident occured for few minutes on the Sigfox Public Cloud, that delayed UL treatment, and thus may have impacted the downlink success rate during the incident time window. It was caused by a shut down of a VM (Virtual Machine) handlinga part of the live/hot database management. This was likely caused by our Cloud service provider. All services are back to nominal but we are monitoring the situation.

2. 2024년 7월 20일 PM 6:02 UTCresolved

   This incident has been resolved.

1. 2024년 5월 29일 AM 12:25 UTCinvestigating

   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-41728 Severity S1 Service Impact AWS IOT callbacks - DOWN Geolocation - DOWN Start Date and Time 24-05-28 7:40 pm CEST Root cause analysis Analysis on-going

2. 2024년 5월 29일 AM 1:17 UTCidentified

   The AWS IOT Callbacks can't be delivered.

3. 2024년 5월 30일 AM 7:44 UTCidentified

   Due to an administrative error at one of our Cloud providers, critical Cloud services have been impacted and Geolocation services are down. The teams are working hard to put the system back on-line, both on UnaBiz and provider side. We expect full restore of the Cloud services before noon today European time, and affected services will then gradually come back online along the day. Sorry again for the inconvenience Best Regards

4. 2024년 5월 30일 AM 9:10 UTCidentified

   Service Impact : AWS IOT callbacks - UP/MONITORING Geolocation - DOWN

5. 2024년 5월 30일 PM 12:45 UTCmonitoring

   Service Impact : AWS IOT callbacks - UP/MONITORING Geolocation - UP/MONITORING

6. 2024년 5월 30일 PM 4:01 UTCresolved

   The incident is now considered resolved, with all the services operational. Service Impact : AWS IOT callbacks - RESOLVED Geolocation - RESOLVED We sincerely apologize for the inconvenience. Unabiz Operations

1. 2024년 3월 5일 PM 1:15 UTCinvestigating

   The situation is degraded again. The delay on message processing is unexpectedly high since 12:16pm CET today : - Global delay in uplink messages processing. - Some downlink may fail as a consequence of the delay on the message processing. We are investigating and will update you as soon as the situation evolves.

2. 2024년 3월 5일 PM 3:07 UTCmonitoring

   The service is back to normal. We are monitoring the situation.

3. 2024년 3월 6일 AM 7:58 UTCresolved

   The incident is resolved. Monitoring shows nominal services quality since yesterday.

1. 2024년 3월 4일 PM 10:32 UTCinvestigating

   Please be advised there is an incident on Sigfox network Incident reference CORP-41086 Severity S1 Service Impact Uplink messages capture - UP Uplink message storage and archiving - UP Uplink callbacks dispatch - UP Downlink sequences - UP Downlink customer platform callbacks - UP API service - UP backend.sigfox.com access - UP Start Date and Time 04/03/24 11:06 pm CET End Date and Time 05/03/24 1:40 am CET Root cause analysis Analysis on-going

2. 2024년 3월 4일 PM 10:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 3월 4일 PM 11:29 UTCinvestigating

   Incident Severity escalated to S1

4. 2024년 3월 5일 AM 12:53 UTCmonitoring

   Root cause is still being analyzed. The main apps have been restarted and the service has been restored. The Uplink Callbacks delayed will be delivered soon.

5. 2024년 3월 5일 AM 7:32 UTCresolved

   Monitoring is stable since 1:40am CET. Global delay in message processing is cleared. Downlink is at nominal state since 6:16am CET. Incident report and root cause will be communicated soon.

1. 2023년 11월 8일 PM 2:00 UTCresolved

   Please be advised there was 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-40345 Severity S3 Service Impact Uplink messages capture - DELAYED Uplink message storage and archiving - UP Uplink callbacks dispatch - DELAYED Downlink sequences - DEGRADED Downlink customer platform call backs - DEGRADED API service - DEGRADED backend.sigfox.com access - DEGRADED Start Date and Time 11/08/23 14:30 PM CET End Date and Time 11/08/23 14:45 PM CET Root cause analysis An incident occured for 15mn on the Sigfox Public Cloud, that delayed UL treatment, and thus may have impacted the downlink success rate during the incident time window. Analysis of the root cause is still on-going.

1. 2023년 9월 26일 AM 10:53 UTCinvestigating

   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-40013 Severity S2 Service Impact Uplink messages capture - DEGRADED Uplink message storage and archiving - UP Uplink callbacks dispatch - UP Downlink sequences - DEGRADED Downlink customer platform call backs - DEGRADED API service - UP backend.sigfox.com access - UP Start Date and Time 09/26/23 10:50 am CET End Date and Time 09/26/23 15:50 am CET Root cause analysis The analysis is done. For details, please contact your Sigfox operator directly.

2. 2023년 9월 26일 PM 1:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 2023년 9월 26일 PM 1:59 UTCresolved

   This incident has been resolved.

1. 2023년 5월 2일 PM 12:27 UTCinvestigating

   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-39012 Severity S2 Service Impact Uplink messages capture - UP Uplink message storage and archiving - UP Uplink callbacks dispatch - UP Uplink callbacks retrieval ("callback not sent" status) - WILL BE PARTIALLY AVAILABLE FOLLOWING THE INCIDENT Downlink sequences - UP Downlink customer platform call backs - UP API service - UP backend.sigfox.com access - UP Start Date and Time 04/02/23 02:13 pm CEST Root cause analysis Analysis on-going

2. 2023년 5월 2일 PM 1:45 UTCmonitoring

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

3. 2023년 5월 2일 PM 4:26 UTCresolved

   The incident was resolved and message processing was back to normal at 3:12 pm CEST.

1. 2023년 4월 16일 AM 10:39 UTCidentified

   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-38898 Severity S3 Service Impact Some OpenVPN stations could not establish a VPN tunnel to the Cloud. Start Date and Time 04/16/23 10:45 am CEST Root cause analysis Root cause has been identified.

2. 2023년 4월 16일 AM 10:39 UTCidentified

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

3. 2023년 4월 18일 PM 2:51 UTCresolved

   This incident has been resolved.

1. 2023년 3월 31일 PM 12:47 UTCinvestigating

   Please be advised there is an incident on the BUY platform (BSS). Analysis of the root cause is still on-going and will be communicated to you as soon as possible. Incident reference CORP-38790 Severity S2 Service Impact BUY purchases - DOWN Start Date and Time 31/03/23 01:40 pm CEST End Date and Time -- Root cause analysis Analysis on-going

2. 2023년 3월 31일 PM 2:10 UTCresolved

   The incident on the BUY platform (BSS) is now resolved. Incident reference CORP-38790 Severity S2 Service Impact BUY purchases - UP Start Date and Time 31/03/23 01:40 pm CEST End Date and Time 31/03/23 02:58pm CEST Root cause analysis BUY platform temporary overload

1. 2023년 3월 8일 AM 10:05 UTCmonitoring

   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-38578 Severity S3 Service Impact Uplink messages capture - UP Uplink message storage and archiving - UP Uplink callbacks dispatch - DELAYED Uplink callbacks retrieval ("callback not sent" status) - IMPACTED/WILL BE PARTIALLY AVAILABLE FOLLOWING THE INCIDENT Downlink sequences - DEGRADED Downlink customer platform call backs - DEGRADED API service - UP backend.sigfox.com access - UP Start Date and Time 08/03/23 10:42 am CET End,Date and Time 08/03/23 10:50 am CET Root cause analysis Analysis on-going

2. 2023년 3월 8일 AM 10:39 UTCresolved

   This incident has been resolved.

1. 2023년 1월 30일 PM 3:13 UTCmonitoring

   Please be advised there was an incident on Sigfox network Incident reference CORP-38275 Severity S3 Service Impact Uplink messages capture - DELAYED (from 3:12PM to 3:17PM CET) Uplink message storage and archiving - UP Uplink callbacks dispatch - DELAYED (from 3:12PM to 3:57PM CET) Downlink sequences - FAILING (from 3:12PM to 3:17PM CET) Downlink customer platform call backs - UP API service - UP backend.sigfox.com access - UP Start Date and Time 30/01/23 03:12 pm CET End Date and Time 30/01/23 03:57 pm CET Root cause analysis Service has been restored following this temporary outage, Issue due to an application communication issue during daily maintenance operation.

2. 2023년 1월 30일 PM 3:54 UTCresolved

   The incident has been resolved and is now closed.

1. 2022년 11월 29일 PM 5:06 UTCidentified

   Please be advised there is an incident on Sigfox backend Incident reference CORP-37882 Severity S3 Service Impact Service Map coverage is not displayed for all countries Start Date and Time 2022-11-28 13:30 UTC End Date and Time 2022-11-29 17:10 UTC Root cause analysis A bug on user rights regarding the Service Map has been introduced with OSS version 11.10.

2. 2022년 11월 29일 PM 5:12 UTCresolved

   This incident has been resolved.

1. 2022년 8월 17일 AM 9:47 UTCinvestigating

   Please be advised there is an on-going incident on Sigfox network. Incident reference CORP-37183 Severity S1 Service Impact Callbacks delay Downlink success rate drop Portal GUI access unavailabilities API error with 500 and 502 codes Registration jobs delay (device registration/transfer, base station registration...) Start/End Date and Time 17/08/22 from 11:23 AM CET to 13:40 PM CET Root cause analysis Database performance drop causing overall service impact.

2. 2022년 8월 17일 AM 10:53 UTCinvestigating

   We are continuing to investigate this issue.

3. 2022년 8월 17일 PM 12:02 UTCmonitoring

   All portals have been restarted and services are back up again. Base stations are progressively unqueuing the stored messages during the incident. We keep monitoring the system closely.

4. 2022년 8월 17일 PM 1:04 UTCresolved

   The incident has been resolved and all services are back to normal.

1. 2022년 7월 5일 PM 10:01 UTCinvestigating

   Please be advised there is an incident on Sigfox network Incident reference CORP-36814 Severity S3 Service Impact Downlink sequences FAILING Start Date and Time 2022/07/05 21:10 UTC End Date and Time 2022/07/05 23:37 UTC Root cause analysis Unexpected amount of simultaneous DL requests caused the database lock due to overload.

2. 2022년 7월 5일 PM 11:58 UTCresolved

   This incident has been resolved.

1. 2022년 7월 2일 PM 10:33 UTCinvestigating

   Dear partners, Please be advised that an incident is OPEN. Analysis of the root cause is still on-going and will be communicated to you as soon as possible. Incident reference CORP-36771 Severity S3 Service Impact Downlink sequences FAILING Start Date and Time 2022/07/02 11:30 pm CET Root cause analysis Analysis on-going

2. 2022년 7월 2일 PM 11:15 UTCinvestigating

   Dear partners, Please be advised that an incident is OPEN. Analysis of the root cause is still on-going and will be communicated to you as soon as possible. Incident reference CORP-36771 Severity S2 Service Impact Downlink sequences FAILING Start Date and Time 2022/07/02 11:30 pm CEST Root cause analysis Analysis on-going

3. 2022년 7월 3일 AM 12:10 UTCinvestigating

   Dear partners, Please be advised that an incident is OPEN. Analysis of the root cause is still on-going and will be communicated to you as soon as possible. Incident reference CORP-36771 Severity S2 Service Impact Uplink messages capture DELAYED Uplink callbacks dispatch DEGRADED Downlink sequences FAILING Start Date and Time 2022/07/02 11:30 pm CEST Root cause analysis Analysis on-going

4. 2022년 7월 3일 AM 3:33 UTCinvestigating

   We are continuing to investigate this issue.

5. 2022년 7월 3일 AM 3:35 UTCresolved

   Dear partners, Please be advised that incident is RESOLVED. Incident reference CORP-36771 Severity S2 Service Impact Uplink messages capture DELAYED Uplink callbacks dispatch DEGRADED Downlink sequences FAILING Start Date and Time 2022/07/02 11:30 pm CEST Stop Date and Time 2022/07/03 05:26 am CEST Root cause analysis Unexpected amount of simultaneous DL requests caused the database lock due to overload.

1. 2022년 6월 2일 AM 9:35 UTCresolved

   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-36531 Severity S3 Service Impact Backend web interface could not be accessed Incoming API requests have been refused Start Date and Time 06/02/22 9:21 am UTC End Date and Time 06/02/22 9:23 am UTC Root cause analysis Analysis on-going