PLNI (GST Hawaii/Aloha.net) is actually good
j...@hi.net
: vizip via PLNI/AT&T =57.9 ms
: SystemMetrics via Sprint: =65.6 ms
: IAV via AT&T: = 66.9 ms
: NextHawaii via UUnet (HNL2 Honolulu Router) = 75.7 ms
: LavaNet via Genuity/ LavaNet via Sprint = 82.0 ms
: Turquoise.Net via UUNet (HAW2 Waipahu Router) = 82.4 ms
Everyone deserves a listing, sorry if I missed some.
Flex
14 cr04-pos-4-0.fht.netenterprise.net (64.29.65.249) 63.168 ms 63.959 ms 63.955 ms
15 cr02-fast6-0.fht.netenterprise.net (207.26.208.44) 64.458 ms 64.402 ms 63.836 ms
16 flex-colo.cust.fht.netenterprise.net (64.29.65.242) 65.855 ms 68.648 ms 65.281 ms
17 highspeed.flex.com (199.201.240.9) 87.110 ms 90.741 ms 85.817 ms
RR Hawaii
12 acr01-p9-0-0.elsg01.exodus.net (216.34.192.126) 12.858 ms 12.158 ms 12.025 ms
13 64.70.82.14 (64.70.82.14) 29.622 ms 29.390 ms 29.771 ms
14 cr04-pos-4-0.fht.netenterprise.net (64.29.65.249) 63.296 ms 63.079 ms 64.198 ms
15 cr03-fast0-0.fht.netenterprise.net (207.26.208.45) 58.024 ms 58.436 ms 58.137 ms
16 ocrr1.cust.netenterprise.net (207.26.208.234) 62.216 ms 61.935 ms 61.720 ms
17 24.25.225.81 (24.25.225.81) 71.010 ms 70.538 ms 70.160 ms
HINET
12 sl-bb22-stk-11-0.sprintlink.net (144.232.8.189) 5.045 ms 4.960 ms 5.038 ms
13 sl-bb21-prl-11-3.sprintlink.net (144.232.8.218) 58.076 ms 58.890 ms 58.158 ms
14 sl-gw1-prl-12-0-0.sprintlink.net (144.232.30.3) 61.809 ms 58.702 ms 59.160 ms
15 ns1.hi.net (63.173.193.3) 61.398 ms 62.006 ms 61.525 ms
Pixi
12 sl-bb22-stk-11-0.sprintlink.net (144.232.8.189) 5.618 ms 5.268 ms 5.120 ms
13 sl-bb21-prl-11-3.sprintlink.net (144.232.8.218) 58.205 ms 58.213 ms 58.365 ms
14 sl-gw1-prl-12-0-0.sprintlink.net (144.232.30.3) 58.563 ms 58.525 ms 58.360 ms
15 sl-netent-4-0.sprintlink.net (160.81.33.86) 135.551 ms 83.657 ms 300.355 ms
16 cr02-fast6-0.fht.netenterprise.net (207.26.208.44) 60.237 ms 71.199 ms 60.444 ms
17 pixi-colo.cust.fht.netenterprise.net (64.29.82.18) 60.657 ms 60.868 ms 60.603 ms
Hawaiian Net
12 gbr5-p70.sffca.ip.att.net (12.122.5.145) 3.175 ms 3.198 ms 3.063 ms
13 gar3-p360.sffca.ip.att.net (12.123.13.157) 3.349 ms 2.904 ms 3.737 ms
14 12.123.195.9 (12.123.195.9) 50.690 ms 50.038 ms 49.330 ms
15 * * *
16 hawaiian-internet.customer.panworld.net (209.213.36.30) 83.208 ms 69.302 ms 69.298 ms
Poi Net
12 sl-bb22-stk-11-0.sprintlink.net (144.232.8.189) 5.483 ms 5.010 ms 5.353 ms
13 sl-bb21-prl-11-3.sprintlink.net (144.232.8.218) 58.218 ms 57.915 ms 58.106 ms
14 sl-gw1-prl-12-0-0.sprintlink.net (144.232.30.3) 58.795 ms 62.585 ms 58.600 ms
15 sl-pacram-1-0.sprintlink.net (160.81.33.18) 65.625 ms 65.364 ms 70.729 ms
HITS Net
12 sl-bb22-stk-11-0.sprintlink.net (144.232.8.189) 5.590 ms 5.128 ms 4.710 ms
13 sl-bb21-prl-11-3.sprintlink.net (144.232.8.218) 58.094 ms 58.187 ms 58.148 ms
14 sl-gw1-prl-12-0-0.sprintlink.net (144.232.30.3) 58.327 ms 58.878 ms 58.584 ms
15 sl-netent-4-0.sprintlink.net (160.81.33.86) 60.714 ms 74.429 ms 80.276 ms
16 oci00.cust.netenterprise.net (64.29.64.186) 62.648 ms 64.793 ms 60.380 ms
17 core1-pos0-0-0.oceanic.net (216.235.40.9) 61.354 ms 62.082 ms 61.964 ms
18 wurldlink.cust.oceanic.net (216.235.33.118) 66.840 ms 64.977 ms 66.923 ms
19 oahu.WURLDLINK.NET (216.235.52.1) 80.902 ms 93.637 ms 65.128 ms
20 MiliLan220.HITS.NET (216.235.56.220) 96.197 ms 98.536 ms *
HI INFO
11 gbr4-p50.sffca.ip.att.net (12.123.13.70) 3.035 ms 2.819 ms 3.147 ms
12 gbr5-p70.sffca.ip.att.net (12.122.5.145) 2.893 ms 4.068 ms 2.444 ms
13 gar3-p360.sffca.ip.att.net (12.123.13.157) 3.431 ms 2.910 ms 3.037 ms
14 12.123.195.17 (12.123.195.17) 50.349 ms 50.049 ms 51.334 ms
15 12.125.92.30 (12.125.92.30) 63.211 ms 60.929 ms 52.726 ms
BizWind
15 main1colo34-core1-oc48.lax3.above.net (208.185.175.230) 45.606 ms 46.925 ms 45.346 ms
16 above-gw.netenterprise.com (64.124.4.29) 45.248 ms 46.099 ms 45.971 ms
17 cr04-pos-4-0.fht.netenterprise.net (64.29.65.249) 85.980 ms 79.751 ms 79.631 ms
18 cr03-fast0-0.fht.netenterprise.net (207.26.208.45) 73.692 ms 73.751 ms 74.434 ms
19 idd.cust.netenterprise.net (64.29.64.182) 101.246 ms 89.131 ms 88.702 ms
20 bizwind-ppp-s41-00-13-00-acr01.hono.twtelecom.net (216.136.57.214) 110.400 ms 91.814 ms 106.876 ms
Ilhawaii
13 gar1-p370.sffca.ip.att.net (12.123.13.61) 5.548 ms 3.201 ms 3.071 ms
14 12.123.195.21 (12.123.195.21) 59.678 ms 55.847 ms 60.093 ms
15 12.125.94.50 (12.125.94.50) 60.076 ms 60.675 ms 59.961 ms
16 agr3.hnl.aloha.net (207.12.15.20) 60.815 ms 60.756 ms 60.449 ms
17 ip64-75-161-246.hsia.aloha.net (64.75.161.246) 61.495 ms 62.842 ms 68.976 ms
18 c2501-1.ilhawaii.net (207.12.19.4) 71.103 ms 75.655 ms 76.729 ms
Konaguy
<j...@hi.net> wrote in message news:99366375...@news.hi.net...
Kimo
Interesting info. I had just come up with some of the same
conclusions a few days ago after signing on with Flex.com and having
them for around a week. I wish I had read a post like yours around a
month ago as it would have saved me some money (read on).
I like Flex.com for their web access, file downloading etc (very
straightforward setup, good speed, no problems whatsoever), but their
pings to the mainland San Jose area are pretty lousy and inconsistent.
Traceroutes show that there are a lot of delays on the hawaii side of
things. I'm into gaming so this is pretty unacceptable. I know flex
doesn't support gaming, but I was just hoping for better/cheaper.
In any case, I found a good lookingglass site on level3
(www.level3.com/LookingGlass) san jose location that I started
performing pings and traceroutes to the various isps here in hawaii.
The best seems to be vizip (at times), pixi (at times), hoike
(business access only but incredibly consistent pings), inets, and
pdchawaii. I got similar results from net.yahoo.com/cgibin/trace.sh.
I did multiple tests on weekends, during the day, at night, etc to see
which ones were the most consistent. I seem to see that the ones
going through the sprint line versus the at&t line seem to be most
consistent. The AT&T pipes can be fastest, but they're not always so
and seem to fluctuate throughout the day. I was also surprised at how
even after it reaches hawaii, there are some pretty big differences
between isps in how quickly packets are routed to the isp. (big
meaning greater than 20 ms)
I signed up for one of the new ones, will let you know if I like them.
I figure $60 for a verizon change fee is a small price to pay for
better latency (hopefully).
Once again, to be very clear, I'd be very happy with flex if it wasn't
for my gaming needs. Please do not use this post as a complaint
against flex, flex has been incredibly easy to setup. After my signup
verizon was instantly notified, and I have had not one single problem
with flex internet access. The only way I would say to possibly look
at other providers is if you need best quality pings for games like
quake, unreal, tribes, etc. Del says just as much on his signup
sheet. If I wanted high speed web access, good downloading, access to
newsgroups, etc I'd be very hard pressed to beat flex as their prices
are competitive (especially beyond bronze plus, they're unbeatable),
they offer dialup access included for free, no bandwidth usage
charges, and a key thing is they're month to month. If you're not
completely satisfied, just stop paying and your account will cancel no
questions asked. I wish Verizon was so forgiving hehe.
Lates and thanks Kona,
PKM
Konaguy
the Level3 Looking glass link I'm allways looking for sites
I can monitor my RR latency.
"Kimo" <ki...@wermo.com> wrote in message
news:59f9aad9.01062...@posting.google.com...
Kimo
http://www.geektools.com/traceroute.php
http://traceroute.org
Probably overkill but they're very useful.
PKM
"Konaguy" <st...@hawaii.com1> wrote in message news:<9P4%6.20250$WI.65...@typhoon.hawaii.rr.com>...
Konaguy
"Kimo" <ki...@wermo.com> wrote in message
news:59f9aad9.01062...@posting.google.com...
Vincent Poy
good of a backbone to begin with. Their peering kinda sucks though.
I hope Kimo when he was tracing vizip.com, he was tracing hi.vizip.com
and not vizip.com which is in Fremont, CA colocated with Level3. Even
with vizip.com in Hawaii, the subnet does make the difference since
when routes go through the AT&T router that is labeled Honolulu, HI
and shows agr3.aloha.net - the routes have lower latency than the
other ones.
Cheers,
Vince
"Konaguy" <st...@hawaii.com1> wrote in message news:<9P4%6.20250$WI.65...@typhoon.hawaii.rr.com>...
Vincent Poy
good of a backbone to begin with. Their peering kinda sucks though.
I hope Kimo when he was tracing vizip.com, he was tracing hi.vizip.com
and not vizip.com which is in Fremont, CA colocated with Level3. Even
with vizip.com in Hawaii, the subnet does make the difference since
when routes go through the AT&T router that is labeled Honolulu, HI
and shows agr3.aloha.net - the routes have lower latency than the
other ones.
Cheers,
Vince
"Konaguy" <st...@hawaii.com1> wrote in message news:<9P4%6.20250$WI.65...@typhoon.hawaii.rr.com>...
Kimo
Yeah I caught that when I first did the ping and noticed it was in the
teens for ms reply. I actually went back up to kona's message to
double check and noticed the hi.vizip.com in his ping. If those teen
pings had been real, I would have been paying big bucks to get
vizip.com :)
I actually ended up signing up for pdchawaii. I'm told my connect
starts this thursday, here's hoping it's a good 30 ms or so faster
than my previous.
Just curious, what kind of numbers do most of you get when you ping
your ISP's gateway? I think I was getting around 35ms with flex.com.
I'm not sure if it would be different for pdchawaii.com. If it's
better, that will just be extra icing on the cake.
Regards,
PKM
vi...@WURLDLINK.NET (Vincent Poy) wrote in message news:<e758f5f2.01063...@posting.google.com>...
Vincent Poy
ki...@wermo.com (Kimo) wrote in message news:<59f9aad9.01070...@posting.google.com>...
> Hi Vince,
>
> Yeah I caught that when I first did the ping and noticed it was in the
> teens for ms reply. I actually went back up to kona's message to
> double check and noticed the hi.vizip.com in his ping. If those teen
> pings had been real, I would have been paying big bucks to get
> vizip.com :)
Heh. Level3 seems to have a preference for Sprint so to see the AT&T
side of
PLNI, you need to use the AboveNet traceroute server at:
http://www.above.net/cgi-bin/trace
I guess you can try this and you will see what I mean by the way PLNI
and AT&T routes things that there is a 20ms difference.
hi.vizip.com is the one with the better routing
64.75.177.203 which goes to the same router at ViAlta Hawaii gets the
same bad routing via PLNI and AT&T as other PLNI customers such as
SystemMetrics, MidPac, InterPAC. hi.vizip.com which is on the
64.75.176.x subnet would route through the newer AT&T Router that has
Honolulu, HI labeled on it while everyone else routes through the
non-labeled AT&T routers with the 12.x.x.x addresses.
> I actually ended up signing up for pdchawaii. I'm told my connect
> starts this thursday, here's hoping it's a good 30 ms or so faster
> than my previous.
Hopefully you'll get the service you expected. Let us know what your
traceroutes looks like since I think Konaguy mentioned it before that
PDCHawaii might be the same as PIXI. PIXI is now co-located at
NetEnterprise
and NetEnterprise does have lots of problems with latency, routing.
> Just curious, what kind of numbers do most of you get when you ping
> your ISP's gateway? I think I was getting around 35ms with flex.com.
> I'm not sure if it would be different for pdchawaii.com. If it's
> better, that will just be extra icing on the cake.
Hmmm, this is what it looks like from us (wurldlink.net) to a Bronze+
customer.
root@oahu [9:42am][/home/vince] >> traceroute 216.235.44.17
traceroute to 216.235.44.17 (216.235.44.17), 30 hops max, 40 byte
packets
1 ward-adsl1-16-us-hnl (216.235.44.17) 26.391 ms 26.144 ms 25.926
ms
root@oahu [9:42am][/home/vince] >> ping -c 5 216.235.44.17
PING 216.235.44.17 (216.235.44.17): 56 data bytes
64 bytes from 216.235.44.17: icmp_seq=0 ttl=64 time=28.243 ms
64 bytes from 216.235.44.17: icmp_seq=1 ttl=64 time=28.567 ms
64 bytes from 216.235.44.17: icmp_seq=2 ttl=64 time=27.815 ms
64 bytes from 216.235.44.17: icmp_seq=3 ttl=64 time=30.046 ms
64 bytes from 216.235.44.17: icmp_seq=4 ttl=64 time=28.335 ms
--- 216.235.44.17 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
Cheers,
Vince - vi...@WURLDLINK.NET