Provider status monitoring

When your site is down, the first question is whether it is your site or your host. DomainGuard polls the public status pages of more than 850 providers and matches them to the vendors your own domains actually use.

Where

• Web: Software, Service status; the public page at nhmohio.com/status shows the whole catalogue.
• iOS: Account, Service status. A hero card appears only when one of your providers has an active problem. A slim strip under the Monitoring title names a provider incident and fades when it resolves.
• API/MCP: GET /api/status/services, /incidents, /history (public); GET/PUT /api/status/subscriptions; tools get_status_services (vendors not operational right now, across the catalogue), get_status_incidents, get_status_history, list_status_subscriptions, get_status_subscription_suggestions, update_status_subscriptions.

Which providers are "yours"

The domain scan records the DNS host, the mail provider, the registrar and the software fingerprinted on the site. Service status leads with those, each with its live status. The Notify me about provider issues switch (on by default in the app) subscribes you only to providers found in your records; Subscribe all and Unsubscribe all on nhmohio.com/status cover the whole catalogue.

Incident detail

Tap a provider issue for what it means for you: which of your domains it touches (named), what is not affected, "Nothing to change on your side" when that is true, the provider's latest update, and a link to their status page.

Providers with no status page

A piece of software your site runs (WordPress, Next.js, nginx) has no uptime page. Its row reads "CVEs and KEVs only" and opens the full record of every CVE and KEV ever published against that software, counted by year and severity. See KEV and CVE alerts.

How polling works

The monitor runs on the five-minute tick and polls up to 250 services per run, subscribed services first, oldest poll first, so the rows anyone is watching are always fresh and the long tail rotates through in about a quarter of an hour.

Suggesting a provider

If a vendor you rely on is missing, POST /api/status/suggest (the "Suggest a status page" form on nhmohio.com/status) files its URL into a review queue. It is added to the catalogue once checked.

Alerts

The Third-party vendor status switch (web; notify_status_push) turns these pushes on or off. With the morning summary on (the default), an incident opening at a provider your domains run on is one of the two things that still push right away, between 8 a.m. and 5 p.m. Eastern; its resolution waits for the summary. Each incident lands in the alert feed naming the provider, as one row that moves through the vendor's own words (investigating, found the cause, monitoring a fix, resolved).

• One push when an incident opens, one when it is resolved ("Cloudflare resolved: API errors / Resolved after 2 hr 10 min"). Updates in between are feed rows. The resolved push goes only to accounts that were pushed the opening.
• Pushes only for providers your domains run on, as the domain scan detected them. A provider you subscribed to that none of your domains use still gets its feed rows.
• Bursts merge. At most three provider pushes in 15 minutes; past that, feed rows. A provider's status dropping in the same poll as its new incident is one push, not two. A subscription at major pushes only incidents the vendor rated major or critical.
• Improvements never push. A return to normal is a feed row for accounts told about the drop.