Check your DNS
Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.
Site web · capitalone.com
Capital One est-il en panne ?
capitalone.com
banking
OPÉRATIONNEL
Checked 1s ago
4/4 regions returned data
every 5 min · HTTP probe
direct probe, not crowd-reported
Résultats par région
US East
OPÉRATIONNEL
38 ms
HTTP 301
US West
OPÉRATIONNEL
261 ms
HTTP 301
Europe
OPÉRATIONNEL
30 ms
HTTP 301
Asia
OPÉRATIONNEL
258 ms
HTTP 301
Détails HTTP
- HTTP status
- 301
- Response time
- 30 ms
- Region consensus
- 4/4 reachable
- 24h success rate
- 100% (1/1 probes)
- 24h latency
- 147–147 ms · 147 ms avg
- Last successful probe
- 1s ago
Décomposition des temps
- DNS lookup
- 10 ms
- TCP connect
- 7 ms
- TLS handshake
- 11 ms
- First byte
- 2 ms
- Total
- 30 ms
Réseau
- Host
- capitalone.com
- Port
- 443
- Transport
- HTTPS
Que signifie ce résultat
Capital One 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.
Que faire ensuite
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 Capital One down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see Capital One's internal cause — we only confirm reachability from each monitoring region. If all 4 regions failed, it's a confirmed outage on Capital One's side. If only some failed, the impact is regional.
Is Capital One 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 Capital One's side.
How often does isitdown.io re-check Capital One?
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.
Voir aussi · banking
Méthodologie
- Sonde
- We send a GET request to the target URL from each region and time the full response.
- Compté comme EN PANNE si
- Every region fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
- Compté comme DÉGRADÉ si
- At least one region succeeds but at least one fails — the outage is partial or regional.
- Détail
- 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).
- Cibles limitées en débit
- 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.
- Source des données
- 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.