Uptime monitoring and status pages.
Fehlo checks your websites, servers, certificates and cron jobs and shows your customers what is up on a status page. In the same product as your errors, on a server in Nuremberg, and included in every plan.
What Fehlo checks
| Monitor | checks | alerts |
|---|---|---|
| HTTP | GET or POST with your own headers and body, status code, response time | on downtime, and when responses stay above your limit several checks in a row |
| Ping | ICMP to a host or IP address | when there is no reply |
| TCP | whether a port is reachable, such as a database or mail server | when the connection fails |
| SSL certificate | validity, issuer, expiry date | 14 days before expiry, adjustable per monitor |
| Domain | status and expiry date via RDAP | when expiry is close; DENIC publishes no expiry date for .de domains |
| Heartbeat | whether your cron job or backup calls a URL | when the call does not arrive within the interval plus grace period |
Alerts go out by email, Microsoft Teams, Discord, Google Chat, ntfy, Zulip or webhook, and again when the service is back. During deployments you pause a monitor for 10, 30 or 60 minutes or until you resume it, in the interface or through the API with a token from your deploy script.
Today Fehlo checks from one location, in Nuremberg. If the connection to it fails, a monitor can turn red by mistake.
Status pages
From your monitors you build status pages for your customers or your team:
- public, or for members of your organisation only,
- with history as daily bars over 30, 60 or 90 days, uptime in percent, response times and a list of outages,
- with scheduled maintenance, during which checks and alerts pause,
- with your logo for light and dark, favicon, accent colour, a header button and links to your imprint and privacy policy,
- in German or English, following the browser language or fixed,
- without fonts or scripts from third parties.
Your own domain
From the Team plan. Add a CNAME record from, say, status.yourcompany.com to the address Fehlo shows you (sp-<token>.fehlo.de). Fehlo checks the record and gets the HTTPS certificate from Let's Encrypt itself. This works with subdomains only, not with the bare yourcompany.com, because DNS does not allow a CNAME there.
For agencies
On the Agency plan, status pages carry no mention of Fehlo and you can add your own CSS. That lets you run status pages in your clients' name, with their logo on their domain.
Not there yet
- subscribers who get an email when something breaks
- incident posts you publish on the status page by hand
- checks from a second location
- on-call with phone calls or SMS
What it costs
Uptime monitors and status pages are included in every plan, the free one too. Uptime checks and heartbeat pings don't count against any allowance. What differs between plans is the number of monitors and how often they can check:
| Plan | monitors | shortest check interval |
|---|---|---|
| Free, €0 | 20 | 5 minutes |
| Solo, €9 a month | 50 | 1 minute |
| Team, €29 a month | 150 | 1 minute |
| Agency, €79 a month | 500 | 1 minute |
HTTP, ping, TCP and heartbeat monitors count. SSL and domain monitors don't count and are unlimited on every plan. How often your cron job sends a heartbeat makes no difference: the pings are free.
Status pages with your logo are on every plan. A custom domain for a status page comes with Team; status pages without Fehlo branding and with your own CSS are on the Agency plan. All prices net, plus VAT.
When your quota for errors is used up, Fehlo gradually stops accepting new data. Your uptime monitors keep checking and alert you about outages as usual.
For comparison: Sentry includes one uptime monitor on every plan and charges $1 a month for each additional one.1 We found no status pages in Sentry.2
Sources
- Sentry pricing page, sentry.io/pricing, retrieved 21 October 2026. Prices in US dollars, excluding tax.
- Sentry documentation, "Uptime Monitoring", docs.sentry.io/product/uptime-monitoring, and changelog, sentry.io/changelog, retrieved 21 October 2026. We found no customer-facing status pages there.
Sentry is a trademark of Functional Software, Inc. Fehlo is not affiliated with Sentry.
Questions
Do I need an SDK for this?
No. Uptime monitors and status pages work without an SDK. For heartbeats your cron job calls a URL; Fehlo shows you the line for curl and crontab.
Can the status page run on my domain?
Yes, on a subdomain such as status.yourcompany.com. You add a CNAME record, Fehlo checks it and takes care of the HTTPS certificate.
Do uptime checks count against my quota?
No. The event quota covers errors only, and transactions and log lines have their own allowances. Uptime checks and heartbeat pings don't count, and when the quota is used up your monitors keep checking.
What happens to my monitors if I move to a smaller plan?
They keep running as before, at their current interval. You can add new monitors once you are below the new plan's limit.
Where does Fehlo check from?
From Nuremberg, from one location.
Can I silence alerts during a deployment?
Yes. Pause a monitor for 10, 30 or 60 minutes or until you resume it, also through the API from your deploy script. On status pages you schedule maintenance in advance.