Website, API & uptime monitoring. Know it broke before your users do.
Alertum watches your websites, APIs, SSL certificates, TCP services, heartbeats, and user journeys — and when something fails, it pages the right person through your escalation policies.
- Free plan available
- No credit card required
- Set up in minutes
Incident opened — checkout response time 1.4s exceeded 800ms threshold. Escalation policy notified · 2m ago
Monitoring for every critical system
One platform covering every layer of your stack — from public URLs and APIs to background jobs, infrastructure ports, and user journeys.
Why teams use Alertum
Monitoring that covers the whole stack, alerts that reach the right person, and communication tools built into the same product.
Fast, reliable checks
HTTP, SSL, TCP, and ping checks run at 30-second intervals from multiple locations. You know within seconds when something fails.
Alerts go to the right person
Escalation policies route incidents through your team's structure — on-call rotations, channels, and fallback paths — without manual configuration per alert.
Fewer false alarms
Configurable failure thresholds mean a single slow probe doesn't page your team at 3am. Incidents open after repeated failures, not the first hiccup.
Transparent to customers
Public status pages communicate service health and incident updates to your users, reducing inbound support tickets during outages.
Background job visibility
Heartbeat checks detect silent cron job failures. When a scheduled job stops reporting, an incident opens automatically — no agent or SDK required.
Team incident workflow
Assign, escalate, comment, and resolve incidents from one shared workspace so every response is documented and visible.
From signal to resolution in one loop
Detection, escalation, diagnostics, and communication — without switching tools or waiting for someone to notice the Slack message.
Failure detected
A check fails across the configured number of consecutive probes. Alertum opens an incident and records the first-seen timestamp.
Team notified
Your escalation policy routes the incident to the right channel — Slack, email, or webhook — without duplicate noise.
On-call responder paged
The current on-call rotation is identified. If the first responder doesn't acknowledge within the escalation window, the next level is triggered automatically.
Context surfaced
Alertum correlates recent failures, related checks, and deployment signals into a diagnostic summary so your responder starts with context, not a blank screen.
Incident resolved
Once checks recover, the incident closes. Your status page updates automatically. The timeline is preserved for review.
Example incident
Checkout service degraded
Check failed — HTTP 503 on /checkout/confirm
Incident opened · Slack notification sent
On-call engineer paged via escalation policy
Incident acknowledged by responder
AI-assisted context
Suggested likely cause: database connection pool exhaustion following a deploy 4 minutes prior. Related checks: auth-service (elevated latency), billing-worker (last heartbeat 6 minutes ago).
Error intake
Every error from your server becomes an incident
Send errors from your backend straight into Alertum — exceptions, crashes, failed jobs, anything your services throw. Each event creates an incident or groups into an existing one, with service context attached and your escalation policies deciding who gets paged. No separate error tracker to check.
Every kind of error, one intake
Unhandled exceptions, failed background jobs, database timeouts, third-party API failures — if your service can report it, Alertum turns it into an incident.
Grouped, not spammed
Repeated events fold into one incident by project and error group — a burst of the same exception becomes a single incident with an event count, not 200 pages.
Triaged like downtime
Each incident carries severity, service, and environment, and follows your escalation policies — acknowledge, reassign, resolve, or snooze in the same queue.
Intake errors
ActiveAI-assisted incident context
When an incident opens, Alertum correlates related signals — recent failures, deployment events, and connected checks — and surfaces a suggested likely cause so your responder starts with context, not a blank screen.
The diagnostic summary is assistive, not authoritative. It gives your team a starting point and reduces the first few minutes of investigation.
Cross-signal correlation
Groups related monitor failures, heartbeat misses, and recent deployment events into a single diagnostic view so your responder sees the full picture immediately.
Suggested likely cause
Surfaces a plain-language hypothesis based on correlated signals — not a definitive answer, but a starting point that saves the first 10 minutes of investigation.
Responder-ready summary
Each incident includes a concise summary of what failed, when it started, what else changed recently, and which other checks are affected.
Post-incident draft
When an incident closes, Alertum pre-fills a review template with the timeline, affected services, and response sequence — saving your team the blank-page problem.
Example AI-assisted summary
Checkout service · Incident #00412
Suggested likely cause
Database connection pool exhaustion. Memory grew steadily after the 09:10 deploy. Connections began queuing at 09:14. Checkout calls started failing at 09:14:02.
Correlated signals
- ·Deploy: v2.4.1 pushed at 09:10 UTC
- ·auth-service: elevated latency since 09:12
- ·billing-worker: last heartbeat 6 min ago
Suggested next step
Recycle the database connection pool and monitor latency over the next 5 minutes. Consider rolling back v2.4.1 if latency does not stabilise.
This is a synthesised summary, not a live diagnostic. Actual output depends on your monitoring configuration.
MCP server
Ask your AI about your infrastructure
Alertum ships a hosted MCP server, so the AI assistant you already use can see your monitoring. Ask what's down, what got slower, or what happened overnight — and get answers grounded in your real checks, incidents, and heartbeats.
Ask in plain language
“What’s down right now?” “Why did checkout fail last night?” “Which certificates expire this month?” — your AI answers from live monitoring data, not from memory.
Your whole fleet, one conversation
Monitors, open incidents, heartbeats, and status pages are all reachable from the same chat — no dashboard tab-hopping while you investigate.
Safe to connect
The MCP server is read-only and team-scoped, with OAuth sign-in. Your AI can look at your monitoring — it can never pause a monitor, close an incident, or touch your API keys.
Works with the tools you already use
Claude, Claude Code, Cursor — anything that speaks the Model Context Protocol can connect in minutes. No SDK, no custom integration.
Claude
Alertum MCP connected
Is anything down right now?
Yes — Payments API is down. It has been failing with HTTP 503 since 09:14, about 4 minutes now. An incident is already open and Maya from your on-call rotation was paged.
Your other 27 monitors are healthy — marketing site, auth service, checkout journey, and last night's backup heartbeat all look normal.
Was it slow before it went down?
It was. Response time climbed from ~300 ms to 1.8 s in the 20 minutes before the first failure — starting right after the 09:02 deploy of payments v2.4.1.
A gradual slowdown like that usually means the service was saturating, not crashing outright.
Who's on it, and what should I tell the team?
Maya acknowledged the page at 09:17 and is investigating. For the team: checkout is unaffected, the incident started at 09:14, and the likely trigger is the v2.4.1 deploy — worth having a rollback ready if Maya confirms it.
Claude setup
$ claude mcp add --transport http alertum https://mcp.alertum.co/mcp$ claude mcp login alertum
Slack app
Run incident response from Slack
Alerts landing in a channel is table stakes. The Alertum app works both ways: acknowledge and resolve incidents, pause monitors during deploys, check who's on call, and open maintenance windows — without switching tabs.
/alertum statusFleet snapshot — what's up, what's down, open incidents./alertum ack <id>Claim an incident without leaving the channel./alertum oncallWho's paged right now, and who's up next./alertum pause <monitor>Silence a monitor while you deploy./alertum maintenanceOpen a maintenance window from a modal./alertum ask <question>Plain-language answers about monitors and incidents.Alertum App 09:14
Incident started — Payments API
Server error (503) · api.payments.example.com
Only visible to you
👀 Acknowledged b4d1f2a9 Payments API — assigned to you.
Alertum App 09:26
Incident resolved — Payments API
Recovered after 12m.
/alertum
Alert where your team already works
Incidents land in the right channel automatically. Configure your escalation policy once — Alertum handles the routing from there.
Slack
Open a thread when an incident fires. Updates post automatically on resolve.
Microsoft Teams
Adaptive card notifications in Teams channels.
Discord
Send structured alert messages to any Discord server channel.
Telegram
Deliver alerts to Telegram groups or bot conversations.
Reliable incident and recovery notifications to any address.
Google Chat
Route alerts to Google Chat spaces and threads.
Webhook
Push any event to your own HTTP endpoint for custom routing logic.
Pushover
Send instant incident alerts to Pushover for simple mobile and desktop notifications.
Pushbullet
Deliver alert notifications to Pushbullet so incidents reach your devices quickly.
Simple pricing. No surprise overages.
Start free with no card required. Upgrade when your team needs more monitors, shorter check intervals, or on-call scheduling.
Free
Core monitoring to get started fast.
- 25 monitors
- 5 heartbeats
- 1 journey
- 5-min checks
- 7 days retention
Solo
Designed for solo founders and indie SaaS.
- 50 monitors
- 10 heartbeats
- 5 journeys
- 3-min checks
- Private status pages
- 30 days retention
Team
Built for growing SaaS teams and production workloads.
- 100 monitors
- 50 heartbeats
- 20 journeys
- 1-min checks
- 3 members included
- SLA reports
- 90 days retention
Business
Serious production reliability and control.
- 200 monitors
- 100 heartbeats
- Unlimited journeys
- 30-sec checks
- 5 members included
- On-call scheduling
- 1 year retention
Set up your first monitor in two minutes
Free plan available. No credit card, no sales call, no setup fee. Add a URL and Alertum starts checking it immediately.