About the service

Independent uptime monitoring, with the evidence always visible.

DownDetector.me answers one question instantly: is this website down right now? We run external HTTPS checks from independent infrastructure every 5 minutes, record every result, and show you a clear timeline so anyone can understand whether a service is healthy, degraded, or offline — without needing to sign up or trust a vendor's own status page.

14,051+

Monitored

6,743

Operational

7,308

Down now

Why independent monitoring matters

A website can appear healthy to one person and broken to another depending on geography, ISP routing, DNS caching, or CDN edge-node health. A service's own status page is written by the same team experiencing the outage — which means it is often updated late or understated.

DownDetector.me adds a second source of truth that is completely outside the service owner's infrastructure. That matters when users need to quickly confirm whether an issue is on their end or the provider's, compare downtime patterns over weeks, or demonstrate an SLA breach with timestamped evidence.

How we monitor

01 · Probe

External HTTPS check

We open a direct HTTPS connection to the public domain from our server, record the HTTP status code, total response time in milliseconds, and whether the request completed at all. No browser, no JavaScript rendering — just the raw server response.

02 · Classify

Operational vs outage

HTTP 2xx and 3xx responses are classified as Operational. Connection failures, DNS errors, TLS handshake failures, timeouts, and 4xx/5xx responses are classified as Down. We do not follow redirects that point outside HTTPS to prevent SSRF risks.

03 · Record

History & timeline

Every result is stored with a precise timestamp. Status pages show a 48-check sparkline, a 30-day uptime percentage, and the exact HTTP code returned so you can see exactly when a service degraded and how long the outage lasted.

How we handle timeouts

A timeout is a real failure, not an ambiguity. If a server does not respond within 10 seconds (our configured limit), we record the check as failed and mark the service Down. A single timeout may be a transient network blip. When multiple consecutive checks time out, the service is genuinely unreachable from the open internet.

We use parallel curl_multi requests so one slow host never blocks the entire monitoring batch. Each probe runs with SSL verification enabled — a site with an expired or invalid certificate will show as Down because it is broken for end users.

What DownDetector.me does and does not claim

✓ What we do

  • External reachability check from independent infrastructure
  • HTTP status code and response time recording
  • Uptime history with 48-check sparkline and 30-day % calculation
  • Discord webhook alerts within 5 minutes of a detected outage
  • Live SVG status badge embeddable in any README or dashboard
  • No login required — fully public, free, and transparent

✗ What we do not claim

  • End-to-end functional testing (login, checkout, API response validation)
  • Multi-region probe coverage (single external server)
  • Service-specific health — a 200 OK does not mean all features work
  • Real-time crowd-sourced outage reports
  • Affiliation with any monitored service or its official status pages

What we monitor

We cover three main categories of internet services, plus an open directory where any public domain can be added:

Want to browse everything? View all 14,051 monitored sites →

Frequently asked questions

Our background worker runs every 5 minutes and checks up to 50 domains per run in parallel using curl_multi. Each domain in the database is checked in round-robin order so every monitored site receives a fresh probe within approximately 5–10 minutes depending on the total count.

A domain is marked Operational when our external HTTPS probe returns an HTTP status code in the 2xx or 3xx range within the configured timeout. It is marked Down if the connection fails entirely, the server returns a 4xx/5xx error, or the request times out — all of which indicate the service is unreachable from our infrastructure.

No. DownDetector.me is a fully independent project and is not affiliated with, endorsed by, or associated with Downdetector® or Ookla, LLC in any way. All product names and trademarks belong to their respective owners.

Our probe runs from a single external server. If your ISP, DNS resolver, or regional routing can reach a service that our probe cannot, results will differ. A single "Down" result should be treated as a signal, not a definitive verdict. We recommend checking the recent history graph — if the last five checks all failed, the outage is likely global.

Yes. Every status page on DownDetector.me has a Discord webhook subscription form. Paste your Discord webhook URL and we will send you an automatic notification within 5 minutes of detecting an outage. No sign-up or account is required.

Simply search for any domain on the homepage. If it is not already in our database, we add it automatically and run an immediate status check. The site will then be included in our regular monitoring rotation.

Each monitored domain has a live SVG status badge available at /badge/{domain}.svg. The badge updates in real time to show green (Operational) or red (Down) and can be embedded in a README, dashboard, or website.

We do not require sign-up or collect personal data to use the platform. Discord webhook URLs submitted for alerts are stored only to send outage notifications and are not shared with third parties. See our Privacy Policy for full details.

Check any website right now

No account needed. Search for any domain and get a real-time HTTPS status check in seconds.

Go to homepage →