Home / Website and service monitoring for IT teams
External checks from outside your network, incidents that name the cause, and a public status page your users can subscribe to.
The problem
Internal monitoring says everything is green while the public site is unreachable, the certificate expired, or DNS was changed by someone else. You need an outside view that pages the right person.
What you get
Checks run from outside your network, so a broken firewall rule, an expired certificate or a DNS change shows up the way your users see it.
PagerDuty, Opsgenie, SIGNL4, Microsoft Teams, Slack, Mattermost, Rocket.Chat, Google Chat, ntfy, Pushover, e-mail and signed webhooks. Escalation to contacts when nobody acknowledges.
Public or on your own domain, with subscriber e-mails on change, maintenance windows that do not raise alerts, and incidents that explain themselves.
HTTP monitor · checked every 30s
Current status
OPERATIONAL
HTTP 200
Avg. response (24h)
29ms
Fast
Last check
36ms
AVG 24H 29 ms · 2026-08-10 15:23:30
Speed pulse
Last 7 days
Auto-scaled to 145ms · 2488 checks
Alert channels
Downtime, SSL and keyword alerts go to every connected channel the moment a check fails — and again on recovery.
White-label branding
One place to control how your public status pages and client reports look. These settings apply to every status page you own.
Live preview
Accent colour, buttons and links use this shade.
Company name
Shown in the status page header and client reports.
Header tagline
Brand colour
Font family
Custom domain
Point a CNAME at errordetector.eu and the page answers on your address.
Screens are rendered from markup with sample data, not screenshots of a customer account.
Which plan
100 monitors, 60-second checks, all channels, login seats for the team, white-label status pages. Every number is on the plan table; start on Free and upgrade when you need it.
Not from ErrorDetector: checks come from one public origin and private addresses are refused by design. Use a heartbeat monitor from inside the network instead: the job pings us, and silence raises the alert.
Down means the target was unreachable and opens an incident that counts against uptime. Issue means it answered but a check failed (a 5xx, a missing keyword, a slow response, an expiring certificate). Both alert; only down moves the uptime number.
Not on the self-serve plans. Enterprise is agreed per contract; talk to us.