Our Team

Is it down checker is built and maintained by a small team of engineers passionate about uptime transparency and public accountability on the web. We believe everyone deserves a fast, accurate answer to the question: "is this site down, or is it just me?"

Who We Are

Our team combines backgrounds in systems engineering, web performance, and SRE (site reliability engineering). Collectively we've operated production infrastructure at scale and understand exactly what "down" means — whether it's a DNS failure, a CDN issue, a regional outage, or a full-stack collapse.

Engineering

Operates the monitoring fleet, builds the dual-signal detection pipeline, and keeps the API fast and reliable 24/7.

Editorial

Curates the site database, reviews user-submitted reports, and ensures our methodology and documentation stays accurate and up to date.

Editorial Standards

Everything we publish — status pages, outage reports, methodology explanations — follows four rules:

  1. Accuracy over speed. A status is only marked "down" when our automated HTTPS checks confirm it, and confirmations require at least two consecutive failures to avoid false positives from transient network glitches.
  2. Signal separation. We clearly distinguish between server-side detection ("our servers can't reach this site") and crowd-sourced reports ("users are reporting issues"). Both are shown so readers can judge for themselves.
  3. No affiliate bias. We don't accept payment to list, delist, or change the status of any website. Monitoring is automated and uniform across all 2,700+ tracked domains.
  4. Privacy first. We don't track users, don't require accounts, and hash IP addresses before storing them. Full details in our Privacy Policy.

How We Verify Claims

Every status shown on Is it down checker is based on measurable data:

  • Automated HTTP/HTTPS probes with timestamps and response codes
  • DNS resolution checks against public resolvers
  • Time-to-first-byte (TTFB) latency measurements
  • Crowd-sourced reports compared against a 7-day rolling baseline

We publish our full approach on the Methodology page so readers can audit how we arrive at each verdict.

Contact the Team

Have feedback, a correction, or a tip about an outage we missed? We read every message.

Contact Us