User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
opennms.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 64 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 19 | 0 | 0.0 | 73 ms | 0 |
| Tue 21 | 0 | 0.0 | 163 ms | 0 |
| Tue 23 | 0 | 0.0 | 143 ms | 0 |
| Wed 01 | 0 | 0.0 | 128 ms | 0 |
| Wed 04 | 0 | 0.0 | 39 ms | 0 |
| Wed 06 | 0 | 0.0 | 96 ms | 0 |
| Wed 08 | 0 | 0.0 | 60 ms | 0 |
| Wed 10 | 0 | 0.0 | 73 ms | 0 |
| Wed 13 | 0 | 0.0 | 110 ms | 0 |
| Wed 15 | 0 | 0.0 | 138 ms | 0 |
| Wed 17 | 0 | 0.0 | 56 ms | 0 |
| Wed 19 | 0 | 0.0 | 98 ms | 0 |
| Wed 21 | 0 | 0.0 | 86 ms | 0 |
| Wed 23 | 0 | 0.0 | 168 ms | 0 |
| Thu 02 | 0 | 0.0 | 112 ms | 0 |
| Thu 04 | 0 | 0.0 | 100 ms | 0 |
| Thu 06 | 0 | 0.0 | 112 ms | 0 |
| Thu 08 | 0 | 0.0 | 272 ms | 0 |
| Thu 10 | 0 | 0.0 | 57 ms | 0 |
| Thu 12 | 0 | 0.0 | 93 ms | 0 |
| Thu 14 | 0 | 0.0 | 107 ms | 0 |
| Thu 16 | 0 | 0.0 | 83 ms | 0 |
| Thu 18 | 0 | 0.0 | 129 ms | 0 |
| Thu 20 | 0 | 0.0 | 96 ms | 0 |
| Thu 22 | 0 | 0.0 | 52 ms | 0 |
| Fri 00 | 0 | 0.0 | 61 ms | 0 |
| Fri 02 | 0 | 0.0 | 143 ms | 0 |
| Fri 04 | 0 | 0.0 | 122 ms | 0 |
| Fri 06 | 0 | 0.0 | 139 ms | 0 |
| Fri 09 | 0 | 0.0 | 148 ms | 0 |
| Fri 11 | 0 | 0.0 | 72 ms | 0 |
| Fri 13 | 0 | 0.0 | 145 ms | 0 |
| Fri 15 | 0 | 0.0 | 44 ms | 0 |
| Fri 17 | 0 | 0.0 | 129 ms | 0 |
| Fri 19 | 0 | 0.0 | 123 ms | 0 |
| Fri 20 | 0 | 0.0 | 116 ms | 0 |
| Fri 21 | 0 | 0.0 | 56 ms | 0 |
| Fri 23 | 0 | 0.0 | 94 ms | 0 |
| Sat 01 | 0 | 0.0 | 111 ms | 0 |
| Sat 03 | 0 | 0.0 | 104 ms | 0 |
| Sat 05 | 0 | 0.0 | 110 ms | 0 |
| Sat 07 | 0 | 0.0 | 102 ms | 0 |
| Sat 10 | 0 | 0.0 | 26 ms | 0 |
| Sat 12 | 0 | 0.0 | 163 ms | 0 |
| Sat 14 | 0 | 0.0 | 41 ms | 0 |
| Sat 17 | 0 | 0.0 | 70 ms | 0 |
| Sat 19 | 0 | 0.0 | 72 ms | 0 |
| Sat 21 | 0 | 0.0 | 64 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for The OpenNMS Group yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when The OpenNMS Group goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
The OpenNMS Group, at opennms.com, is one of the Cloud & developer services we monitor. OpenNMS is an enterprise-grade network monitoring platform that can be deployed anywhere. Companies in the Fortune 100 use it every day.
The OpenNMS Group publishes an official status page at status.opennms.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 86 ms average, 26–163 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public The OpenNMS Group incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
86 ms on average over the last 24 hours (26–163 ms).
Yes, at https://status.opennms.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report The OpenNMS Group here at once, the problem is on The OpenNMS Group's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with The OpenNMS Group. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.