Outage in Sigfox

Incident S3 CORP-42160

Resolved Minor
July 20, 2024 - Started 5 months ago - Lasted about 5 hours
Official incident page

Need to monitor Sigfox outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Sigfox, and never miss an outage again.
Start Free Trial

Outage Details

Please be advised that 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-42160 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 20/07/24 14:25 PM CET End Date and Time 20/07/24 14:50 PM CET Root cause analysis An incident occured for few minutes on the Sigfox Public Cloud, that delayed UL treatment, and thus may have impacted the downlink success rate during the incident time window. It was caused by a shut down of a VM (Virtual Machine) handlinga part of the live/hot database management. This was likely caused by our Cloud service provider. All services are back to nominal but we are monitoring the situation.
Latest Updates ( sorted recent to last )
RESOLVED 5 months ago - at 07/20/2024 06:02PM

This incident has been resolved.

MONITORING 5 months ago - at 07/20/2024 01:09PM

Please be advised that 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-42160

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
20/07/24 14:25 PM CET

End Date and Time
20/07/24 14:50 PM CET

Root cause analysis
An incident occured for few minutes on the Sigfox Public Cloud, that delayed UL treatment, and thus may have impacted the downlink success rate during the incident time window.
It was caused by a shut down of a VM (Virtual Machine) handlinga part of the live/hot database management. This was likely caused by our Cloud service provider. All services are back to nominal but we are monitoring the situation.

Be the first to know when Sigfox and other third-party services go down

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 3278 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook

Setup in 5 minutes or less

How much time you'll save your team, by having the outages information close to them?

14-day free trial · No credit card required · Cancel anytime