Website, API & Uptime Monitoring
Know when something breaks before your users do.
Alertum monitors your websites, APIs, SSL certificates, TCP services, heartbeats, and user journeys — and routes incidents to the right person through configurable escalation policies.
No credit card required · Free plan available
Monitors
Example monitor outputIncident opened — checkout service response time exceeded threshold. Escalation policy notified.
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).
AI-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.
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.
Webhook
Push any event to your own HTTP endpoint for custom routing logic.
Reliable incident and recovery notifications to any address.
Discord
Send structured alert messages to any Discord server channel.
Microsoft Teams
Adaptive card notifications in Teams channels.
Google Chat
Route alerts to Google Chat spaces and threads.
Slack
Open a thread when an incident fires. Updates post automatically on resolve.
Webhook
Push any event to your own HTTP endpoint for custom routing logic.
Reliable incident and recovery notifications to any address.
Discord
Send structured alert messages to any Discord server channel.
Microsoft Teams
Adaptive card notifications in Teams channels.
Google Chat
Route alerts to Google Chat spaces and threads.
Telegram
Deliver alerts to Telegram groups or bot conversations.
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.
New Relic
Correlate Alertum incident events with New Relic observability data.
Splunk
Forward incident data to Splunk for log correlation and analysis.
Telegram
Deliver alerts to Telegram groups or bot conversations.
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.
New Relic
Correlate Alertum incident events with New Relic observability data.
Splunk
Forward incident data to Splunk for log correlation and analysis.
Simple pricing. No surprise overages.
Start free with no card required. Upgrade when your team needs more monitors, shorter check intervals, or on-call.
Starter
For indie developers and small projects
- ✓10 monitors
- ✓5-min checks
- ✓Email alerts
- ✓30-day history
Pro
For growing teams that need reliability
- ✓50 monitors
- ✓1-min checks
- ✓All channels
- ✓AI diagnostics
- ✓On-call
- ✓90-day history
Enterprise
For teams that need SLA-backed infrastructure
- ✓Unlimited monitors
- ✓30s checks
- ✓SSO
- ✓Custom SLA
- ✓Dedicated support
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.