46 Sigfox Operator Risks
By the end of this chapter, you will be able to:
- Evaluate infrastructure dependency risks inherent in the Sigfox operator-only model
- Diagnose coverage degradation by analyzing message success rate trends over time
- Contrast operator-managed and self-deployed network models on cost, control, and risk
- Assess long-term viability by quantifying technology transition and sunset scenarios
- Architect resilient LPWAN deployments using hybrid and modular radio strategies
Key Concepts
- Operator Dependency Risk: Sigfox devices depend on regional SNO infrastructure; operator business failure or coverage withdrawal strands deployed devices.
- Sigfox SA Insolvency: Sigfox parent company filed for insolvency in 2022; Unabiz acquired assets; represents realized example of operator risk for IoT deployments.
- Vendor Lock-in: Sigfox’s proprietary protocol and managed network create dependency on single ecosystem; contrasts with open LoRaWAN deployable on any infrastructure.
- Technology Obsolescence: Risk of LPWAN technology becoming obsolete as competing technologies mature; Sigfox faces pressure from LoRaWAN and NB-IoT ecosystem growth.
- Migration Planning: Risk mitigation through designing modular firmware, selecting multi-protocol hardware, and maintaining technology independence at application layer.
- Business Continuity: Organizational risk assessment for IoT deployments including technology risk, network availability SLAs, and contingency planning.
- Comparative Risk: LoRaWAN mitigates operator risk through private deployment option; NB-IoT relies on cellular carriers with more established business stability.
Sigfox operates as a single global network run by one company, which creates unique risks compared to open technologies like LoRaWAN. If the Sigfox operator has financial difficulties or changes pricing, all devices on the network are affected. This chapter examines the business and technical risks of depending on a proprietary network.
“Here is something scary,” Sammy the Sensor said seriously. “With LoRaWAN, if coverage is weak, you buy a gateway for $500 and fix it yourself. With Sigfox, if coverage is weak, you call the operator and ask politely. They might say, ‘Sorry, not enough subscribers to justify a new base station.’ And you are stuck – forever. You cannot build your own Sigfox base station. It is like renting an apartment versus owning a house.”
“I watched a real case unfold,” Lila the LED recalled. “A city deployed 5,000 water meters on Sigfox. Year one was great – 98% message delivery. By year three, the operator had removed 5 of 8 base stations to cut costs. Message success dropped to 65%. The city was still paying the same subscription fees but getting much worse service. And they could not do anything about it.”
Max the Microcontroller added a historical note. “In 2022, Sigfox SA itself filed for bankruptcy. Imagine having 10,000 devices on a network whose operator goes bankrupt! With LoRaWAN, your private gateways keep working no matter what happens to any company. That is the difference between depending on someone else’s infrastructure and owning your own.”
“My advice for long deployments?” Bella the Battery said. “Design devices with modular radios. Start with Sigfox if coverage is good and you want zero infrastructure hassle. But make sure you can swap to a LoRaWAN module if things go wrong. Monitor your message success rate every month. And for mission-critical applications, consider a hybrid approach – Sigfox for daily reporting, LoRaWAN backup for critical zones.”
46.1 Prerequisites
Required Chapters:
- Sigfox Fundamentals - Core Sigfox concepts
- Sigfox Architecture - Network structure
- Sigfox Review - Overview and quizzes
Technical Background:
- Ultra-narrowband modulation basics
- Global network architecture concepts
- Duty cycle limitations
Estimated Time: 20 minutes
46.2 The Operator-Managed Model
Sigfox’s fundamental architectural choice is the operator-only infrastructure model. Unlike LoRaWAN where users can deploy their own gateways, Sigfox requires all base stations to be operated by licensed Sigfox Network Operators (SNOs).
Key Characteristics of Operator Model:
| Aspect | Sigfox (Operator) | LoRaWAN (Private) |
|---|---|---|
| Base Station Ownership | SNO | User |
| Coverage Control | None | Full |
| CapEx Required | None | Gateway purchases |
| Monthly Fees | Per-device subscription | None (after CapEx) |
| Deployment Timeline | Instant (if coverage exists) | 1-2 weeks per gateway |
| Maintenance | Operator handles | User responsibility |
46.3 Coverage Degradation Risk
The Myth: “Once Sigfox coverage exists in my region, I can rely on it for 10+ year deployments without worrying about network changes.”
The Reality: Sigfox operator economics can cause significant coverage degradation over time, impacting deployed devices without warning.
Real-World Data:
Case Study: European Smart Water Metering (5,000 devices)
Year 1 Performance:
- Message success rate: 98%
- Average RSSI: -105 dBm (strong signal)
- Base stations: 8 covering city
- Cost: EUR5,000/month subscriptions
Year 3 Reality Check:
- Message success rate: 65% (33% DROP!)
- Average RSSI: -125 dBm (weak signal)
- Base stations: 3 remaining (5 decommissioned, 62.5% reduction)
- Cost: Still EUR5,000/month (no refund for degraded service)Why This Happens:
Operator Economic Pressure:
Initial Deployment (Land Grab Phase):
- 8 base stations x EUR10k capex = EUR80k investment
- Maintenance: EUR16k/month operational cost
- Revenue: EUR500/month (100 early adopters x EUR5)
- Burn rate: -EUR15.5k/month (investor funded, unsustainable)
Post-Deployment Optimization (Year 3):
- Remove "redundant" stations: 8 -> 3 (save EUR10k/month maintenance)
- Maintenance cost reduced: EUR16k -> EUR6k/month
- Revenue grew: EUR5k/month (1000 subscribers x EUR5)
- Now profitable: -EUR1k/month (break-even targeted)
- BUT: Coverage quality dropped 33%!Quantified Impact:
- 33% message loss = 33% of water meter readings lost
- No SLA compensation = customers still pay full subscription
- Zero user control = cannot add base stations independently
- Detection lag = 3-6 months before pattern noticed in logs
46.4 Understanding Check: Diagnosing Network Degradation
Scenario: Your city deployed 500 Sigfox parking sensors across downtown. Year 1 performance was excellent: 98% message delivery, averaging 4 messages/hour per sensor.
Year 3 Reality:
- Message success rate dropped to 65% (33% decline)
- Same sensors, same batteries (still 3.4V), same firmware
- Network shows uplink count unchanged (still 4 messages/hour attempted)
- RSSI values in backend logs dropped from -105 dBm to -125 dBm average
Your Investigation:
Battery analysis: Voltage still healthy at 3.4V (started at 3.6V). Transmission power only drops 5-10% with this voltage change. Cannot explain 33% message loss.
Regulatory check: EU 1% duty cycle unchanged since Year 1. Parking sensors use approximately 0.67% duty cycle (4 messages x 6 seconds = 24 seconds per hour out of 3,600 seconds), well under the 1% limit. No enforcement changes.
Protocol verification: Sigfox protocol backward-compatible. If protocol changed, would see 100% failure, not 65% success rate.
Coverage audit: Check Sigfox operator portal. Discover base station count dropped from 8 stations (Year 1) to 3 stations (Year 3).
Root Cause Discovery:
Operator economic pressure:
Year 1: Land-grab phase
- 8 base stations x $10k capex = $80k
- Maintenance: $16k/month
- Subscriber revenue: $500/month
- Burn rate: -$15.5k/month (investor funded)
Year 3: Profitability push
- Removed "redundant" base stations (5 decommissioned)
- Reduced costs: $6k/month maintenance
- Subscriber revenue grew: $5k/month
- Now break-even
- But: Coverage degraded 33%!Key Insight:
Sigfox’s operator-dependent model means you have zero control over infrastructure: - Cannot add base stations yourself - No SLA guarantees (best-effort service) - No visibility into infrastructure changes until messages fail - Economic pressures on operator directly impact your deployment
Comparison: LoRaWAN Private Network
- You deploy 8 gateways (8 x $500 = $4k)
- Year 3 performance degrades? Deploy 2 more gateways ($1k)
- You control: placement, upgrades, monitoring
- No third-party dependency
Mitigation Strategy:
- For mission-critical deployments: hybrid approach (Sigfox + 10 LoRaWAN gateways in critical zones = $5k)
- Design sensors with modular radios (swap Sigfox to LoRaWAN if needed)
- Monitor message success rate monthly (detect degradation early)
The Lesson: “Free” infrastructure (Sigfox model) isn’t free–you pay with control. For 10-year deployments, ownership may be worth 10x upfront cost.
46.5 Sigfox vs LoRaWAN: Operational Control
## Operator Risk Scenarios {#net-sigfox-risk-scenarios}
Scenario 1: Coverage gap discovered
| Approach | Sigfox | LoRaWAN |
|---|---|---|
| Discovery | 30% sensors have poor connectivity | Same |
| Action | Contact operator, request base station | Purchase outdoor gateway (~$1,000) |
| Response | “Business case insufficient, denied” | Install and configure |
| Result | Accept loss OR switch technology | 100% coverage achieved |
| Timeline | Months (if agreed), never (if denied) | 1-2 weeks |
Scenario 2: Scaling from 100 to 10,000 devices
| Aspect | Sigfox | LoRaWAN |
|---|---|---|
| Action | Activate subscriptions | Deploy additional gateways |
| Cost | $59,400/year ongoing | $15,000 one-time |
| Deployment | Instant (if coverage) | 1-2 months |
| Control | None | Full |
Scenario 3: Operator bankruptcy (Sigfox SA 2022)
| Aspect | Sigfox | LoRaWAN |
|---|---|---|
| Impact | Service disruption possible | Zero (private network) |
| User action | Wait for resolution | Continue operating |
| Risk | Stranded assets | None |
46.6 Mitigation Strategies
1. Hybrid Deployment ($5k for 10 gateways) - Sigfox primary coverage in operator-covered zones - LoRaWAN backup in critical zones - Unified application layer aggregates both
2. Monthly Monitoring
- Track message success rates
- Alert on degradation > 5%
- Detect issues before critical impact
3. Modular Radio Design
- Design devices with swappable radios
- Migration path: Sigfox to LoRaWAN ready
- Firmware supports multiple protocols
4. SLA Negotiation
- Request guaranteed coverage SLAs
- Rare, expensive, often refused
- Document all commitments
46.7 Total Cost of Ownership Analysis
Total Cost of Ownership (TCO) analysis reveals how subscription fees compound over time compared to infrastructure investment:
10-Year Deployment (5,000 devices):
Sigfox costs:
Device hardware: 5,000 × $5 = $25,000 (one-time)
Subscriptions: 5,000 × $6/year × 10 = $300,000 (recurring!)
Total: $325,000LoRaWAN costs:
Devices: 5,000 × $15 = $75,000 (one-time)
Gateways: 10 × $1,000 = $10,000 (one-time)
Backhaul: $2,400/year × 10 = $24,000 (recurring)
Server: $500/year × 10 = $5,000 (recurring)
Total: $114,000Cost ratio: \[\frac{\$325{,}000}{\$114{,}000} \approx 2.9:1\]
The subscription model costs ~3x more over 10 years for this fleet size. The crossover point is approximately 1,000-2,000 devices – below this, Sigfox’s simplicity justifies the cost; above it, private infrastructure amortizes rapidly.
10-Year Deployment Comparison (5,000 devices)
| Cost Item | Sigfox | Private LoRaWAN |
|---|---|---|
| Device Hardware | $25,000 | $75,000 |
| Subscriptions | $300,000 | $0 |
| Gateway Infrastructure | $0 | $10,000 |
| Backhaul Connectivity | $0 | $24,000 |
| Network Server | $0 | $5,000 |
| Total 10-Year | $325,000 | $114,000 |
| Control Level | Zero | 100% |
| Coverage Risk | High | None |
Key Insight: “Free” infrastructure (operator-managed model) costs you control. For mission-critical 10-year deployments with thousands of devices, the higher upfront cost of private infrastructure provides better long-term value through operational control and coverage stability.
46.8 Worked Example: Evaluating Operator Risk for a 10-Year Deployment
Scenario: A water utility in southern France is evaluating Sigfox vs private LoRaWAN for 8,000 smart water meters across a mid-sized city (population 120,000). Meters report daily consumption readings (12 bytes) once per hour. The deployment must last 10 years with minimal intervention.
Step 1 – Quantify the operator dependency exposure:
| Risk Factor | Probability (10yr) | Impact | Sigfox Exposure | LoRaWAN Exposure |
|---|---|---|---|---|
| Base station removal (cost optimization) | High (70%) | 20-40% message loss in affected zones | Full – no recourse | None – you own gateways |
| Operator pricing increase (>20%) | Medium (50%) | Budget overrun | Full – captive customer | None – no subscription |
| Operator bankruptcy or acquisition | Medium (40%) | Service disruption 3-12 months | Full – stranded assets | None – private infra |
| Regulatory spectrum change | Low (10%) | Technology migration | Shared risk | Shared risk |
Step 2 – Calculate expected 10-year costs under realistic scenarios:
Optimistic scenario (no operator issues):
| Sigfox | Private LoRaWAN | |
|---|---|---|
| Device hardware (8,000 units) | $40,000 ($5/unit Sigfox module) | $120,000 ($15/unit LoRa module) |
| Subscriptions (10yr) | $480,000 ($6/device/yr) | $0 |
| Gateway infrastructure | $0 | $12,000 (24 gateways x $500) |
| Backhaul (cellular per gateway, 10yr) | $0 | $28,800 ($10/mo x 24 gateways x 10yr) |
| Network server hosting (10yr) | $0 | $6,000 ($50/mo x 10yr) |
| Total | $520,000 | $166,800 |
Realistic scenario (operator removes 40% of base stations in year 4):
| Additional cost | Sigfox | LoRaWAN |
|---|---|---|
| Lost meter readings (30% loss x 4,000 affected meters x 6 years) | $240,000 in unbilled water + leak detection failures | $0 |
| Emergency LoRaWAN overlay deployment | $15,000 (if hybrid fallback added) | N/A |
| Subscriber churn / reputation damage | Unquantifiable | $0 |
Step 3 – Decision framework:
The 10-year TCO difference is roughly 3:1 in favor of private LoRaWAN ($520K vs $167K). Even if LoRaWAN gateway hardware costs doubled and you added a full-time network technician ($50K/year for 10 years = $500K), private LoRaWAN at $667K is still comparable to Sigfox’s $520K but provides full infrastructure control.
The real lesson: Sigfox subscriptions compound linearly with device count and time. At 8,000 devices, the break-even point for private infrastructure investment is approximately 18-24 months of avoided Sigfox subscriptions.
When Sigfox DOES make sense despite operator risk:
- Fewer than 200 devices (subscription cost is low enough that convenience outweighs risk)
- Deployment under 3 years (limited exposure window)
- Area with strong, stable Sigfox coverage AND contractual SLA guarantees
- Proof-of-concept before committing to full infrastructure
46.9 Summary
Sigfox’s operator-managed infrastructure model presents unique risks:
- Zero control over base station deployment, coverage, or network quality
- Coverage degradation can occur when operators optimize infrastructure for profitability
- Economic pressures on operators directly impact your deployment quality
- No SLA guarantees in most standard subscriptions
- Operator bankruptcy risk demonstrated by Sigfox SA filing in 2022
- Mitigation requires hybrid deployments, monthly monitoring, and modular device design
- TCO analysis may favor private infrastructure for long-term, mission-critical deployments
Common Pitfalls
Sigfox’s 2022 insolvency demonstrated that LPWAN operator risk is real, not hypothetical. Organizations that built significant infrastructure on Sigfox faced genuine business disruption. Take operator risk seriously in new LPWAN technology evaluations.
Applications tightly coupled to Sigfox-specific APIs and data formats are difficult to migrate. Design application layers with abstracted connectivity interfaces that can be re-implemented for alternative LPWAN technologies without redesigning business logic.
LoRaWAN being an open standard doesn’t eliminate all vendor risk. Key components (gateway hardware vendors, network server software, cloud integration platforms) still have vendor-specific dependencies. Evaluate the full technology stack when assessing long-term risk.
Technology migration isn’t just “change the radio module.” Field device replacement, firmware redesign, backend reconfiguration, and operator transition all have real costs. Include realistic migration cost estimates when calculating the risk-adjusted value of technology choices.
46.10 What’s Next
Continue your Sigfox learning:
| Order | Chapter | Focus |
|---|---|---|
| Next | Sigfox Use Case Analysis | Evaluate Sigfox suitability for different applications |
| Then | Sigfox Device Management | Firmware updates and downlink challenges |
| Alternative | NB-IoT Fundamentals | Compare with cellular IoT standards |