Sigfox incident

Incident S1 CORP-41728 on Sigfox network

Major Resolved View vendor source →

Sigfox experienced a major incident on May 29, 2024 affecting Sigfox Services, lasting 1d 15h. The incident has been resolved; the full update timeline is below.

Started
May 29, 2024, 12:25 AM UTC
Resolved
May 30, 2024, 04:01 PM UTC
Duration
1d 15h
Detected by Pingoru
May 29, 2024, 12:25 AM UTC

Affected components

Sigfox Services

Update timeline

  1. investigating May 29, 2024, 12:25 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-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. identified May 29, 2024, 01:17 AM UTC

    The AWS IOT Callbacks can't be delivered.

  3. identified May 30, 2024, 07:44 AM UTC

    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. identified May 30, 2024, 09:10 AM UTC

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

  5. monitoring May 30, 2024, 12:45 PM UTC

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

  6. resolved May 30, 2024, 04:01 PM UTC

    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