Atlassian Statuspage and Fehlo compared.
Statuspage is strong at incident communication but checks nothing itself. At Fehlo, uptime monitors fill the status page. Here is what each can and can't do.
Facts about Statuspage as of 24 October 2026; sources are listed below. If you spot a mistake, write to hallo@fehlo.de and we will fix it.
Atlassian Statuspage is a mature incident communication tool: publish incidents from templates, notify subscribers by email, SMS and webhook, embed third-party components. But it checks nothing itself. The status comes from other tools, an email automation or the API.3 Fehlo works the other way round: monitors check, and the status page shows their results.
Side by side
| Topic | Fehlo | Statuspage |
|---|---|---|
| Monitoring | included: HTTP, ping, TCP, SSL, domain, heartbeat | none; status through integrations (such as PagerDuty, Opsgenie), email or API3 |
| Free status page | yes, with logo, 20 monitors included | yes, 100 subscribers, 25 components, no custom domain12 |
| Custom domain | from Team: €29 a month, with 150 monitors and error monitoring | from Hobby: $29 a month12 |
| Subscriber notifications | no (in progress) | email from Free, SMS and webhook from Startup ($99)1 |
| Manual incident posts | no (in progress) | yes, with templates1 |
| Scheduled maintenance | yes | yes1 |
| Restricted pages | yes, members of your organisation only, on every plan | private pages from $29, audience-specific from $3001 |
| Data location | Germany (Hetzner, Nuremberg) | not stated; Statuspage is not among the Atlassian products with data residency4 |
Fehlo prices net, plus VAT.
When Statuspage fits better
- You communicate incidents actively: write posts, add updates, notify thousands of subscribers by email or SMS. Fehlo can't do that today.
- You already have a monitoring or incident tool (PagerDuty, Opsgenie, Datadog) and only need the communication part.
- You need pages for specific customer groups with single sign-on.
When Fehlo fits better
- You want the status page to be right on its own, because the monitors fill it.
- You want a custom domain without paying for the status page alone: Fehlo Team includes 150 monitors and error monitoring.
- You're an agency and want status pages in your clients' names, with no vendor branding (Agency plan, €79).
- Data and contract partner should be in Germany. A status page with subscribers processes email addresses, so location matters.
Switching
Create a monitor for each component, build the status page from them and point your CNAME record at Fehlo. Fehlo checks it and fetches the certificate itself. Subscribers and incident history don't move. Details under uptime monitoring and status pages.
Sources
- Atlassian Statuspage pricing, atlassian.com/software/statuspage/pricing, retrieved 24 October 2026. Prices in US dollars.
- Atlassian Support, "Set a custom domain and SSL", support.atlassian.com, retrieved 24 October 2026.
- Atlassian Support, "Know when to automate your status page", support.atlassian.com, retrieved 24 October 2026.
- Atlassian Support, "Understand data residency", support.atlassian.com, retrieved 24 October 2026.
Atlassian and Statuspage are trademarks of Atlassian. Fehlo is not affiliated with Atlassian.
Questions
Can Fehlo notify subscribers during incidents?
Not yet. Subscribers and manual incident posts are in progress. Today Fehlo notifies your team by email, Microsoft Teams, Discord, Google Chat, ntfy, Zulip or webhook.
Does Statuspage check my services?
No. According to Atlassian, Statuspage doesn't ping your servers or endpoints. You set the status by hand, by email, through the API or through integrations.
Can the status page run on my domain?
At Fehlo from the Team plan, on a subdomain such as status.yourcompany.com. Fehlo fetches the HTTPS certificate itself.