i don´t like the website, because the site is dogslow. and worse are the downloadtimes. waiting 40 minutes for a 60MB VEpro-update download is unbearable these times. that was 1998. anyway, i like the company!

 i'm sorry to hear about your slow download, but you should definitely contact your provider which seems to be deutsche telekom

  6   626 ms   638 ms   665 ms  dtag-muc.peering.cogentco.com [212.20.155.37]
  7   671 ms   608 ms   566 ms  hh-ea1-i.HH.DE.NET.DTAG.DE [217.5.74.154]
  8     *      599 ms   647 ms  87.186.245.133

it appears they have a problem with the peering point between cogento and dtag (extremely high latency and packetloss)

christian

better now (2 AM CET) but still bad ... you can verify the other direction doing a traceroute to vsl.co.at

  6   424 ms   424 ms   413 ms  dtag-muc.peering.cogentco.com [212.20.155.37]
  7   396 ms   395 ms   395 ms  hh-ea1-i.HH.DE.NET.DTAG.DE [217.5.74.154]

 

here is one from the US westcoast over more than twice the number of hops

 12    84 ms    84 ms    85 ms  te7-7.ccr02.ymq02.atlas.cogentco.com [66.28.4.138]
(--atlantic cable--)
 13   163 ms   163 ms   163 ms  te3-1.mpd01.ymq02.atlas.cogentco.com [154.54.7.125]
 14   163 ms   163 ms   163 ms  te9-3.mpd03.fra03.atlas.cogentco.com [154.54.26.142]
 15   163 ms   163 ms   162 ms  te3-7.ccr01.fra03.atlas.cogentco.com [130.117.49.169]
 16   168 ms   169 ms   168 ms  te3-2.ccr01.muc01.atlas.cogentco.com [130.117.0.66]
 17   175 ms   175 ms   175 ms  te1-1.ccr01.vie01.atlas.cogentco.com [130.117.3.22]
 18   175 ms   177 ms   176 ms  149.6.80.42
 19   175 ms   175 ms   176 ms  vsl.co.at [212.24.125.70]

hi cm. thanks for answering, i only just see your posts. so i searched the web a little and it seems like this is a known and probably a "political" issue between dtag and cogentco which is hard to believe. seems to be about to pay or not to pay for peering. hmmm. in one statement from the dtag they say that many network carrier have issues with cogentco regarding peering, leading to the question wether a company providing a lot of content to many people all over the world should solely work with cogentco. i will now call up the t-online hotline, but i don´t see any chance, that they can do anything for me. i´ll report back anyway...

hi again, the principle of routing is based on the *least cost of a route* where bandwidth, number of hops, latency, priorization are some factors. remember the internet has been designed as a failure tolerant mesh.

our servers in vienna have uplinks to 3 major backbone providers available, our server in US 2 - to some extent we can ask for priorizing one route or another but we don't have influence on peering points of the destination network.

eg. if DTAG decides to peer incoming traffic mainly with cogentco we actually don't get another possible route ...

anyway, thanks for reporting - we always keep a wary eye on such issues, christian

 

edit: hehe ... our provider managed to change the preferred route  from our side and it should be much better now ...

christian, wow cool. it IS much better now. though: today. after reading your edit yesterday evening i still got an download speed average of 20KB/s. right now i get 200-250 KB/s which is o.k.. enough for software downloads. for instruments downloads it still might be a bit slow but i don´t care today. this doesn´t happen very often. thanks for asking your provider :-)

thanks again, christian - it´s been running perfect for the latest updates. like 1MB/sec. you care - i like this website. :)