Submit a tool

Search iThub

Search tools, categories and collections. Type at least two characters.

Explore all tools
↑ ↓ to explore resultsEnter to open · Esc to close

Uptime Monitoring & Status Pages

Uptime monitoring, alerting and public status pages for websites, APIs and services.

Choosing guide

5 results in Uptime Monitoring & Status Pages

Active Pro listings from this category appear first. Your sort applies within Pro and Free results.

Advertisements
Advertisements
Focused collections

Shortlists for Uptime Monitoring & Status Pages

Explore collections with tools relevant to this category, grouped by deployment, source model or workload.

Open-source network monitoring tools →

2 matching tools from this category

Self-hosted monitoring tools →

3 matching tools from this category

How to choose uptime monitoring & status pages tools

Uptime monitoring tools probe websites, APIs, ports and servers from outside at regular intervals and alert someone when a check fails or slows down. Status pages publish that availability to customers and staff, together with incident updates and planned maintenance notices. They answer whether a service is reachable, while full observability platforms dig into metrics, traces and logs to explain why it failed.

Read the guide

Who uses these tools

  • SRE and on-call engineers responsible for availability
  • Small teams monitoring a handful of websites
  • Support managers communicating incidents to customers

Capabilities to compare

  • HTTP, TCP, ping, DNS and keyword checks
  • Check frequency and multi-region probe locations
  • Alert channels, escalation and on-call schedules
  • Hosted status pages with incident history
  • SSL certificate and domain expiry warnings

Operating considerations

  • Self-hosted monitors fail together with the network they watch
  • Pricing by number of monitors and check interval
  • Custom domain and branding on status pages
  • False alerts from a single probe location

Selection checklist

  1. Count the endpoints you need to watch and the shortest interval required, then compare plans on that basis.
  2. Confirm alerts require failures from several locations before paging anyone at night.
  3. Check that the status page stays online when your own infrastructure is down.
  4. Test every alert channel your team uses, including phone calls and chat integrations.

What belongs in this category: A product fits here when external availability checks, alert routing or public status communication are its core features, rather than deep application performance tracing or log analysis.

Uptime Monitoring & Status Pages on iThub in figures

iThub lists 5 tools in Uptime Monitoring & Status Pages. 4 of 5 are open source, 4 of 5 can be self-hosted, 5 of 5 have a free, freemium or open-source pricing model and 4 of 5 offer an API.

Tools listed
5
Open source
4
Self-hostable
4
Free to start
5
With an API
4
Web app
4
Desktop app
1

Recently added: OneUptime, Checkmate, Better Stack, Cachet

Typical use cases

  • Paging the on-call engineer when the checkout API stops responding
  • Publishing a public status page during a hosting outage
  • Warning before TLS certificates or domains expire
  • Monitoring internal services in a home lab

Trade-offs to model

  • Self-hosted monitors are free and private, but need a second location so they are not down with your services.
  • Combined monitoring and incident suites reduce tool count, while standalone checkers stay simpler and cheaper.

Common mistakes

  • Hosting the status page on the same server it reports on, so it disappears during outages.
  • Setting one-minute checks with single-failure alerts and training the team to ignore pages.

Browse all uptime monitoring tools →Explore monitoring and observability →Browse self-hosted monitoring tools →

Decision resources

Continue the technical evaluation

Use the resources that match your decision stage. Profile data and linked sources were refreshed through November 11, 2026.

Evaluation methodology · Corrections process