Onomondo logo

Is Onomondo Down?

CommunicationLive status, outages, and incident history

No. Onomondo is up right now.

Every monitored Onomondo system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment Onomondo breaks

Onomondo is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Onomondo status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Onomondo Status Summary

As of 19:39 UTC on 14 November 2026, Onomondo is operational. PulsAPI checked Onomondo's official status page and found 18 of 18 components operational, with no active incidents. The latest incident, "Degraded connectivity for SIMs using IMSI range 20416", was on Nov 8, 2026 and lasted 3h 34m.

Cite as: PulsAPI, “Onomondo status”, checked 14 November 2026, 19:39 UTC. https://www.pulsapi.com/services/onomondo

Onomondo Component Status

The main Onomondo systems on this page. All 18 are operational right now.

18operational
API
Operational
App
Operational
Connectors » AWS IoT Core
Operational

15 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Connectors » HTTPS, Connectors » Microsoft Azure DPS, Connectors » MQTT, Connectors » TLS, External Connectivity » Asia-Pacific, External Connectivity » Central and South America & Caribbean, External Connectivity » Europe, External Connectivity » Middle East & Africa, External Connectivity » North America, Network, Network Operators, SMS, and 3 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Onomondo Outages & Incidents

Incident history from the official Onomondo status page, including resolution updates.

Degraded connectivity for SIMs using IMSI range 20416Resolved Nov 8, 2026 · 3h 34mResolved

This incident has been resolved. Service for SIMs using IMSI range 20416 has remained stable throughout the monitoring period, and devices are connecting and establishing data sessions as normal. The issue was caused by an incident at one of our upstream network partners following planned maintenance on their side. We are following up with the partner to understand the root cause and provide an incident report thereafter. If you still see devices that are unable to connect, please contact our support team. --- [2026-11-08T14:28:39.448+01:00] (monitoring) Service for SIMs using IMSI range 20416 has fully recovered. Network traffic and data sessions are back to normal, stable levels, and devices are able to establish new data sessions as expected. We will continue to monitor network performance. If you still see devices that are unable to connect, we recommend rebooting the device or resetting the modem, and contacting our support team if the issue persists. --- [2026-11-08T13:58:49.156+01:00] (monitoring) Service for SIMs using IMSI range 20416 has largely recovered, and the number of active data sessions is almost back to normal levels. Most affected devices have now reconnected. We are still seeing elevated network activity as remaining devices re-establish their connections, so some devices may take a little longer to come back online. We will continue to monitor and post a further update once we have confirmed full recovery. --- [2026-11-08T13:36:06.844+01:00] (monitoring) Our upstream network partner is implementing a fix, and we are beginning to see service recover for SIMs using IMSI range 20416. Devices are gradually regaining the ability to establish new data sessions. Devices that were unable to connect during the incident may take some time to reconnect. If a device has not reconnected, we recommend rebooting it or resetting the modem. We are continuing to monitor the situation and will post a further update once we have confirmed full recovery. --- [2026-11-08T12:55:17.755+01:00] (identified) We remain in close contact with the partner and will post an update as soon as the fix is in place. --- [2026-11-08T12:56:23.414+01:00] (identified) Our upstream network partner has confirmed they are working on a temporary solution to restore service. Devices on SIMs using IMSI range 20416 may continue to fail to establish new data sessions until then, while active sessions remain unaffected. --- [2026-11-08T12:00:06.727+01:00] (investigating) Since approximately 09:15 CET, devices on SIMs using an IMSI starting with 20416 are failing to establish new data sessions. Devices with an active session are not affected, but devices that disconnect or reboot may be unable to reconnect. SIMs on other IMSI profiles are not affected. The issue has been traced to an incident at one of our upstream network partners following planned maintenance on their side. We are in direct contact with the partner and have escalated the issue. No estimated resolution time is available yet. We are continuing to investigate issues on IMSI range 20416.

Signalling issues on 2G, 3G and 4GResolved Nov 3, 2026 · 1h 44mResolved

All systems are now performing nominally. We have seen a full recovery in signalling and authentication rates. If you are still experiencing issues please contact our support team via support@onomondo.com. Thank you again for your patience. --- [2026-11-03T13:43:53.562+01:00] (monitoring) Our incident response team has identified the issue affecting signalling and authentication on IMSI range 23450; having applied a fix to this problem we are now observing rapid recovery and SIMs successfully re-authenticating.  We are continuing to monitor the situation and will provide further updates shortly. If you are still experiencing issues, please reach out to our Technical Support Team via support@onomondo.com We apologise for the inconvenience and thank you for your patience. --- [2026-11-03T13:01:12.818+01:00] (identified) Our incident response team are continuing to investigate.  We have successfully identified a root cause affecting IMSI range 20416.  We are observing improvements for both signalling and authentications on this range and devices should begin recovering shortly.  We are continuing to investigate issues on IMSI range 23450 and expect to provide an update shortly. --- [2026-11-03T12:30:49.518+01:00] (investigating) We are currently observing abnormal behaviour in all signalling and authentication of devices on our network. We are actively investigating the root cause and we will provide updates as soon as possible.

No traffic shown in Traffic MonitorResolved Nov 3, 2026 · 37 minResolved

This incident has been resolved. --- [2026-11-03T11:18:10.002+01:00] (monitoring) An issue in our rate limiter was identified and has been fixed. Monitoring --- [2026-11-03T11:05:54.813+01:00] (investigating) We are currently experiencing issues with Traffic Monitor in the app. We are investigating.

Upcoming maintenance

Announced by Onomondo. Planned work, not an outage.

Core Network MaintenanceScheduled for Nov 18, 2026 · 7h 0mScheduled

We are scheduling general system maintenance for our core network. Maintenance is planned for Nov 18, 2026, starting at 9:30 UTC, with an expected duration of up to three hours. During this time, we will be updating services of our core network responsible for authentication on 2G, 3G, 4G LTE, LTE-M, and NB-IoT. No service disruptions are expected. Customers should not experience authentication rejections due to this maintenance.

GRX link routing updateScheduled for Nov 19, 2026 · 1h 0mScheduled

We will be performing upgrades to our GRX links in cooperation with our GRX provider. Temporary and minimal network instability may occur during this work. We will monitor the environment closely throughout the maintenance window.

Onomondo Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Onomondo incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Onomondo Outage Reports

Problems reported by engineers using Onomondo. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Onomondo problems reported yet.

Something wrong with Onomondo on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Onomondo

Onomondo's status page at status.onomondo.com lists 18 components, such as API, App and AWS IoT Core. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Onomondo's side or yours.

Onomondo Status FAQ

Is Onomondo down right now?

The verdict at the top of this page comes from the latest poll of the official Onomondo status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Onomondo is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Onomondo recovers.

How do I check Onomondo uptime history?

PulsAPI tracks Onomondo uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Onomondo changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Onomondo outages?

PulsAPI reads the official Onomondo status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Onomondo components?

Yes. PulsAPI monitors 18 individual Onomondo components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Onomondo goes down?

Yes. Create a free account and subscribe to Onomondo: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Onomondo to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Onomondo problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Onomondo?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Onomondo plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Onomondo with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services