Home
/
Status
/
Service
LPWAN technology for massive IoT connectivity at low cost.
Source
auto
Category
Analytics
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 12m ago
15
Components
0
Active incidents
0
Maintenance
12.5%
90d uptime
Incident S2 CORP-45409 on Sigfox Network
Apr 13, 12:45 AM
Normalized official status-page data for incidents, maintenance, components, and history.
12.5%
Known uptime
8 known history days
15
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
50
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Sigfox Services
Operational
API
Operational
Business Support System (BSS)
Operational
Callbacks
Operational
Downlink
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
1
outage days
6
maintenance days
82
unknown days
Latest outages and degradations detected from the official status page.
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
The situation has been resolved from 3 pm UTC.
This incident has been resolved.
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
This incident has been resolved.
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
The incident is resolved. Monitoring shows nominal services quality since yesterday.
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.
Please be advised there was 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-40345 Severity S3 Service Impact Uplink messages capture - DELAYED Uplink message storage and archiving - UP Uplink callbacks dispatch - DELAYED Downlink sequences - DEGRADED Downlink customer platform call backs - DEGRADED API service - DEGRADED backend.sigfox.com access - DEGRADED Start Date and Time 11/08/23 14:30 PM CET End Date and Time 11/08/23 14:45 PM CET Root cause analysis An incident occured for 15mn on the Sigfox Public Cloud, that delayed UL treatment, and thus may have impacted the downlink success rate during the incident time window. Analysis of the root cause is still on-going.
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has to be extended to 18:00 CEST
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Sigfox status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.unabiz.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 15 of 15 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Operations Support System (OSS) | Operational | Group | Not recorded |
IoT Connectivity Service | Operational | Group | Not recorded |
UnaConnect Singapore | Operational | Group | Not recorded |
UnaConnect Paris | Operational | Group | Not recorded |
API | Operational | Component | Not recorded |
GraphQL V2 Api | Operational | Component | Not recorded |
Network API | Operational | Component | Not recorded |
Uplink | Operational | Component | Not recorded |
Downlink | Operational | Component | Not recorded |
GUI backend.sigfox.com | Operational | Component | Not recorded |
GraphQL V2 Api | Operational | Component | Not recorded |
Network API | Operational | Component | Not recorded |
Callbacks | Operational | Component | Not recorded |
Business Support System (BSS) | Operational | Component | Not recorded |
Sigfox Services | Operational | Component | 6/16/2026 |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Sigfox is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
