Quote:
|
Originally Posted by Chrysalis
its not LT I am complaining about its the route used to my connection, I will be a bit more clear.
The problem exists with many usa providers, infact level3 appears so bad cogent outperforms it.
Anyone not coming in on level3 is fine including ntl people, but the one other guy I know off on the level3 route has the exact same problems as me.
The problem could be level3 itself or ntl's level3 peering. I am also annoyed that ntl dont route all their customers the same.
I did try to traceroute your connection but it seems your website isnt hosted on your cable anymore so I cant see which route is been taken to it. I dont get the constant over 200ms but I am getting a lot of lag spikes and slow transfer speeds. These are happening at places like steadfast sagonet as well tho.
I think you jumped the gun blaming lt if other isp's and users are not getting the lag to your server and go over savvis the problem isnt at lt.
|
I know its savvis as Ive got people I know from all over the world to do tracert's and they all show problems as soon as it hits savvis. Its not level3 thats the problem. Its the router at the savvis side that level3 jump to. This is why the level3 connection is showing a high ping. Its the savvis router being a pain.
If you wish to ping my house you can try m3ezw.no-ip.com but I think my router blocks the pings. A tracert would be better.
People from sweden, USA itself, france and ireland are all having these ping problems to my server and the cause is savvis. They dont even hit the level3 network. It seems to be worse during the evenings and better during the morning/early afternoon.
I seem to get these pings spikes too, again, its the savvis network at fault. Their 2x 1Gbps connections from the UK to the US seem to be saturated a lot at peak times.