Sigfox incident

Incident S2 CORP-32610 on Sigfox network

Major Resolved View vendor source →

Sigfox experienced a major incident on June 16, 2021, lasting 2h 33m. The incident has been resolved; the full update timeline is below.

Started
Jun 16, 2021, 06:32 PM UTC
Resolved
Jun 16, 2021, 09:06 PM UTC
Duration
2h 33m
Detected by Pingoru
Jun 16, 2021, 06:32 PM UTC

Update timeline

  1. investigating Jun 16, 2021, 06:32 PM 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-32610 Severity S2 Service Impact UL sucess rate Downlink sucess rate Some stations communication status are reported as down into the backend Start Date and Time 06/16/21 07:45 pm CEST Root cause analysis Analysis on-going

  2. monitoring Jun 16, 2021, 07:07 PM 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-32610 Severity S2 Service Impact Base stations are connected and transmitting messages. Uplink messages are processed with more latency than usual. Downlink messages still have some delays Start Date and Time 06/16/21 07:45 pm CEST Root cause analysis Analysis on-going

  3. resolved Jun 16, 2021, 09:06 PM UTC

    Please be advised that an incident is RESOLVED. Analysis of the root cause is still on-going and will be communicated to you as soon as possible. Incident reference CORP-32610 Severity S2 Service Impact Uplink message failure Downlink message failure Some stations communication status are reported as down on the backend Start Date and Time 06/16/21 07:45 pm CEST Stop Date and Time 06/16/21 10:45 pm CEST Root cause analysis Analysis on-going