User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
opusdns.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 1 hr ago. Last stored result reached it in 86 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 214 ms | 0 |
| Mon 20 | 0 | 0.0 | 115 ms | 0 |
| Mon 22 | 0 | 0.0 | 123 ms | 0 |
| Tue 00 | 0 | 0.0 | 78 ms | 0 |
| Tue 02 | 0 | 0.0 | 139 ms | 0 |
| Tue 04 | 0 | 0.0 | 104 ms | 0 |
| Tue 06 | 0 | 0.0 | 131 ms | 0 |
| Tue 08 | 0 | 0.0 | 119 ms | 0 |
| Tue 11 | 0 | 0.0 | 99 ms | 0 |
| Tue 13 | 0 | 0.0 | 137 ms | 0 |
| Tue 15 | 0 | 0.0 | 57 ms | 0 |
| Tue 17 | 0 | 0.0 | 79 ms | 0 |
| Tue 20 | 0 | 0.0 | 264 ms | 0 |
| Tue 22 | 0 | 0.0 | 131 ms | 0 |
| Wed 00 | 0 | 0.0 | 91 ms | 0 |
| Wed 02 | 0 | 0.0 | 126 ms | 0 |
| Wed 05 | 0 | 0.0 | 60 ms | 0 |
| Wed 07 | 0 | 0.0 | 131 ms | 0 |
| Wed 09 | 0 | 0.0 | 48 ms | 0 |
| Wed 11 | 0 | 0.0 | 52 ms | 0 |
| Wed 13 | 0 | 0.0 | 175 ms | 0 |
| Wed 15 | 0 | 0.0 | 208 ms | 0 |
| Wed 18 | 0 | 0.0 | 144 ms | 0 |
| Wed 20 | 0 | 0.0 | 176 ms | 0 |
| Wed 22 | 0 | 0.0 | 227 ms | 0 |
| Thu 00 | 0 | 0.0 | 160 ms | 0 |
| Thu 02 | 0 | 0.0 | 208 ms | 0 |
| Thu 04 | 0 | 0.0 | 157 ms | 0 |
| Thu 06 | 0 | 0.0 | 171 ms | 0 |
| Thu 09 | 0 | 0.0 | 169 ms | 0 |
| Thu 11 | 0 | 0.0 | 178 ms | 0 |
| Thu 13 | 0 | 0.0 | 118 ms | 0 |
| Thu 15 | 0 | 0.0 | 85 ms | 0 |
| Thu 17 | 0 | 0.0 | 212 ms | 0 |
| Thu 19 | 0 | 0.0 | 93 ms | 0 |
| Thu 21 | 0 | 0.0 | 107 ms | 0 |
| Thu 23 | 0 | 0.0 | 113 ms | 0 |
| Fri 01 | 0 | 0.0 | 100 ms | 0 |
| Fri 03 | 0 | 0.0 | 107 ms | 0 |
| Fri 05 | 0 | 0.0 | 110 ms | 0 |
| Fri 07 | 0 | 0.0 | 86 ms | 0 |
| Fri 09 | 0 | 0.0 | 61 ms | 0 |
| Fri 10 | 0 | 0.0 | 78 ms | 0 |
| Fri 12 | 0 | 0.0 | 122 ms | 0 |
| Fri 13 | 0 | 0.0 | 214 ms | 0 |
| Fri 15 | 0 | 0.0 | 190 ms | 0 |
| Fri 17 | 0 | 0.0 | 185 ms | 0 |
| Fri 18 | 0 | 0.0 | 86 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for OpusDNS 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 OpusDNS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OpusDNS alerts to Slack, Discord or a webhook — free.
OpusDNS, at opusdns.com, is one of the Cloud & developer services we monitor. Meet OpusDNS, the next generation of domain reselling. Join us as we revolutionize the industry, simplifying the way you buy, sell, and manage domains.
OpusDNS publishes an official status page at status.opusdns.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 116 ms average, 59–214 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public OpusDNS incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
116 ms on average over the last 24 hours (59–214 ms).
Yes, at https://status.opusdns.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 OpusDNS here at once, the problem is on OpusDNS'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 OpusDNS. 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.