Is UnaBiz down?
Last checked 9m agoNo incidents right now.
UnaBiz is operational right now. Last checked 9m ago; the most recent incident resolved 17d ago.
Real-time UnaBiz status, recent outages, and incident history — pulled directly from UnaBiz's official status page at https://status.unabiz.com every 5 minutes. Pingoru tracks 11 UnaBiz services and has captured 4 incidents in the last 90 days (99.70% uptime). Get email, Slack, Discord, or webhook alerts the moment UnaBiz reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- DownlinkCallbacks
Timeline · 4 updates
- 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
- 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.
- 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.
- 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
Latest: 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
-
- Started Apr 13, 2026, 12:45 AM UTC · Resolved Apr 13, 2026, 12:13 PM UTC · 11h 27m