On 03.01.2012 23:13, Fredy Kuenzler wrote:
Responsetime of hop 12 (80.91.251.98) is much higher than hop 11 (80.91.249.113) and a ping test did show lost packets on hop 12 but not on hop 11.
11 prs-bb1-link.telia.net (80.91.249.113) [AS1299] 25.882 ms 125.402 ms 25.827 ms 12 ash-bb1-link.telia.net (80.91.251.98) [AS1299] 108.584 ms 113.053 ms ash-bb1-link.telia.net (80.91.252.36) [AS1299] 158.407 ms
Hop 11 is in Paris, hop 12 in Ashburn. I don't see anomalies considering the latency, as the atlantic is in between.
ah, beginner's mistake. :) I was on some geoip page that told me it was in EU and the map showed a point in switzerland.
The path seems to be multipath, but this is still ok. The loss / congestion could be on the return path, for proper diagnosis you need a traceroute from the other end, too.
Sadly I can't do a traceroute from the other side.
Check return pathes to proxies and compare them to the direct link... and, as Victor already said, don't expect guaranteed latecy on a xDSL service...
yeah I know about the xDSL, guaranteed latency and "best effort" things. it's just a more or less one-man show and he does not bother about possible outages. the connection was working for about 2 years now and it is only slow on startup (after a 30min startup, the app is working normally). Seems it's just a problem while downloading some initial things.
as it seems to be a problem that is catchy to solve, he'll work with the easy solution of using a proxy (startup time: 30seconds).
thanks to all others who have answerd!
- Thomas