Check your DNS
Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.
Web · fedex.com
¿Está caído FedEx?
fedex.com
logistics
FUNCIONA
Checked 1s ago
4/4 regions returned data
every 5 min · HTTP probe
direct probe, not crowd-reported
Resultados por región
US East
FUNCIONA
250 ms
HTTP 301
US West
FUNCIONA
234 ms
HTTP 301
Europe
FUNCIONA
68 ms
HTTP 301
Asia
FUNCIONA
69 ms
HTTP 301
Detalles HTTP
- HTTP status
- 301
- Response time
- 68 ms
- Region consensus
- 4/4 reachable
- 24h success rate
- 100% (2/2 probes)
- 24h latency
- 155–210 ms · 183 ms avg
- Last successful probe
- 1s ago
Desglose de tiempos
- DNS lookup
- 13 ms
- TCP connect
- 17 ms
- TLS handshake
- 19 ms
- First byte
- 19 ms
- Total
- 68 ms
Red
- Host
- fedex.com
- Port
- 443
- Transport
- HTTPS
Qué significa
FedEx 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.
Qué hacer ahora
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 FedEx down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see FedEx's internal cause — we only confirm reachability from each monitoring region. If all 4 regions failed, it's a confirmed outage on FedEx's side. If only some failed, the impact is regional.
Is FedEx 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 FedEx's side.
How often does isitdown.io re-check FedEx?
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.
Status badge
Embed a live status badge on your site, README, or status page. Updates automatically — same status-aware SVG the rest of isitdown.io uses.
<a href="https://isitdown.io/website/fedex.com"><img src="https://isitdown.io/badge/fedex.com.svg" alt="FedEx status"></a>
Relacionados · logistics
Metodología
- Sonda
- We send a GET request to the target URL from each region and time the full response.
- Se considera CAÍDO si
- Every region fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
- Se considera DEGRADADO si
- At least one region succeeds but at least one fails — the outage is partial or regional.
- Detalle
- 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.
- Cadencia
- Every 5 minutes, in parallel across 4 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
- Objetivos con límite de tasa
- 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.
- Fuente de datos
- 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.