Identified - The issue has been identified and a fix is being implemented.
Nov 17, 2023 - 13:00 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 17, 2023 - 09:29 CET
Update - We are continuing to investigate this issue.
Nov 15, 2023 - 10:07 CET
Investigating - We’re aware of reported SMS instability since October 27, 2023. Our team is actively investigating and has redeployed key components and enhanced monitoring to address this issue.
Nov 14, 2023 - 12:52 CET
Update - We are continuing to monitor for any further issues.
Dec 02, 2022 - 11:32 CET
Update - We are continuing to monitor for any further issues.
Oct 28, 2022 - 14:21 CEST
Monitoring - A couple of networks are closing LTE-M connections after they are created as a way to reject LTE-M. However, this method is causing issues as devices are registering these networks as the last successful connections. Without manual intervention on the network list side, it results in a connection loop where data is not able to be sent.

We have been in touch with them regarding incorrect handling of LTE-M rejections per the standards. We are currently witnessing no action on their part to resolve the issue. Unfortunately, our SLA on LTE for these networks does not extend specifically to LTE-M.
We have also requested that in the signaling that communicates that it is LTE-M instead of LTE. This is something that has been introduced in later standards and would allow us to differentiate between the two technologies and actively block LTE-M. This would prevent the device from attaching to the network and saving these networks as the last known network.

We are now advising all clients who utilize LTE-M in the affected countries to take these networks off their Network List until further notice. We cannot promise a time period for when LTE-M will be accessible on these networks, but we will continue to test LTE-M and monitor the results. Because of the way the network closes a connection, the device will need to be authorized again the next time it attempts to connect. This allows us to block and push the device onto another LTE-M network in the affected country.

Current networks identified:

LTE-M
Vodafone, Germany
Bouygues Telecom, France

NB-IoT
Orange (206-10), Belgium

Oct 19, 2022 - 10:35 CEST
Network Operators ? Operational
External Connectivity ? Operational
North America Operational
Europe Operational
Asia-Pacific Operational
Central and South America & Caribbean Operational
Middle East & Africa Operational
Network ? Operational
90 days ago
99.96 % uptime
Today
SMS Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
99.98 % uptime
Today
App Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Connectors Operational
90 days ago
100.0 % uptime
Today
TLS Operational
90 days ago
100.0 % uptime
Today
HTTPS Operational
90 days ago
100.0 % uptime
Today
AWS IoT Core Operational
90 days ago
100.0 % uptime
Today
Microsoft Azure DPS (beta) Operational
MQTT (beta) Operational
VPN Operational
90 days ago
100.0 % uptime
Today
IPSec Operational
90 days ago
100.0 % uptime
Today
OpenVPN ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Upgrading Amazon Broker Engine Dec 12, 2023 10:00-14:30 CET
On December 12th between 10.00 CET- 14.30 CET we will be performing an upgrade of a core infrastructure service to increase stability and performance going forward.

Delayed messages delivery of Webhooks might occur.
Device connectivity is NOT expected to be affected during this maintenance window.

Posted on Nov 06, 2023 - 17:52 CET
Past Incidents
Dec 2, 2023

No incidents reported today.

Dec 1, 2023

No incidents reported.

Nov 30, 2023

No incidents reported.

Nov 29, 2023
Resolved - Today, from 13:33 UTC until 13:45 UTC a bad deployment caused our traffic monitoring service to show gibberish.
The deployment caused data to be captured in a format our app couldn't parse. As soon as we noticed, we rolled the deployment back which fixed the issue.
We did not leak any data during this incident. The data you saw was still the data from your devices, just unintelligible.
This also didn't affect any data transmission. All device data continued to flow as intended during this time.

Nov 29, 14:30 CET
Nov 28, 2023

No incidents reported.

Nov 27, 2023
Resolved - This incident has been resolved.
Nov 27, 18:10 CET
Update - We have identified the issue and implemented a temporary fix.
We are working on a proper fix, and will roll it once it has been fully verified.

Nov 27, 16:38 CET
Investigating - We are missing packages in Traffic monitor and are currently investigating the issue. Other network traffic is not affected.
Nov 27, 15:08 CET
Nov 26, 2023
Resolved - From 2023-11-26 00:30 UTC until 2023-11-26 12:30 UTC on of our routers started exhibiting erratic behaviour that can have caused packet loss for device traffic.
When we were alerted about the issue we immediately pulled the router out of rotation, and spun up a replacement.

Nov 26, 01:30 CET
Nov 25, 2023
Resolved - all data propagated
Nov 25, 07:01 CET
Monitoring - Wystems have been upgrades. Webhooks are going out, backlog of messages i being worked through.
Nov 25, 05:48 CET
Investigating - All signalling logs have been backfilled. However we have issues service on webhooks and are investigating.
Nov 25, 04:44 CET
Update - signalling logs are being backfilled
Nov 25, 00:55 CET
Update - Signalling data is being backfilled and there is a small delay for messages on webhooks. All other services back to normal.
Nov 24, 19:03 CET
Monitoring - An internal configuration combined with an external network not respecting specific signaling caused a bottleneck which propagated in our system. We’ve rectified the configuration and are currently monitoring while the system recovers.
Nov 24, 15:51 CET
Investigating - Having issues with delays for messages, this is affecting Webhooks, IoT Connectors, and Signalling logs. Some location data got dropped, however other data is currently being backfilled. regular user data is unaffected.
Nov 24, 11:38 CET
Nov 24, 2023
Nov 23, 2023

No incidents reported.

Nov 22, 2023

No incidents reported.

Nov 21, 2023

No incidents reported.

Nov 20, 2023

No incidents reported.

Nov 19, 2023

No incidents reported.

Nov 18, 2023

No incidents reported.