Uptime checksHTTP, keyword and TLS checks on your addresses, with the evidence of every failure kept.
Cron heartbeatsOne curl line at the end of a job. Silence past the grace window is the alert.
Status pagesA page your customers read, on your own domain, with the incident in plain words.
ExplanationsA written reason with the alert: what failed, what the checks saw, what to look at first.
on every plan Alerts to six channelsImportTeams
APIRead, pause, acknowledge and post updates from your own scripts.
MCP serverAsk your AI assistant what is down, then acknowledge or post an update.
WebhooksSigned JSON when an incident opens, is acknowledged or recovers.
Heartbeat guidescrontab, GitHub Actions, Railway, Node, Go, WordPress and Kubernetes.
DocsShort guides, each one task, with the lines to copy.
GuidesWhy monitors send false alarms, why cron jobs stop, and the fix.
ChangelogThe big things we shipped, newest first.
Trust and securityWhere your data lives, who processes it, how long we keep it.
Referral program soonRecommend Upglory to another team. In the works.
Contact
Guides menu All guides

Guides

The problems behind a missed outage or a false alarm, how to find the cause, and the fix that works with any tool.

  1. Why uptime monitors send false alarms, and how to stop them

    The alert says the site is down. You open it and it loads. Here is what usually happened, and how to stop it happening again.

    Updated on 24 October 2026, 7 minute read

  2. Cron job not running? How to find out when it silently stops

    Cron does not tell anyone when a job fails or never starts. Here is how to find out why it stopped, and how to hear the next time it does.

    Updated on 24 October 2026, 7 minute read

  3. Certificate expiry: why auto-renewal still fails

    Renewal is automatic, so nobody watches it, and the day it fails browsers block the site. Here is why it fails, and how to hear in time.

    Updated on 24 October 2026, 7 minute read

  4. How often should an uptime monitor check? 1 minute or 5

    A check is a sample, and between two checks the monitor knows nothing. Here is what an interval costs you in minutes, and how to pick one.

    Updated on 24 October 2026, 6 minute read

  5. How to monitor an API: what a 200 does not tell you

    An API that answers 200 can still be broken for everyone calling it. Here is what a useful check looks at, and how to build an endpoint worth checking.

    Updated on 24 October 2026, 8 minute read

  6. Status page updates: what to write at each stage

    During an outage people write too little, too late, or guess. Here is what to say at each stage, with an example update for each one.

    Updated on 24 October 2026, 7 minute read

  7. Is it DNS or the server? A five-step check with dig and curl

    When the site is down, any of four layers can be the cause, and each one needs a different person. Five commands tell them apart.

    Updated on 24 October 2026, 7 minute read

  8. How to write an incident report your customers will read

    A postmortem is written for engineers. A customer wants three answers in two minutes. Here is the shape that gives them, with a full example.

    Updated on 24 October 2026, 7 minute read