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

Every incident, explained in plain words.

Once an incident is confirmed, Upglory reads the evidence the checks kept and writes two or three sentences on what most likely happened.

headers, body and DNS, read into one written reason
how it works

From evidence to a reason.

It starts from what the checks saw, never from a guess.

  1. The evidence is kept

    Headers, the body excerpt, the DNS answer, the certificate and the timings from every location.

  2. It is read once

    After the incident is confirmed. Never on a single failing check.

  3. You get the reason

    In the incident, and in the alert when it is ready in time, marked as written by AI, with the time.

what it never does

Useful, and kept in its place.

An explanation helps you start. It never changes a state or reaches a visitor on its own.

  • Change a state only checks decide up and down
  • Reach your visitors never on a status page
  • Hold an alert if it fails, the alert goes out without it
  • Pretend when the evidence is thin, it says so
incident 48 checkout.devglory.com
What happened on the Checkout incident, written by AI from the evidence: the load balancer answered with a 502, so the checkout service is unreachable; look at it first, then the payments API. It says it can be wrong.

Drop it into an update as a draft and rewrite it in your own words. Only your words are published.

after the incident

From the alert to the write-up.

When the incident is over, the same evidence becomes the record you keep and the one you send.

  1. incident 46 investigation
    The investigation of the same incident: what happened, in order, from the first failure to its confirmation, then every check from each location oldest first, failed with a 503 or passed with a 200.
    01

    Investigate it

    Every check from every location, from 30 minutes before the failure to just after it ended, in order. Open any check for its status, timings, DNS answer and certificate.

  2. incident 46 incident report
    The incident report on a resolved Payments API incident, written by AI: it lasted 9 minutes, the summary, the likely cause, the impact, what the evidence shows, three follow-ups and the buttons to copy it, start the review from it and download the PDF.
    02

    Ask for the report

    On a resolved incident, one press writes a summary, the impact, what the evidence shows, the likely cause and follow-ups. It uses 3 AI credits, and if it cannot be written they come back.

  3. incident 46 PDF, page 1
    The first page of the incident PDF: Payments API was down for 9 minutes, when it opened and resolved, the explanation and the incident report, each marked as written by AI.
    03

    Send the PDF

    The timeline, the checks from each location, the explanation and the report, each AI part marked as written by AI. Free to download, as often as you need.

Copy the report as plain text or Markdown, or start your incident review from it.

plans

A monthly allowance on every plan.

A written explanation uses 1 AI credit and an incident report 3. When they run out, the incident says so and everything else still works.

Free0 EUR

  • 10 AI credits a month

Solo15 EUR a month

  • 100 AI credits a month

Team49 EUR a month

  • 500 AI credits a month
Every limit, side by side a top-up of 500 costs 20 EUR once and never expires
questions

Before you rely on it.

What is sent to write it?

The evidence of that incident. A monitor marked as carrying secrets never keeps a body or headers, so none are sent.

Who writes it?

An AI model provider, named by category in the privacy notice. It reads only that incident's evidence.

What happens when the AI credits run out?

The incident says so where the written reason would be. Monitoring, incidents and alerts carry on as before. A written explanation uses 1 AI credit and an incident report 3. A pack of 500 AI credits is 20 EUR, paid once, and never expires.

Does the report change anything?

No. Like the explanation, it never changes a state and never appears on a status page. It is marked as written by AI; read it before you share it.

What does the PDF show for a monitor carrying secrets?

Its host only, never the full address.

20 monitors free. No card.

Your first check runs two minutes from now.

Start free
the mark: five days, one short