Web · renfe.com

¿Está caído RENFE?

renfe.com web ES
FUNCIONA
RENFE · renfe.com
Accesible desde las 4 regiones de monitorización
HTTPS · 1055 ms
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
1055 ms HTTP 302
US West FUNCIONA
1055 ms HTTP 302
Europe FUNCIONA
1063 ms HTTP 302
Asia FUNCIONA
1062 ms HTTP 302

Detalles HTTP

HTTP status
302
Response time
1055 ms
Region consensus
4/4 reachable
24h success rate
100% (1/1 probes)
24h latency
1059–1059 ms · 1059 ms avg
Last successful probe
1s ago

Desglose de tiempos

DNS lookup
624 ms
TCP connect
112 ms
TLS handshake
215 ms
First byte
104 ms
Total
1055 ms

Red

Host
renfe.com
Port
443
Transport
HTTPS
Qué significa

RENFE 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

Check your DNS

Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.

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 RENFE down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see RENFE's internal cause — we only confirm reachability from each monitoring region. If all 4 regions failed, it's a confirmed outage on RENFE's side. If only some failed, the impact is regional.
Is RENFE 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 RENFE's side.
How often does isitdown.io re-check RENFE?
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.

RENFE status
<a href="https://isitdown.io/website/renfe.com"><img src="https://isitdown.io/badge/renfe.com.svg" alt="RENFE status"></a>

Relacionados · web

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.
JSON: /check?target=renfe.com&format=json Share: https://isitdown.io/es/website/renfe.com