Data location stated in Monitoring and observability
Where the data physically sits decides which law applies to it.
- 14Published
- 28Vendors measured
- 50%Of those measured
- 2026-08-31Checked
50% here against 56% across every category we measure. Monitoring and observability sits below the overall share for this criterion.
Back to Data location stated across all categories, or to Monitoring and observability.
Published
The hosting location is stated on a public page.
No statement about data location 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 | 7 addresses checked |
| Bugsnag | 7 addresses checked |
| Dynatrace | 7 addresses checked |
| Highlight | 7 addresses checked |
| Last9 | 7 addresses checked |
| Logz.io | 7 addresses checked |
| Pingdom | 7 addresses checked |
| Raygun | 7 addresses checked |
| Sematext | 7 addresses checked |
| SigNoz | 7 addresses checked |
| Site24x7 | 7 addresses checked |
| Splunk | 7 addresses checked |
| StatusCake | 7 addresses checked |
| Zabbix | 7 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 |
|---|---|
| Cronitor | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured. |
| 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.