What is MTR traceroute and how does it work?

MTR (My Traceroute) combines ping and traceroute into a single diagnostic. It sends packets with incrementing TTL values, causing each router on the path to return a time-exceeded message. This reveals every network hop between the probe node and your server, with latency and packet loss measured at each individual hop.

How do I read an MTR result?

Each row represents a network hop. The Host column shows the router IP or hostname, Loss% shows packet loss at that hop, and Avg shows average latency. If a middle hop shows high loss but subsequent hops respond fine, that hop is rate-limiting ICMP replies — not actually dropping real traffic. Actual packet loss that affects users shows at the final destination hop.

What does 100% packet loss at a hop mean in MTR?

A hop showing 100% packet loss while subsequent hops respond normally is almost always ICMP rate-limiting — the router is forwarding traffic fine but deprioritizes generating TTL-exceeded replies to reduce load. Only packet loss at the final destination hop indicates traffic is actually being dropped for real users.

Can I run an MTR traceroute from a specific country?

Yes. Use the country-specific node pages (e.g. /mtr/germany or /mtr/singapore) to run an MTR diagnostic from nodes in that specific country. Running from multiple countries simultaneously helps identify whether routing issues are path-specific or affect all global traffic to your server.

MTR Traceroute para t1-tor-2.check-host.eu

Name: Check-Host t1-tor-2.check-host.eu Traceroute visual y MTR
Author: Check-Host

Ajustes avanzados

Mostrar mapa mundial

Info Ping HTTP TCP UDP MTR DNS

SQLSTATE[HY000] [1040] Too many connections (Connection: mysql, Host: 172.17.0.1, Port: 3306, Database: laravel, SQL: insert into `check_tasks` (`pubuuid`, `target`, `method`, `repeatchecks`, `delete_at`, `updated_at`, `created_at`) values (b9050e87-13fc-4a4d-8783-fa54b59e7a0d, t1-tor-2.check-host.eu, mtr, 5, 2036-10-25 11:09:04, 2026-10-25 11:09:04, 2026-10-25 11:09:04))

Comprobar MTR: Diagnóstico de red global y traceroute

Introduce un dominio o dirección IP arriba para empezar el diagnóstico global de MTR.

Ejemplos: 1.1.1.1 tarnkappe.info google.com

MTR Global (Mi Traceroute) e Inspección de Red

MTR (abreviatura de My Traceroute) es una herramienta de diagnóstico de red estándar que combina las funciones de ping y traceroute en una única interfaz en tiempo real. Se utiliza principalmente para solucionar problemas de calidad de la conexión, como una alta latencia o pérdida de paquetes, al mostrar exactamente qué nodo (salto) en la ruta de red está causando el problema.

Latencia de Salto y Pérdidas

La técnica MTR asocia la visualización rápida de ping continuado frente al reporte perimetral salto a salto usando ICMP. En nuestra consola visualizas la suma de este entorno sobre una latencia escalada globalmente en minutos.

Enrutamiento BGP e Infraestructuras de Peering

Analiza las paradas y el ancho del problema BGP identificando en qué router intermedio salta tu fallo con el proveedor, todo ello mientras te exponemos los servidores DNS inversos operando a nivel capa 3.

Resoluciones (PTR) Inversa

Nuestra matriz inspecciona DNS tras cada salto de red (rDNS). Al devolver los registros oficiales de esas ips crudas, el origen y portador de esas caídas (por ejemplo, Level 3, Cogent) será obvio e identificable al instante. Nota: Si observas cortes íntegros del 100% de la ruta con continuidad local posterior, usualmente un salto se omite artificialmente descartando ecos que exijan repuestas predefinidas.