Invite the bot
One click through Discord's own authorization screen. ASP asks for the minimum: read a channel, post and edit its own message.
/asp setup
Status delivery for Discord
Nobody opens a status page. So we bring it to the one place your team never closes.
Point ASP at any status page. It watches every component, and the moment something breaks, degrades or recovers, your channel knows. One pinned message, always current.
Free to add no card, no seats running in about two minutes
A
AverisStatusPage
bot
edited just now
This card updates on its own. So does the real one.
How it works
Three steps, then never think about it again
No webhook plumbing, no cron jobs, no scraping scripts of your own.
Bind a page and a channel
Paste the status page URL, pick the channel. Everything on that page (components, uptime, open incidents) gets parsed and mapped.
/asp bind url: #channel:
Read it where you already are
One message stays pinned and edits itself in place. Real state changes ping you; routine checks stay quiet.
/asp watch --alerts on
AverisStatusPage
watching since 2024
What you get
Built for the five minutes when everything is on fire
01 / LIVE
A message that edits itself
ASP keeps one embed per binding and rewrites it on every poll instead of flooding the channel. Scroll up, and the history is incidents only.
02 / ALERTS
Pings only when state changes
Operational to degraded, degraded to down, down to recovered. Choose the role to mention per severity, so a partial blip does not wake up everyone.
03 / SOURCES
Any status page, one syntax
Statuspage, Instatus, BetterStack, Cachet and Uptime Kuma are parsed natively. Anything else works through a JSON, RSS or plain HTTP check.
04 / SCOPE
Many pages, many channels
Bind production to your on-call channel and vendor pages to a quieter one. Each binding has its own filters, so a component you do not care about never shows up.
05 / HISTORY
Uptime you can quote
Ninety days of per-component history, kept whether or not the upstream page keeps it. Ask the bot for a summary before your next review meeting.
Two buttons, that is the whole onboarding
Add the bot. Then connect your account.
Adding the bot gets status into a channel. Connecting your Discord account unlocks the dashboard: manage every binding, see poll logs and export history without touching a slash command.
Questions people actually ask
Before you invite it
Does it need admin permissions?
No. View Channel, Send Messages, Embed Links and Read Message History. If a server asks for less, ASP still works with reduced output.
What if my status page is self-hosted or private?
Fine, as long as the VPS running ASP can reach it. Basic auth and a static header token are both supported per binding.
How fast are the updates?
Default poll is 60 seconds. Pages exposing webhooks or RSS get pushed changes within a few seconds instead.
Do you store message content?
No. ASP has no message content intent. It stores guild id, channel id, the URLs you bind and the status history it collects. Details are in the privacy policy.
Who runs it?
One independent operator on a dedicated VPS, not a venture backed startup. Contact goes straight to a human.