Update - Resolution is taking longer than expected. We will continue to open up more SIM ranges for network access. Existing connections will not be affected
May 29, 2024 - 21:09 CEST
Update - There are no updates at this time. We are continuing to open up more SIM ranges for network access in a controlled manner.
May 29, 2024 - 18:49 CEST
Update - We are continuing to open up more SIM ranges for network access in a controlled manner.
May 29, 2024 - 16:18 CEST
Update - We're gradually opening up for more ranges in a controlled manner.
May 29, 2024 - 14:03 CEST
Update - We are still experiencing elevated levels of signaling which is impacting system stability. As a precaution, we will temporarily block all traffic to stabilize the environment. Gradual restoration of traffic will follow to ensure a smooth recovery. We will continue to monitor the situation closely.
May 29, 2024 - 12:08 CEST
Update - We are still working on stabilizing our core
May 29, 2024 - 10:34 CEST
Update - We are experience instability in our core, so opening up for new ranges is taking longer than expected
May 29, 2024 - 09:34 CEST
Update - We are still opening up for devices gradually
May 29, 2024 - 07:09 CEST
Update - Our systems are stable and we are gradually letting devices back online
May 29, 2024 - 05:21 CEST
Identified - Since 2024-05-29 00:15 UTC we have been seeing an increased amount of signaling causing issues with device signaling. This may result in increased or dropped device authentication during this time. We are working on stabilizing our systems.
May 29, 2024 - 04:28 CEST
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
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 ? Partial Outage
90 days ago
99.64 % 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.97 % uptime
Today
API Operational
90 days ago
99.97 % 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.
Past Incidents
May 29, 2024

Unresolved incident: Signalling issues.

May 28, 2024

No incidents reported.

May 27, 2024

No incidents reported.

May 26, 2024

No incidents reported.

May 25, 2024

No incidents reported.

May 24, 2024

No incidents reported.

May 23, 2024

No incidents reported.

May 22, 2024
Completed - We're pleased to announce that our planned maintenance is complete, and all systems are operational. We're closely monitoring system performance to ensure stability. If you experience any issues or have concerns, please don't hesitate to reach out to our support team for assistance.

We appreciate your patience during this time and thank you for your support.

May 22, 13:38 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 22, 09:30 CEST
Scheduled - On May 22nd, our team will be conducting an emergency 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.

May 20, 07:50 CEST
May 21, 2024
Completed - We're pleased to announce that our planned maintenance is complete, and all systems are operational. We're closely monitoring system performance to ensure stability. If you experience any issues or have concerns, please don't hesitate to reach out to our support team for assistance.

We appreciate your patience during this time and thank you for your support.

May 21, 11:56 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 11:00 CEST
Update - We will be undergoing scheduled maintenance during this time.
May 16, 11:54 CEST
Scheduled - On May 21, 2024 at CET 11:00 we will deprecate the offset parameter of the GET /sims API endpoint, which means that requests to the GET /sims endpoint will no longer return count, limit, offset, and total. The response object will instead include a pagination object. If you wish to paginate through the results, you can use the next_page value as a parameter.
We will also be making changes to the GET /sims/find endpoint that will affect the response object returned. With this change, the endpoint will no longer return the values count, limit, offset, and total.

What Do You Need To Do?
From May 15th CET 11:00 until May 21st CET 11:00, you need to review your current API call configurations and update them to reflect the changes.

Detailed guidance and updated API documentation are available in the link here.

May 15, 10:45 CEST
May 20, 2024

No incidents reported.

May 19, 2024

No incidents reported.

May 18, 2024

No incidents reported.

May 17, 2024

No incidents reported.

May 16, 2024

No incidents reported.

May 15, 2024

No incidents reported.