Solo
Side projects and single services.
$9 per month
- 10 checks, 60 second interval
- Email and Slack alerts
- 7 day history
Checks from 14 regions
Tideline pings your endpoints every ten seconds from fourteen regions, confirms a failure from a second region before it wakes anyone, and posts to your status page automatically.
checks:
- name: api-gateway
url: https://api.example.com/health
every: 10s
expect: 200
confirm_from: 2 # regions
notify:
- pagerduty://on-call-primary
- slack://#incidents
How it works
A URL and an expected status code is enough. Add headers, a request body or a response assertion if you need them.
Route by check, by tag or by time of day. Escalation is a list, not a rules engine you have to learn.
Failures that survive confirmation post automatically, with the region and the response that failed.
Confirmation, not noise
A single region failing is usually the region, not you. Tideline requires a second region to agree before it pages anyone.
Every alert carries the failing region, the last successful check, the response code and body, and a link to the timeline. No log spelunking at 3am.
Features
Status codes, response assertions, TLS expiry and raw port checks.
Heartbeat URLs that alert when a scheduled job stops calling home.
Hosted or on your own domain, updated from the same incident record.
Ordered lists with per-step delays. PagerDuty, Slack, SMS, webhook.
Mute by check or by tag, scheduled ahead or started from the API.
Every check result available as CSV or over the API. Your data leaves when you do.
Pricing
Invite the whole team on any plan. We charge for what we run, not who looks at it.
Side projects and single services.
$9 per month
Production services with an on-call rota.
$49 per month
Multiple products and environments.
$199 per month
| Feature | Solo | Team | Scale |
|---|---|---|---|
| Checks | 10 | 100 | 1,000 |
| Interval | 60s | 10s | 10s |
| Escalation | Not included | Included | Included |
| Status pages | Not included | 1 | Unlimited |
| SSO | Not included | Not included | Included |
Questions
No. A check has to fail from two regions before an alert is raised, which removes almost all single-region noise.
Yes, on Team and above, using an agent you run inside the network. It polls out, so no inbound firewall rule is needed.
Existing checks keep running. New ones are refused with a clear error until you remove one or move up a plan.
Everything in the dashboard is an API call, including creating checks, starting maintenance windows and exporting results.
Free for 14 days. No card, no sales call, no onboarding sequence.