Uptime and certificate alerts in Discord

hostnag posts an embed for every alert to a Discord channel webhook, colored by severity.

Start free See pricing

Included on Pro and Business.

PlansFreeProBusiness

Down

Title: [Critical] https://www.example.com/ is down
Description: Down from 2 of 3 locations (US East, Frankfurt). Last error: unexpected_status: 503. [Acknowledge](https://hostnag.com/ack/abababababababababababababababababababababababababababababababab)
Group: Client A
Monitor: Marketing site
Target: https://www.example.com/
Down since: 12 Sept 2026, 07:58 UTC
Locations: US East, Frankfurt
Status code: 503
Last error: unexpected_status: 503

Set up

01
Create a channel webhook
In Discord: Edit Channel, Integrations, Webhooks, then copy the URL.
02
Paste the webhook URL
The URL must be on discord.com; hostnag stores it as a secret, never in plain config.

What arrives

Rendered by the same code that sends it.

Back up

Title: [Recovered] https://www.example.com/ is back up after 1 h 15 min
Description: https://www.example.com/ answered again from every location. It was down for 1 h 15 min. [Acknowledge](https://hostnag.com/ack/abababababababababababababababababababababababababababababababab)
Group: Client A
Monitor: Marketing site
Target: https://www.example.com/
Down since: 12 Sept 2026, 07:58 UTC
Duration: 1 h 15 min

Issuer changed

Title: [Warning] Certificate issuer changed on api.example.com
Description: The certificate on api.example.com is now issued by ZeroSSL RSA Domain Secure Site CA (was Let's Encrypt (R11)). A renewal by a new CA is normal; anything else is worth a look. [Acknowledge](https://hostnag.com/ack/abababababababababababababababababababababababababababababababab)
Group: Client A
Monitor: API
Target: api.example.com
Expires: 11 Nov 2026
Issuer: Let's Encrypt R11
Was: Let's Encrypt (R11)
Now: ZeroSSL RSA Domain Secure Site CA

Routing

Every alert follows the group's alert policy: which channels a route goes to and the minimum severity each one takes, in bands of critical, warning and info. Quiet hours hold non-critical alerts for email, Slack, Discord, SMS, Teams and Telegram until the window closes, then deliver one digest; critical alerts are never held, and webhook, PagerDuty and Opsgenie always deliver right away since they hand off to another machine, not a person. A maintenance window on a group or a monitor suppresses alerts for its duration while checks keep running. An alert nobody acknowledges escalates through up to three tiers, each after its own number of minutes, and can be acknowledged with one tap from the alert message itself.

Questions

Does the embed color mean anything?

Yes. It follows severity, the same info, warning and critical bands used everywhere else.

Can one channel serve several groups?

Yes. Channels are org-level and routed per group by its own policy.

Watches

Alerting and status pagesEvery alert routed to the right channel at the right severity, held during quiet hours and maintenance, escalated until it's acknowledged.Uptime monitoringWebsites, APIs and anything that answers on a port, checked every minute from up to four places, with a failure confirmed before anyone is paged.Certificate monitoringEvery certificate hostnag can reach is watched for expiry and a swapped chain; the ones it cannot reach get a URL to report to instead.

Add a host. Hear about it in Discord.

Start free