detectdown
Verdicts use cached measurements from the named testing area, not a visitor-triggered local check. testing evidence tested from Chicago tested from Chicago

Privacy

detectdown is built to answer outage questions without tracking people. We use only the data needed to match existing cached measurements to your location, keep the service from being abused, and understand aggregate product usage.

IP addresses

Your IP is used once in memory, then dropped. Never stored, never shared.

When you load a page, your IP address is used only for one in-memory geolocation lookup. When you submit the API early-access form, sign in with an AI assistant, or register an AI-assistant connector, a short-lived abuse-control counter also uses the IP address. The counter is keyed by a hash of the address, not the raw address.

We do not write visitor IP addresses to disk. We do not send them to the third parties who run our measurements. Page views read cached measurements; they do not send visitor-IP-derived continent, country, city, or ASN targeting to measurement networks.

API early-access emails

The paid API early-access form asks for a work email so we can follow up about API access.

When you submit it, detectdown stores the normalized email address with the form source and timestamp. We use it to follow up about paid API early access. We do not sell it or share it with measurement networks.

Browsing public status pages does not require submitting an email.

MCP sign-in

AI-assistant connectors store only the account data needed to sign in and improve the connector.

When you connect an AI assistant over MCP, detectdown stores your verified email address and keeps a record of each tool call: which tool ran, which monitored service it was about, the service text you asked for when it matches nothing we track, the optional location you provided, the outcome, and when it happened. We use that data so the connector can authenticate and so we can understand which monitored services people ask about.

During sign-in, detectdown sets a 90-day verified-email cookie so returning users can skip re-verification. It is a sign-in convenience, not a tracking cookie.

Email codes, authorization codes, and rotated refresh tokens are pruned automatically. Browsing public status pages does not require sign-in.

Analytics

First-party, privacy-friendly, cookieless analytics.

The site uses first-party, privacy-friendly, cookieless analytics. It sets no tracking cookies and collects no personal data, only aggregate page views and a few product events.

Trackers

No third-party trackers.

detectdown does not run advertising pixels, social widgets, fingerprinting scripts, or third-party tracking tags. The site uses self-hosted fonts and first-party analytics only.

GeoLite2 data created by MaxMind, available from maxmind.com.