Skip to content

Service Status

Current State

✅ Control Center: Available
✅ Data Center: Available
✅ Mobile data connectivity: Available

History

28–29 September 2026 – Data Center

The incident was first reported on 28 September at 08:15 CEST. Initially, no data was available through the user interface or API; data was then restored in stages. Service was fully restored on 29 September at 09:47 CEST, ahead of the estimated time of 12:00 CEST. Based on our current assessment, no data has been lost.

Read the incident report

Read the root cause analysis

21 July-5 August 2026

Some BMA V3 and BMA TLC V3 devices were unable to establish a mobile data connection under certain network conditions. Affected devices appeared offline in Control Center, so monitoring and configuration were unavailable. Communication between BMA TLC and BMC continued to operate normally, and events were cached locally. Maintenance update 2026.2 U2 restored mobile data connectivity and improved resilience through LTE and GSM/EDGE support.

Read the incident report

30 June 2026 · 09:15-11:10 CEST

Multiple devices temporarily lost mobile data connectivity because of a service degradation at the SIM card provider. Affected devices appeared offline in Control Center, so configuration and monitoring were temporarily unavailable. Devices continued to operate normally, communication with traffic light controllers was not impacted, and locally cached events were delivered after connectivity was restored.

Read the root cause analysis

2-3 June 2026 · 05:15-05:27 CEST

Multiple devices temporarily lost mobile data connectivity because of a service degradation at the SIM card provider. Affected devices appeared offline in Control Center, so configuration and monitoring were temporarily unavailable. Devices continued to operate normally, communication with traffic light controllers was not impacted, and locally cached events were delivered after connectivity was restored.

Read the root cause analysis

1 May 2026 · 08:55-10:45 CEST

Control Center generated false device-offline alerts after heartbeat data became stale because queries to Microsoft Service Log Analytics timed out. Devices and the Data Center remained fully operational throughout; the incident affected monitoring and alerting accuracy only.

Read the root cause analysis

29 October 2025 · 17:30–21:30 CET

Control Center became inaccessible due to a Microsoft Azure outage at 17:30 CET. Microsoft mitigated the incident and service was restored around 21:30 CET. Devices and the Data Center remained fully operational throughout.

Last updated: 29 September 2026, 09:47 CEST