Update - We are continuing to monitor for any further issues.
Dec 02, 2022 - 11:32 CET
Dec 02, 2022 - 11:32 CET
Update - We are continuing to monitor for any further issues.
Oct 28, 2022 - 14:21 CEST
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
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
Degraded Performance
Issues we have identified with specific network operators will be posted here
External Connectivity
Operational
Any issues identified outside of Onomondo's Mobile Core Network
North America
Operational
Europe
Operational
Asia-Pacific
Operational
Central and South America & Caribbean
Operational
Middle East & Africa
Operational
Network
Operational
Onomondo's own Mobile Core Network
SMS
Operational
Webhooks
Operational
App
Operational
API
Operational
Connectors
Operational
TLS
Operational
HTTPS
Operational
AWS IoT Core
Operational
Microsoft Azure DPS (beta)
Operational
MQTT (beta)
Operational
VPN
Operational
IPSec
Operational
OpenVPN
Operational
OpenVPN server to connect directly to devices
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
Increasing our announced BGP range for our GRX subnet
Sep 28, 2023 10:00-13:00 CEST
During the maintenance window we will be increasing our announced subnet range towards our GRX provider.
When we start the change we will redirect the load to other devices before applying the configurations. It will be done in a rolling fashion, as we try to reduce any potential downtime.
Posted on Sep 07, 2023 - 14:55 CEST
When we start the change we will redirect the load to other devices before applying the configurations. It will be done in a rolling fashion, as we try to reduce any potential downtime.
Posted on Sep 07, 2023 - 14:55 CEST