Check your DNS
Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.
Website · doctolib.fr
Is Doctolib down?
doctolib.fr
web
FR
UP
Checked 1s ago
4/4 regions returned data
every 5 min · HTTP probe
direct probe, not crowd-reported
Per-region results
US East
UP
703 ms
HTTP 301
US West
UP
702 ms
HTTP 301
Europe
UP
704 ms
HTTP 301
Asia
UP
703 ms
HTTP 301
HTTP details
- HTTP status
- 301
- Response time
- 702 ms
- Region consensus
- 4/4 reachable
- 24h success rate
- 50% (1/2 probes)
- 24h latency
- 703–703 ms · 703 ms avg
- Last successful probe
- 1s ago
Timing breakdown
- DNS lookup
- 419 ms
- TCP connect
- 3 ms
- TLS handshake
- 175 ms
- First byte
- 106 ms
- Total
- 702 ms
Network
- Host
- doctolib.fr
- Port
- 443
- Transport
- HTTPS
What this means
Doctolib is reachable from all 4 monitoring regions.
If you still can't connect, the outage is on your side: DNS cache, VPN routing, ISP filtering, or a browser-level block. Try a different network or device to confirm.
What to try next
Try another network
Switch between Wi-Fi and mobile data, or disable your VPN. If it works there, the issue is on your primary network.
Browser reset
Try an incognito window or a different browser — a bad extension or cached error page can masquerade as downtime.
FAQ
Why is Doctolib down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see Doctolib's internal cause — we only confirm reachability from each monitoring region. If all 4 regions failed, it's a confirmed outage on Doctolib's side. If only some failed, the impact is regional.
Is Doctolib down for everyone or just me?
Look at the per-region grid above. If every region succeeded, the issue is local to your network — flush DNS, switch networks, or disable your VPN. If two or more regions failed, the outage is on Doctolib's side.
How often does isitdown.io re-check Doctolib?
Every 5 minutes via background HTTP probes from US East, US West, Europe, and Asia. You can also re-run on demand by reloading — the verdict above reflects the latest probe.
Related · web
Methodology
- Probe
- We send a GET request to the target URL from each region and time the full response.
- Counts as DOWN
- Every region fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
- Counts as DEGRADED
- At least one region succeeds but at least one fails — the outage is partial or regional.
- Detail
- Per-region results include HTTP status code, response time, and best-effort DNS / connect / TLS / first-byte phase timings when the Node HTTP client exposes them.
- Cadence
- Every 5 minutes, in parallel across 4 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
- Rate-limited targets
- If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status — we do not flood the target to confirm the outage.
- Data source
- Direct probes from our monitoring infrastructure. We do not aggregate crowd reports, Twitter mentions, or DownDetector signals — every result on this page is a live network request.