Audessy, see my trace and then tell me anything about my network, Your making a concusion without knowing how something works.
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1] (connection goes to the router) 2 7 ms 7 ms 8 ms 10.239.96.1 3 8 ms 11 ms 6 ms 213.51.151.113 4 10 ms 9 ms 8 ms csw2-pc156.tilbu1.nb.home.nl [213.51.151.95] 5 12 ms 12 ms 12 ms asd-tr0409-cr101-ae5-0.core.as9143.net [213.51.1 58.154] 6 13 ms 13 ms 14 ms ae5.ams20.ip4.tinet.net [77.67.64.65] 7 180 ms 203 ms 170 ms xe-4-1-0.sjc12.ip4.tinet.net [89.149.186.205] 8 168 ms 169 ms 169 ms panther-express-gw.ip4.tinet.net [77.67.68.138]
9 211 ms 210 ms 211 ms 174.35.18.121 10 190 ms 198 ms 198 ms 174.35.18.74 11 187 ms * 185 ms 174.35.12.6 12 177 ms 180 ms 174 ms 174.35.13.246 13 185 ms 185 ms 185 ms 208.80.251.170 14 189 ms 189 ms 191 ms 211.43.149.199
On line 7 i'm already past my ISP without issues.
Data packets often have to go through routers (more generally: gateways), if not several, before they reach their final destination. Each time packets are passed to the next router a hop occurs. (To see how many hops it takes to get from one host to another ping or traceroute/tracepath commands can be used).
From hop 7-14 the pain starts, Hoplita
|