Re: low-latency bandwidth for cheap?

[John Lyons <john.lyons () heanet ie>]

>   verizon / lavanet (hawi to honolulu, 25 mins air time by plane)
>
>     64 bytes from 64.65.95.73: icmp_seq=0 ttl=64 time=20.637 ms
>     64 bytes from 64.65.95.73: icmp_seq=1 ttl=64 time=22.186 ms
>     64 bytes from 64.65.95.73: icmp_seq=2 ttl=64 time=21.965 ms
>     64 bytes from 64.65.95.73: icmp_seq=3 ttl=64 time=21.723 ms
>     64 bytes from 64.65.95.73: icmp_seq=4 ttl=64 time=21.538 ms
>
>   qwest / iinet (30 miles from bainbridge to hellview wa us)
>
>     64 bytes from 209.20.186.1: icmp_seq=0 ttl=63 time=67.008 ms
>     64 bytes from 209.20.186.1: icmp_seq=1 ttl=63 time=67.700 ms
>     64 bytes from 209.20.186.1: icmp_seq=2 ttl=63 time=56.696 ms
>     64 bytes from 209.20.186.1: icmp_seq=3 ttl=63 time=60.249 ms
>
> i do not know why and can get no useful info on provisioning.
> i know iinet is redback.

 It's more than likely interleaving which is causing the latency, 
 it's used in order to reduce line errors (and to increase reach) 
 but a side effect is that it increases latency.
 
 The verizon connection is more than likely not using interleaving
 while the Qwest connection is. 

 John 

-- 
John Lyons              Phone:  +353-1-660-9040
Network Engineer        Fax:    +353-1-660-3666
HEAnet Ltd.             Email:  john.lyons () heanet ie