UnaBiz Outage History

UnaBiz is up right now

UnaBiz had 4 outages in the last 2 years totaling 12h 31m of downtime — averaging 0.2 incidents per month.

There were 4 UnaBiz outages since November 8, 2024 totaling 12h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.unabiz.com

Minor August 17, 2026

Incident S3 CORP-46056 on Sigfox network

Detected by Pingoru
Aug 17, 2026, 07:39 AM UTC
Resolved
Aug 17, 2026, 07:39 AM UTC
Duration
—
Affected: GUI backend.sigfox.comSigfox Services
Timeline · 1 update
  1. resolved Aug 17, 2026, 07:39 AM UTC

    The email service from the backend has been restored. All services should be nominal. We are still closely monitoring the situation and will continue investigating on the root cause. Incident reference CORP-30565 Severity S3 Service Impact Emails from the Sigfox backend were no longer delivered. This also concerned 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

Read the full incident report →

Major April 13, 2026

Incident S2 CORP-45409 on Sigfox Network

Detected by Pingoru
Apr 13, 2026, 12:45 AM UTC
Resolved
Apr 13, 2026, 12:13 PM UTC
Duration
11h 27m
Affected: DownlinkCallbacks
Timeline · 4 updates
  1. 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

  2. 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.

  3. 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.

  4. 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

Read the full incident report →

Major June 18, 2025

Incident S2 CORP-43969 on Sigfox network

Detected by Pingoru
Jun 18, 2025, 08:57 AM UTC
Resolved
Jun 18, 2025, 10:01 AM UTC
Duration
1h 4m
Affected: UplinkAPIDownlinkGUI backend.sigfox.comCallbacks
Timeline · 4 updates
  1. 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

  2. investigating Jun 18, 2025, 09:07 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 18, 2025, 09:08 AM UTC

    Incident is resolved, we are monitoring the situation.

  4. resolved Jun 18, 2025, 10:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 8, 2024

Incident S2 CORP-42784 on Sigfox network

Detected by Pingoru
Nov 08, 2024, 08:49 AM UTC
Resolved
Nov 08, 2024, 08:49 AM UTC
Duration
—
Affected: UplinkDownlinkCallbacks
Timeline · 1 update
  1. 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

Read the full incident report →