Status page with history in Monitoring and observability
A status page without past incidents tells you nothing about reliability.
- 14Published
- 29Vendors measured
- 48%Of those measured
- 2026-08-31Checked
48% here against 49% across every category we measure. Monitoring and observability sits below the overall share for this criterion.
Back to Status page with history across all categories, or to Monitoring and observability.
Published
A public status page with incident history.
No public status page found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Better Stack | 3 addresses checked |
| Checkly | 3 addresses checked |
| Chronosphere | 3 addresses checked |
| Coralogix | 3 addresses checked |
| Cronitor | 3 addresses checked |
| Dynatrace | 3 addresses checked |
| Highlight | 3 addresses checked |
| Last9 | 3 addresses checked |
| Middleware | 3 addresses checked |
| Pingdom | 3 addresses checked |
| Sematext | 3 addresses checked |
| SigNoz | 3 addresses checked |
| Site24x7 | 3 addresses checked |
| Splunk | 3 addresses checked |
| Zabbix | 3 addresses checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| Graylog | The vendor’s server blocked or rate-limited our crawler, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.