Sigfox incident

Incident S1 CORP-41086 on Sigfox network

Notice Resolved View vendor source →

Sigfox experienced a notice incident on March 4, 2024 affecting Uplink and Downlink and 1 more component, lasting 8h 59m. The incident has been resolved; the full update timeline is below.

Started
Mar 04, 2024, 10:32 PM UTC
Resolved
Mar 05, 2024, 07:32 AM UTC
Duration
8h 59m
Detected by Pingoru
Mar 04, 2024, 10:32 PM UTC

Affected components

UplinkDownlinkCallbacks

Update timeline

  1. investigating Mar 04, 2024, 10:32 PM UTC

    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. investigating Mar 04, 2024, 10:51 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 04, 2024, 10:52 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 04, 2024, 11:29 PM UTC

    Incident Severity escalated to S1

  5. monitoring Mar 05, 2024, 12:53 AM UTC

    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.

  6. resolved Mar 05, 2024, 07:32 AM UTC

    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.