Integrations
Alerts wherever your team works
Slack, Microsoft Teams, PagerDuty, SMS, push and more, confirmed before they go out and followed by a recovery. Plus webhooks, a REST API and an MCP server for your own tools.
Chat
Alerts where your team already talks.
-
Slack
Add to Slack: alerts in the channel you pick, with an Acknowledge button on outages. How it works : Slack -
Microsoft Teams
Alerts as cards in a Teams channel, through a Teams workflow. How it works : Microsoft Teams -
Discord
Color-coded embeds in a Discord channel, through a channel webhook. How it works : Discord -
Google Chat
Alerts as messages in a Google Chat space, through a webhook. How it works : Google Chat -
Mattermost
Alerts in a channel on your own Mattermost server, through an incoming webhook. How it works : Mattermost -
Telegram
Press Start in our bot’s chat, or add it to a group. No token to create. How it works : Telegram
Paging, SMS and email
For the alerts that must reach a person.
-
PagerDuty
Outages trigger a PagerDuty incident; recoveries resolve it. How it works : PagerDuty -
SMS
A text when a monitor goes down and when it recovers. On every plan, with credits. How it works : SMS -
Email
Clear alert emails with the cause, the start time and a button to the incident. How it works : Email
Push notifications
Straight to the lock screen.
-
Push notifications
Free lock-screen alerts on iPhone, Android and computers, to whoever is on call. How it works : Push notifications -
ntfy
Push alerts through ntfy.sh or your own server, outages at top priority. How it works : ntfy -
Pushover
Outages as high-priority Pushover alerts that break through quiet hours. How it works : Pushover
Developers
Wire Uptimecheck into your own systems and assistants.
-
Webhooks
Every alert as signed JSON to your own endpoint, with retries. How it works : Webhooks -
REST API
Monitors, incidents, maintenance and status updates, with an OpenAPI document. Read more : REST API -
MCP server
Let Claude, Cursor or VS Code check status and manage monitors with an API key. How it works : MCP server
Every channel works the same way
- Alerts go out only when a second check confirms the outage, and a recovery follows with the downtime.
- Any channel can wait 5 to 60 minutes and alert only if the outage lasts and nobody has acknowledged it.
- A failed alert is retried for about 40 minutes; if it still fails, the channel shows Not delivering with the reason.
- Every channel is on every plan; SMS uses credits.
For your status page too
Visitors of an Uptimecheck status page can follow it by email, in Slack, Microsoft Teams or Discord, or by webhook, for the whole page or only the components they care about.
Moving from another tool? Monitors import from UptimeRobot, Better Stack, Pingdom and StatusCake, and status pages from Atlassian Statuspage. See the feature comparison.
Downtime is obsolete.
Set up your first monitor in under a minute, or look around the live demo first.
14-day free trial · No credit card required