OpusDNS logo

Is OpusDNS Down?

OtherLive status, outages, and incident history

No. OpusDNS is up right now.

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

OperationalChecked just nowLive · every 60s

Know the moment OpusDNS breaks

OpusDNS 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.

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

Status report

OpusDNS Status Summary

As of 19:37 UTC on 14 November 2026, OpusDNS is operational. PulsAPI checked OpusDNS's official status page and found 24 of 24 components operational, with no active incidents. The latest incident, ".mx domain registrations temporarily failing", was on Nov 10, 2026 and lasted 9 min.

Cite as: PulsAPI, “OpusDNS status”, checked 14 November 2026, 19:37 UTC. https://www.pulsapi.com/services/opusdns

OpusDNS Component Status

The main OpusDNS systems on this page. All 24 are operational right now.

24operational
API » Live | https://api.opusdns.com
Operational
API » Sandbox | https://sandbox.opusdns.com
Operational
Domain Services » DNS
Operational

21 more components tracked

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

Also tracking Domain Services » Domain Management, Domain Services » Domain Parking, Domain Services » Domain Registration, Domain Services » Domain Search, Domain Services » Domain Transfer, Domain Services » RDAP, Domain Services » Statistics, Domain Services » WHOIS, Infrastructure » Data Center, Infrastructure » DDoS Mitigation, Infrastructure » DNS, Infrastructure » Domain Forwarding, and 9 more.

See all of them free

Component statuses may change independently during partial outages.

Recent OpusDNS Outages & Incidents

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

.mx domain registrations temporarily failingResolved Nov 10, 2026 · 9 minResolved

The registry issue has been resolved and new .mx domain registrations are working again. --- [2026-11-10T18:06:01.987Z] (identified) We are continuing to work on a fix for this issue. --- [2026-11-10T18:00:16.303Z] (identified) New .mx domain registrations are currently failing with a temporary registry error (502 ERROR_REGISTRY_TEMPORARY). We have identified the cause and are working with the registry to resolve it. Other TLDs and existing .mx domains are not affected. We will post an update when .co registrations are working again

.co domain registrations temporarily failingResolved Nov 10, 2026 · 16h 54mResolved

This incident has been resolved. --- [2026-11-10T18:06:26.000Z] (identified) We are continuing to work on a fix for this issue. --- [2026-11-10T17:58:53.961Z] (identified) New .co domain registrations are currently failing with a temporary registry error (502 ERROR_REGISTRY_TEMPORARY). We have identified the cause and are working with the registry to resolve it. Other TLDs and existing .co domains are not affected. We will post an update when .co registrations are working again.

Domain Transfer Search Issue in the DashboardResolved Aug 24, 2026 · 0 minResolved

Organization pricing endpoints returned errors, so the dashboard could not display price information. Registration search, the public API, and order processing were unaffected. - Transfer search showed no prices and Add to cart was disabled; bulk-add skipped affected domains. Customers could not start inbound transfers from the dashboard. - Scheduled price-change views were unavailable. - Checkout was degraded but not blocked: some line items and totals displayed as €0, while orders already in the cart could still be submitted and were billed at the correct price. - Registration search was unaffected; its prices come from a different source. - Affected environments: Production and Sandbox.

OpusDNS Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a OpusDNS 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 OpusDNS Outage Reports

Problems reported by engineers using OpusDNS. 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 OpusDNS problems reported yet.

Something wrong with OpusDNS on your end?

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

About OpusDNS

OpusDNS's status page at status.opusdns.com lists 24 components, such as Live | https://api.opusdns.com, Sandbox | https://sandbox.opusdns.com and DNS. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on OpusDNS's side or yours.

OpusDNS Status FAQ

Is OpusDNS down right now?

The verdict at the top of this page comes from the latest poll of the official OpusDNS 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 OpusDNS 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 OpusDNS recovers.

How do I check OpusDNS uptime history?

PulsAPI tracks OpusDNS 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 OpusDNS changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect OpusDNS outages?

PulsAPI reads the official OpusDNS 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 OpusDNS components?

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

Can I get alerts when OpusDNS goes down?

Yes. Create a free account and subscribe to OpusDNS: 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 OpusDNS 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 OpusDNS problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor OpusDNS?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so OpusDNS 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 OpusDNS 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