Operations · Uptime Monitoring
We call your website. From 3 datacenters.
HTTP availability, response time and TLS certificates — checked from Frankfurt, Falkenstein and Nürnberg. An outage only counts when the majority sees it: false positives from local network issues do not stand a chance.
60s
interval
3
locations
2 of 3
quorum
30 days
history
Illustration — the marketing page above shows live status of all 3 locations.
Multi-location monitoring
Measured from 3 datacenters in Germany
Frankfurt am Main, Falkenstein and Nürnberg measure independently. An outage only counts as down when a majority of locations sees it — network false positives never reach your inbox. And if our main system fails, the satellites keep alerting.
Frankfurt am Main
Checking status…
Falkenstein
Checking status…
Nuremberg
Checking status…
Features
Measure availability — without false alarms
HTTP checks
GET/HEAD/POST with expected status code and timeout — from 60 second intervals, configurable per monitor.
TLS certificates watched
Expiry of every HTTPS endpoint is monitored — email alert X days before expiry, you choose.
Response time charts
Latency over time (min/avg/max) across 24 hours, 7 and 30 days — regressions visible immediately.
Uptime bars & history
Status-page-style availability bars and percentages — from real measurements, never estimated.
Incident log with duration
Every status change logged with timestamp and outage duration — ongoing incidents highlighted.
Instant alerts, no spam flood
Email only on status changes — transitions, not state spam. Includes recovery mail.
Set up in 1 minute
How your URL gets monitored
Enter the URL
Name, URL, interval (60s to 1h) and whether TLS should be checked — that is all.
3 locations measure
Frankfurt, Falkenstein and Nürnberg check the URL independently at your chosen interval.
Majority decides
We only alert when 2 of 3 locations see “down”. Local network issues filter themselves out.
Alerts
Instant email on every status change
With outage duration and cause (HTTP code or error). No newsletters, no noise — just your monitors.
- Down: page unreachable — with HTTP code or error message
- Up: back online — including “X minutes of downtime”
- TLS warning: certificate expires in X days (you choose, default 14)
- Alerts come from 3 datacenters — even if provider.tools itself fails
alerts@provider.tools → du@firma.de
🔴 testpage.com is unreachable
The monitored URL https://testpage.com has been unreachable since 16:00. Cause: HTTP 503 — Service Unavailable. You will receive an all-clear as soon as it responds again.
Quorum: 2 of 3 locations reported down
FAQ
Häufige Fragen
What is checked?
HTTP status code against your expected value, response time and — for HTTPS — the TLS certificate expiry date.
Why 3 locations?
Because “unreachable” can mean two things: the site is down — or only the route from the checker to the site is broken. Our locations in Frankfurt, Falkenstein and Nürnberg measure independently: we alert only when the majority sees “down”.
When do I get an email?
Instantly on every status change: down and recovery, including outage duration. Optionally before TLS certificate expiry. No state spam — transition-based with throttled reminders.
How fast are outages detected?
In the next check interval — from 60 seconds. The majority decision needs results from at least 2 locations; the satellites measure at the same cadence.
What happens if provider.tools itself goes down?
The satellites in Falkenstein and Nürnberg keep measuring autonomously, buffer results and alert on their own. Everything is backfilled after recovery — history without gaps.
Where do the uptime percentages come from?
From real checks: 24h from raw data, 7 and 30 days from hourly aggregates — combined across all locations.
Your website, monitored from 3 datacenters.
Enter the URL, done. False alarms excluded, outages detected within a minute. Email alerts from Pro.