Status page with history in Network connectivity
A status page without past incidents tells you nothing about reliability.
1 of 8 companies we measured here publish it, that is 13%. Last checked 2026-09-30.
13% here against 18% across every category we measure. Network connectivity sits below the overall share for this criterion.
This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.
Back to Status page with history across all categories, or to Network connectivity.
Published
A public status page with incident history.
| Vendor | What we found |
|---|---|
| ngrok | https://status.ngrok.com/ |
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 |
|---|---|
| localhost.run | 3 addresses checked |
| Netmaker | 3 addresses checked |
| Packetriot | 3 addresses checked |
| Pangolin | 3 addresses checked |
| Pinggy | 3 addresses checked |
| Router Architects | 3 addresses checked |
| ZeroTier Central | 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.
None. Every vendor here was measured for this criterion.
Other criteria in Network connectivity
- Data processing agreement
- Data location stated
- Public pricing
- Certifications named
- Uptime SLA with a figure
- HTTPS enforced with HSTS
- No third-party tracking before consent
- security.txt (RFC 9116)
- Notice before subprocessors change
- Named privacy contact
Status page with history in related categories
Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.