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

A status page your customers can read.

Your domain, your logo, your words. Incidents appear the moment they open, and your updates say what happens next.

Start free See an example
the status page, the band set by you
how it works

Three steps to published.

One screen to create it, one editor to make it yours.

  1. Pick what is on it

    A new page starts empty. Add the monitors, heartbeats and groups you want, with names your customers understand. The page needs at least one before it is built.

  2. Make it yours

    In the design editor: logo, favicon, accent, one of four layouts and your own domain, previewed on a bad day, then published from the editor.

  3. Write the updates

    Investigating, identified, monitoring, resolved, each with the time of the next update.

what is on the page

Built to be read on a bad day.

The page works when your app does not: it reads in full without script and loads from a cache.

  • Layouts Banner, Plain, Grid and Docs
  • States Operational, Degraded performance, Partial outage, Major outage, Maintenance, No data and Paused, each with its own colour, symbol and word
  • Days No downtime, Some checks failed, Degraded performance or Major outage
  • Incidents each one has its own public page with every update
  • Your domain on Solo and Team, the certificate issued for you
  • Subscribers An email when an incident opens, on each update, when it ends, and before planned maintenance
  • History 90 days per component, a page per month
  • Badge an image for your nav, footer or README
status.devglory.com public
The services on the Devglory status page: Storefront, Payments, Search and Images operational, each with its daily bars and uptime, one slow day and one outage day on Storefront.
plans

One page free, more on paid plans.

Every page carries the same states and the same history.

Free0 EUR

  • 1 status page
  • on an upglory.io address
  • 90 days of history

Solo15 EUR a month

  • 5 status pages
  • your own domain
  • 1 year of history

Team49 EUR a month

  • 50 status pages
  • your own domain
  • the credit can be removed
Every limit, side by side prices in EUR, VAT added where it applies
questions

Before you publish.

Does the written reason appear on the page?

Never. Your customers read your updates. The explanation stays inside, for you.

Can I keep an incident off the page?

Yes, from the incident itself. The day still shows its dip in the history, so the page stays honest.

How long is history kept?

Daily history and incidents are kept for 90 days on Free, 1 year on Solo and 2 years on Team, and you read them in the dashboard. Raw checks are kept for 30 days on every plan. Public status pages show the last 90 days.

Which time zone does the page use?

The one you set, or the visitor's own if you allow it. The footer of the page says which.

20 monitors free. No card.

Your first check runs two minutes from now.

Start free
the mark: five days, one short