Check-Host.cc

資訊 Ping HTTP TCP UDP MTR DNS

:target MTR 檢查 nl-eyg-ghosted.check-host.eu

永久連結 |
Location Result
AL Albania, Tirana
AU Australia, Sydney
BA Bosnia and Herzegovina, Novi Travnik
BG Bulgaria, Sofia
CA Canada, Montreal
CH Switzerland, Bern
CL Chile, Santiago
CN China, Hohhot
DE Germany, Nuernberg
DE Germany, Frankfurt am Main
DE Germany, Frankfurt am Main
DE Germany, Limburg
DK Denmark, Glostrup Municipality
ES Spain, Madrid
FI Finland, Helsinki
FI Finland, Helsinki
FR France, Gravelines
FR France, Paris
GB United Kingdom, London
HK Hong Kong, Hong Kong
HR Croatia, Zagreb
HU Hungary, Budapest
ID Indonesia, Jakarta
IN India, New Delhi
IS Iceland, Reykjavik (Miðborg)
IT Italy, Como
LT Lithuania, Pilaite
LV Latvia, Riga
MD Moldova, Chisinau
NL Netherlands, Amsterdam
NL Netherlands, Amsterdam
NL Netherlands, Amsterdam
NL Netherlands, Eygelshoven
QA Qatar, Doha
RO Romania, Bacău
RO Romania, Bucharest
RS Serbia, Belgrade
SG Singapore, Singapore
TW Taiwan, Taipei
US United States, Miami
US United States, Dallas
US United States, Kansas City

Global MTR (My Traceroute) & Routing Diagnostic Tool

我們的 MTR (My Traceroute) 工具結合了「traceroute」和「ping」指令的功能，為您提供一個強大的網路診斷介面。我們從全球多個節點，發送具有遞增存活時間 (Time-To-Live, TTL) 數值的連續資料封包序列。這能繪製出流量從我們的全球伺服器到達您目標位置的確切網路運作路徑。

Hop-by-Hop Packet Loss and Latency

在探測連線路徑的同時，MTR 會持續對該路徑上的每一個中繼路由器 (hop) 進行 Ping 執行測試，並即時收集各個階段的封包遺失 (packet loss) 與網路延遲 (latency) 的統計資料。這讓 MTR 成為精確定位網路瓶頸或連線故障發生位置的絕對最佳工具 — 無論這問題是發生在來源端 ISP 供應商、骨幹網路供應商 (backbone provider)，還是目標網路邊緣路由器 (edge router) 上。

BGP Routing and Suboptimal Paths

The internet relies on the Border Gateway Protocol (BGP) to route traffic. However, BGP prioritizes the shortest AS-path, which is not necessarily the fastest or most reliable physical route. By executing a distributed MTR test, administrators can identify suboptimal peering arrangements, asymmetric routing anomalies, and circular routing loops that degrade application performance for specific international demographics.

Reverse DNS (PTR) Resolution

Our MTR engine automatically performs reverse DNS (rDNS) lookups on every discovered hop. Translating raw IP addresses back into canonical hostnames helps quickly identify the commercial operators (e.g., Telia, Level3, Cogent) managing the transit infrastructure. Note: If a specific hop returns a consistent 100% loss but subsequent hops respond normally, it usually indicates a firewall silently dropping ICMP TTL-exceeded packets rather than a true network outage.