-
api.alidade.net
Operational
212 ms from Frankfurt, 99.98% over 90 days
-
p95 response, all cities
184 ms
-
Frankfurt
41 ms
12 probes, all passing
-
Edge nodes
- ams123 ms
- fra231 ms
- sin1212 ms
- sfo358 ms
-
São Paulo
118 ms
8 probes, all passing
-
Checks in the last minute
41,206
Alidade, uptime and network monitoring. From $29 a month.
Know when a region goes quiet. Uptime checks from 26 cities, every 10 seconds.
Alidade runs HTTP, TCP, DNS and TLS checks from probes in 26 cities and compares them before it alerts, so a slow route out of São Paulo is not a false alarm from Frankfurt. When something fails, it pages one person with the failing hop, not a channel with a graph.
- 26 probe cities
- 10 s between checks
- 14 s median time to page
Checked from 26 cities, confirmed before anyone is paged
Every monitor runs from at least three cities at once. A failure seen from one city is checked again from two others within 6 seconds, and only then does Alidade page you. The numbers below are from October 2026.
- Probe cities
- 26
- Amsterdam, Frankfurt, London, Paris, Stockholm, Warsaw, Toronto, New York, Ashburn, Chicago, Dallas, Los Angeles, Mexico City, São Paulo, Santiago, Johannesburg, Lagos, Dubai, Mumbai, Singapore, Jakarta, Tokyo, Seoul, Sydney, Auckland and Rotterdam.
- Check types
- 7
- HTTP and HTTPS with keyword and JSON assertions, TCP, ICMP, DNS, TLS certificate expiry, and a traceroute from every city on failure.
- Interval
- 10 s
- 30 seconds on Solo, 10 seconds on Team, and 1 second bursts for up to 5 minutes on Fleet.
- Median time from failure to page
- 14 s
- Measured from the first failed check to the delivered page, including the confirmation from two more cities.
- Checks run in October
- 4.1 billion
- 99.997% of them ran within 1 second of schedule. The rest were late by a median of 2.3 seconds.
- History kept
- 13 months
- Raw check results and traceroutes. Incident records are kept for the life of the account.
Three plans, priced per account, not per seat
Start on any plan free for 30 days. Monthly or yearly, cancel from settings. Prices in USD, excluding VAT.
| Plan | Solo | Team | Fleet |
|---|---|---|---|
| Price | $29per month | $79per month | $240per month |
| Monitors | 20 | 100 | 1,000 |
| Check interval | 30 seconds | 10 seconds | 10 seconds, with 1 second bursts |
| Probe cities | 8 | 26 | 26, plus your own private probes |
| Team members | 1 | 10 | Unlimited |
| Status pages | 1 | 3 | 20, on your own domain |
| Phone and SMS alerts | Email and webhooks only | Included, 100 a month | Included, unlimited |
| History | 3 months | 13 months | 13 months |
| Support | Email, next business day | Email and chat, same day | Phone, within 1 hour, around the clock |
| Start Solo free | Start Team free | Start Fleet free |
- What counts as a monitor?
- One URL, host or DNS name checked on one interval. A monitor checked from 26 cities is still one monitor.
- Do you page on the first failed check?
- No. The failing city asks two others to check within 6 seconds, and you are paged only if they agree. False pages were 0.4% of all pages in October.
- Can I run a probe inside my own network?
- On Fleet, yes. The probe is a 9 MB binary for Linux that reports to the same account and shows up as one more city.
Try it on your own endpoints
Add a URL and Alidade starts checking it from 26 cities within a minute. No card for 30 days, and one email with a login link, nothing else.
Alidade status
All 26 probe cities are running. In the last 90 days, 99.997% of checks ran within 1 second of schedule. Incidents and changes from the last two months are listed below; get status updates by email.
Slower checks from São Paulo
For 41 minutes, checks from the São Paulo probes took up to 3 seconds longer than usual. Results were confirmed from Santiago and no false pages were sent.
Resolved
Status page images
Logos on customer status pages failed to load for 12 minutes after a CDN configuration change. Checks and alerts were not affected.
Resolved
Tokyo probe moved
The Tokyo probe moved to a new provider. 6 minutes without checks from Tokyo, covered by Seoul and Singapore.
Maintenance
SMS delays in Australia
A carrier delayed SMS alerts to Australian numbers by up to 9 minutes for 2 hours. Phone calls and push alerts were on time.
Resolved
TLS expiry warnings at 14 days
Certificates that expire within 14 days now raise a warning on every plan, 30 days on request.
Change