Get alerted when a service goes down
Instead of checking, be told. isuptime can raise a desktop notification and post to Discord, Slack or Telegram the moment any of the 102 services it monitors changes status. Pick the severity worth interrupting you for below. It is free, there is no account, and your settings — webhook URLs included — stay in this browser and are never sent to isuptime.
What is enough to start getting alerts
Three things, and two of them are already true. Everything above is optional beyond this.
- 1One channel, either kindBrowser notifications turned on, or one webhook URL pasted in. Either alone is enough; both together is fine and sends to both. Until one of them is set, nothing is sent at all.
- 2A threshold — already chosenIt starts at Degraded or worse, which alerts on everything. Change it only to be interrupted less: Partial Outage skips the wobbles, Major Outage keeps just the emergencies.
- 3A isuptime tab openThe alert is raised by this site running in your browser, so pin the dashboard in a background tab. Nothing has to stay on screen, and the tab may be any page on the site.
That is the whole list. No account, no email address, no per-service selection — one threshold covers all 102 services, so a provider you had not thought to watch still reaches you when it breaks.
Setting up a channel
Pick one. A webhook is the sturdier choice — it puts the alert in a channel your team already watches instead of on one machine — and browser notifications are the fastest, at two clicks and nothing to copy.
Browser notificationstwo clicks, nothing to copy
- Press Enable in the browser notifications card above.
- Allow the permission prompt your browser raises. If you have refused it here before, the prompt will not reappear — allow notifications for this site in your browser's site settings, then reload.
- Pin a tab and you are done.
Slackan incoming webhook for one channel
- Go to api.slack.com/apps and choose Create New App, then From scratch. Name it (isuptime alerts) and pick the workspace.
- Open Incoming Webhooks in the sidebar and turn Activate Incoming Webhooks on.
- Choose Add New Webhook to Workspace, pick the channel the alert should land in, and allow it.
- Copy the URL that appears — it starts https://hooks.slack.com/services/ — and paste it into the Slack field above.
Discordthe quickest of the three
- Open the channel's settings (the cog beside the channel name) and go to Integrations, then Webhooks.
- Choose New Webhook, name it, and confirm the channel.
- Press Copy Webhook URL and paste it into the Discord field above.
Telegrama bot token and a chat id
- Message @BotFather, send /newbot, and follow the two prompts. It replies with a token that looks like 123456789:AAF-abc… — that is the bot token field.
- Add the bot to the group you want alerts in, or send it a direct message. A bot cannot start a conversation, so this step is what makes it reachable.
- Send any message in that chat, then open https://api.telegram.org/bot<your token>/getUpdates in a browser and read chat.id from the response.
- Paste that id into the chat ID field. Group ids are negative and usually start with -100; a direct message id is a plain number.
GitHub: Major Outage
Status changed from Operational to Major Outage — Major Service Outage
The same two lines go to every channel, and the last part is the provider's own wording rather than ours. Finish with Send a test alert above — it delivers exactly this, so a channel that stays silent is misconfigured now rather than during an outage.
How these alerts work
An alert is raised by isuptime running in your browser: it compares each new reading against the one before it, and fires when a service crosses your threshold. That means a isuptime tab has to be open — pinned or in the background is fine. There is no server-side subscription, because there is no account to attach one to.
The reading itself comes from each provider's own published status feed, so an alert is only as early as the provider's own admission. A service can be visibly broken for you well before its status page says so — the method, and its limits, are written up in how it works.
Alerts — FAQ
- Do I need an account?
- No. There is no account, no email address and no sign-up. Your settings, including any webhook URL you enter, are stored in your own browser and never sent to isuptime. Clearing site data deletes them, and they do not follow you to another device.
- What is the minimum I need to set up?
- One delivery channel and an open tab. Turn browser notifications on or paste in a single Discord, Slack or Telegram webhook — either alone is enough — and keep a isuptime tab open in the background. The severity threshold is already set to alert on everything, so it needs no action unless you want to be interrupted less. There is nothing else: no account, no email address and no per-service selection.
- Will I get alerts when the tab is closed?
- Not reliably — alerts are raised by the page itself, so keep a isuptime tab open if you want them. A webhook is the sturdier option of the two: it puts the alert in a channel your whole team already watches, rather than on one machine.
- Which services can I set alerts for?
- All 102. Alerts follow a severity threshold across every monitored service rather than a per-service list, so something you had not thought to watch still reaches you when it breaks. Browse the full list on the services page, or keep the handful you depend on in one view with your stack.
- Where do the webhook URLs go?
- They stay in your browser. When an alert fires, the message is relayed through isuptime to the chat provider — the only way a browser can post to one — and nothing about the webhook is stored on the way through. Only Discord, Slack and Telegram webhook addresses are accepted, so the relay cannot be pointed anywhere else. More detail in the privacy policy.