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 (262-02), Germany
Bouygues Telecom (208-20), France
Vodafone (230-03), Czech Republic
O2 (234-10), UK

NB-IoT
Orange (206-10), Belgium

Oct 19, 2022 - 10:35 CEST
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
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.55 % uptime
Today
SMS Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
App Operational
90 days ago
99.98 % uptime
Today
API Operational
90 days ago
99.98 % 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
TCP timeout time increased Mar 5, 2024 11:00-15:00 CET
On March 5th, our team will be increasing TCP timeouts for parts of the environment. During the maintenance the packet gateways will be taken out of rotation one by one. Some lingering connections might require reconnection when a packet gateway is taken out of rotation.
Posted on Feb 13, 2024 - 11:05 CET
Database maintenance Mar 11, 2024 17:00-19:00 CET
On March 11th, our team will be conducting a routine database version upgrade. During the maintenance process, certain services and features may become unavailable for a short period of time.

Services affected:

- API
- Our platform: *app.onomondo.com*
- Connectors
- Webhooks: delayed processing
- New device authentications

The non-connector traffic from devices that are already online should not be impacted.

Posted on Feb 26, 2024 - 19:46 CET
We are making important changes to the Network Whitelist API and Webhooks requirements that will affect how you generate API calls and IP addresses required for Webhooks.

Starting March 27th, it will be mandatory to specify both a Mobile Country Code (MCC) and a Mobile Network Code (MNC) for all API calls. This update is designed to enhance security and prevent unintentional charges by ensuring connections are made only to specified networks. To improve our service delivery for Webhooks, we're introducing a new IP address for Webhooks: 52.58.186.11/32.

API Action Required: Review and update your API call configurations to comply with the new requirements. Detailed guidance and updated API documentation are available in the link here.

Webhook Action Required: Update your firewall settings to include this new IP address alongside the current ones, ensuring continuous reception of Webhooks without interruption. More documentation can be found here.

Posted on Feb 27, 2024 - 15:59 CET
Past Incidents
Mar 3, 2024

No incidents reported today.

Mar 2, 2024

No incidents reported.

Mar 1, 2024

No incidents reported.

Feb 29, 2024

No incidents reported.

Feb 28, 2024

No incidents reported.

Feb 27, 2024

No incidents reported.

Feb 26, 2024
Resolved - Today's changes have been rolled back and we are fully operational, and all network and platform components are working as intended. The maintenance scheduled for Feb 26, 2024 17:30-19:00 CET has been postponed. We will notify you once this maintenance update has been scheduled again.
Feb 26, 13:20 CET
Update - We are still working to resolve unexpected side effects from today's maintenance. Platform components may still be experiencing performance issues. All network components are fully operational. We will continue to provide updates as we roll back these changes.
Feb 26, 12:56 CET
Identified - We made a change in preparation for today's maintenance, which triggered unexpected side-effects. This may result in some performance issues with Network and Platform components. We're currently rolling back the change and working carefully to resolve the issues.
Feb 26, 12:22 CET
Feb 25, 2024

No incidents reported.

Feb 24, 2024

No incidents reported.

Feb 23, 2024
Resolved - This incident has been resolved the affected caries in the The United States. If you are still experiencing issues related to connectivity in the US, please contact us.
Feb 23, 09:25 CET
Update - The issue is persisting and we are continuing to monitor the situation.
Feb 23, 01:23 CET
Update - We are continuing to monitor for any further issues.
Feb 22, 22:31 CET
Monitoring - The United States is experiencing a nationwide incident, affecting local carriers such as T-Mobile and AT&T. During this time, devices may experience connectivity issues.
We are in regular communication with our partners and keeping a close eye on the situation. If you are experiencing any unexpected problems during this time, please contact us.

Feb 22, 22:30 CET
Feb 22, 2024
Feb 21, 2024

No incidents reported.

Feb 20, 2024

No incidents reported.

Feb 19, 2024
Completed - The scheduled maintenance has been completed.
Feb 19, 21:16 CET
Update - Scheduled maintenance is currently in progress. The initial database backup is still running.
Feb 19, 19:04 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 19, 17:30 CET
Scheduled - On February 19th, our team will be conducting routine database maintenance to enable a future upgrade. During the maintenance period, certain services and features may become unavailable for a short period of time.

Services affected:

- API
- Our platform: *app.onomondo.com*
- Connectors
- Webhooks: delayed processing
- New device authentications

The non-connector traffic from devices that are already online should not be impacted.

Feb 1, 13:40 CET
Feb 18, 2024

No incidents reported.