Free
$0 / month
No card needed
Start for free- 5 monitors
- Checks every 5 minutes
- 1 team member
- 1 status page
- 90 days of history
Website, server and API monitoring
Know first. Then do something about it.
UptimeWave checks your websites, servers, APIs and scheduled jobs around the clock and tells the right people the moment something breaks. It also takes in alerts from the tools you already use, and when you want it to, it responds for you.
- Website
- Keyword
- Ping
- Port
- Heartbeat
- DNS
- API
- SSL and domain expiry
Free plan, no card needed. Checks as often as every 15 seconds on paid plans.
- Something goes wrong
- Website check failedcheckout.example.com answered 503, confirmed from 3 regions
- Alert from DatadogBrute force on /login from
203.0.113.42
- The right people hear firstand your responses run
- Team told by email and SlackEscalates to on-call if nobody acts in 30 minutes
- Block 203.0.113.42Waiting for a person to approve
- Handledin 4 minutesBack up. Address blocked for 1 hour.
Recovery sent, status page updated, block removed on its own.
Monitoring you can rely on, before anything else
Every response starts with a check you trust. Eight kinds cover the things most teams run, from a website to a cron job to alerts from other tools, and each takes a minute to set up.
Website
Checks that your page loads and answers with a good status code.
Keyword
Checks that a word is on the page, or is not, so an error page never passes as up.
Ping
Checks that a server answers ping.
Port
Checks that a port, such as a database or mail server, accepts connections.
HeartbeatPro and up
Your cron job or backup pings a secret address. We alert you when it goes quiet.
DNSPro and up
Checks that a DNS record still returns what you expect.
APIPro and up
Calls an endpoint with your method, headers and body, and checks the response.
Incoming alertsPro and up
Datadog, Grafana, Alertmanager, CloudWatch or any webhook raises an incident here, and your responses can act on it.
As often as every 15 seconds
Faster on paid plans, and a monitor that is down is checked again sooner, so you see it recover quickly.
From up to 10 regions
A site is only called down when most of your chosen regions agree, so one bad route never wakes you up.
Failures are confirmed
A failed check is re-checked before an alert goes out, and you hear again when it recovers, with how long it was down.
Expiry reminders
Warnings before an SSL certificate or a domain registration runs out, not after.
Marketing site
example.com
- Uptime
- 99.97%
- Response
- 231 ms
- Check every
- 1 min
Last 60 days
Response time, last 24 hours
Watch it, hear about it, respond to it
One place for the whole loop, from the first failed check to the action you take.
Watch
Checks that run from the places you pick, and confirm a failure before they make a noise.
- Websites, keywords, ping, ports, DNS, APIs and heartbeats
- Check from several regions, or from fixed addresses you can allow in a firewall
- Warnings before an SSL certificate or domain expires
Hear
Your other tools already know things your checks cannot. Let them raise incidents here too.
- Alerts from Datadog, Grafana, Alertmanager, CloudWatch or any webhook
- One place for every incident, with a timeline and who handled it
- Alerts kept apart from downtime, so uptime figures stay honest
Respond
Say once what should happen, and it happens every time, the way you wrote it.
- Tell the owning team, escalate if nobody acts, post to chat or your own URL
- Block an attacker at your firewall straight from the alert
- Practice mode, approvals and limits, so automation never surprises you
Trouble comes in waves
An attack or an outage rarely arrives as one event. It builds, peaks and fades. A response written ahead of time meets it at the right moment, and puts everything back afterwards.
It builds: an alert arrives
A check fails, or a tool such as Datadog raises an alarm. An incident opens and the right people are told.
It peaks: your response runs
Escalate, post to chat, call your system, or block the address at the firewall, exactly as you wrote it.
It fades: it puts things back
Blocks expire on their own, a recovery notice goes out, and the timeline keeps the record.
Inbound alerts that actBusiness and up
An alert from anywhere can stop an attack, not just report one
Most tools stop at a notification. UptimeWave treats an alert from your other systems as the start of a response: it opens an incident, runs the rules you wrote, and can block the address behind it at your firewall.
- Cloudflare and AWS WAF. Add an address to a list or IP set for a set time, then remove it again.
- Practice first. A practice run shows what it would block and blocks nothing.
- You stay in charge. Run automatically, or ask a person to approve each one. A never-block list and an hourly cap protect your own traffic.
1. Send us the alert
Point Datadog, Grafana, Alertmanager, CloudWatch or any tool that can call a webhook at a private address we give you. We show exactly what to paste.
2. We read it for you
We pull out the title, how serious it is and, when the alert has one, the source address. Anything you want can be mapped by hand.
3. A response acts
Your rules decide what happens: notify a team, call a webhook, or add the address to a Cloudflare list or an AWS WAF IP set.
4. It cleans up after itself
Blocks expire on their own after the time you set, and every block is listed with who approved it and when it ended.
Connected to the tools you already use
Alerts flow in from your monitoring stack, out to your team's chat and phones, and into the systems that can act on them.
Alerts come in
Our own checks and the tools you already run all raise incidents in the same place.
- UptimeWave
- Datadog
- Grafana
- Alertmanager
- Amazon CloudWatch
- Any tool with a webhook
Incoming alerts start on Pro.
Alerts go out
The right people hear about it where they will actually see it.
- SMS
- Voice calls
- Slack
- Microsoft Teams
- Discord
- Telegram
- Google Chat
- Mattermost
- PagerDuty
SMS, voice and chat apps start on Pro. Email is on every plan.
Actions happen
Your responses reach into the systems that can stop the problem.
- Cloudflare IP lists
- AWS WAF IP sets
- Your own URL, as a webhook
Automatic responses start on Business.
Product names belong to their owners and are used only to say what connects. No affiliation is implied.
Start from a playbook
Pick a ready-made response, change what you like, and apply it to every monitor, a team or a group.
Escalate if nobody acts
Still open after 30 minutes? Tell the on-call team.
Recovery notice
Post to a chat channel the moment an incident ends.
Expiry heads-up
A certificate or domain is close to expiring: tell the people who renew it.
Call your own system
Post a JSON message to your ticketing or automation URL.
Block attacker addresses
Add the address in an alert to your WAF list for an hour.
And the parts teams ask about
What turns monitoring into something a whole company can use.
Status pages
A public page with uptime, announcements and email updates, in your colors.
Monthly uptime reportsPro and up
Every monitor's month at a glance, as a page, a CSV and an email on the first.
On-call schedulesBusiness and up
Rotate who is on call, cover a shift, and page the right person if an incident drags on.
Teams and accessPro and up
Each team gets its own monitors, alerts and area of the app.
Single sign-onEnterprise and up
Sign in with Okta, Entra, Google or any OpenID Connect provider, and require it for your team.
Approve from SlackEnterprise and up
A response that needs a person waits in your channel with Approve and Reject buttons.
Maintenance windows
Planned work stays out of uptime figures and wakes nobody.
Fixed check addresses
A published list of the addresses our checks come from, for your firewall.
An API
Create and read monitors from scripts and your CI.
Alerts everywhere
Email, SMS, voice and chat apps such as Slack, Teams and Discord.
Pricing
Start free. Upgrade when you need faster checks, more people or automatic responses.
Pro
$25 / month
Billed yearly, $300
Start with Pro- 50 monitors
- Checks every 1 minute
- 2 team members
- 3 status pages
- 1 year of history
Business
$55 / month
Billed yearly, $660
Start with Business- 150 monitors
- Checks every 30 seconds
- 5 team members
- 100 status pages
- 2 years of history
Enterprise
$125 / month
Billed yearly, $1,500
Start with Enterprise- 500 monitors
- Checks every 15 seconds
- 25 team members
- 1,000 status pages
- 3 years of history