Upptime vs Instatus: privacy compared
Upptime and Instatus are both rated in status pages and uptime monitoring against the same 7 public criteria. Upptime does better on open source, no trackers or telemetry and runs on your own infrastructure.
| Criterion | Upptime Our pick | Instatus |
|---|---|---|
| Grade | Grade B B (78/100) | Grade F F (31/100) |
| Jurisdiction | Unknown | Unknown |
| Open source Is all the source code needed to run the product public? | Yes source | No |
| No trackers or telemetry Are the website and apps free of third-party trackers, with any analytics anonymous and any telemetry off by default? | Partial source | No |
| No ads or data sales Is the product funded without advertising, ad targeting or selling user data? | Yes source | Yes source |
| Independent audit Has an independent security or privacy audit been published within the last three years? | No | No |
| Runs on your own infrastructure Can it run entirely on your own infrastructure or repository, without a vendor account? | Yes source | No |
| No visitor tracking Is the public status page free of third-party trackers and analytics? | Yes source | Yes source |
| Public uptime history Does it publish response times and incident history? | Yes source | Yes source |
Summaries
Upptime. Upptime scores 78 out of 100 (grade B) on the status pages and uptime monitoring criteria. It meets 5 of 7 criteria: open source, no ads or data sales, runs on your own infrastructure, no visitor tracking and public uptime history. It partly meets no trackers or telemetry. It does not meet independent audit.
Instatus. Instatus scores 31 out of 100 (grade F) on the status pages and uptime monitoring criteria. It meets 3 of 7 criteria: no ads or data sales, no visitor tracking and public uptime history. It does not meet open source, no trackers or telemetry, independent audit and runs on your own infrastructure.