What I found out today is the new bandwidth may not be turned on until late next week. Since that is the case, Hawaiian Tel is working with Sprint to see if its something besides a congestion issue.
2006-07-07 23:02:12 Speed test @ lax.speedtest.dslextreme.com 359/282 kbps
2006-07-07 22:58:42 Speed test @
www.sonic.net 256/602 kbps
2006-07-07 22:56:51 Speed test @ dslreports-west2.speakeasy.net 275/484 kbps
2006-07-07 22:55:21 Speed test @ dslreports.linkline.com 211/737 kbps
2006-07-07 22:53:35 Speed test @ dslr-west1.megapath.net 290/442 kbps
Address:
www.dslreports.com
Number of Packets: 1
Packet size: 64
Trace Hop 1 through 20
Timeout: 5
Resolve Addresses: Yes
Don't Fragment: No
#1 Unavailable (192.168.1.1): TTL Exceeded, ttl=128, 16 ms
#2 Unavailable (72.234.154.1): TTL Exceeded, ttl=126, 32 ms
#3 Unavailable (10.245.225.34): TTL Exceeded, ttl=252, 31 ms
#4 sl-gw2-prl-6-2.sprintlink.net (144.223.63.85): TTL Exceeded, ttl=252, 344 ms
#5 sl-bb20-prl-0-0.sprintlink.net (144.232.30.21): TTL Exceeded, ttl=251, 344 ms
#6 sl-bb20-stk-6-0.sprintlink.net (144.232.8.26): TTL Exceeded, ttl=250, 422 ms
#7 sl-bb20-sj-9-0.sprintlink.net (144.232.20.99): TTL Exceeded, ttl=249, 422 ms
#8 sl-bb25-sj-13-0.sprintlink.net (144.232.3.198): TTL Exceeded, ttl=248, 422 ms
#9 sl-st21-sj-12-0.sprintlink.net (144.232.9.240): TTL Exceeded, ttl=247, 422 ms
#10 Unavailable (144.232.9.90): TTL Exceeded, ttl=245, 422 ms
#11 nyk-bb1-pos7-3-0.telia.net (213.248.80.2): TTL Exceeded, ttl=243, 469 ms
#12 nyk-b3-link.telia.net (80.91.249.81): TTL Exceeded, ttl=241, 468 ms
#13 nac-110814-nyk-b3.c.telia.net (213.248.82.94): TTL Exceeded, ttl=241, 469 ms
#14 12.ae0.gbr1.tl9.nac.net (209.123.11.71): TTL Exceeded, ttl=241, 485 ms
#15 33.ge-3-0-0.gbr2.nwr.nac.net (209.123.11.7): TTL Exceeded, ttl=241, 469 ms
#16 0.so-0-3-0.gbr1.oct.nac.net (209.123.11.233): TTL Exceeded, ttl=241, 468 ms
#17
www.dslreports.com (209.123.109.175): Echo Reply, ttl=50, 469 ms
Statistics: Out 17, in 17, loss 0%, times (min/avg/max) 16/363/485 ms
Address:
www.konaweb.com
Number of Packets: 1
Packet size: 64
Trace Hop 1 through 20
Timeout: 5
Resolve Addresses: Yes
Don't Fragment: No
#1 Unavailable (192.168.1.1): TTL Exceeded, ttl=128, 0 ms
#2 Unavailable (72.234.154.1): TTL Exceeded, ttl=126, 32 ms
#3 Unavailable (10.245.225.34): TTL Exceeded, ttl=252, 32 ms
#4 sl-gw2-prl-6-2.sprintlink.net (144.223.63.85): TTL Exceeded, ttl=252, 312 ms
#5 sl-bb20-prl-0-0.sprintlink.net (144.232.30.21): TTL Exceeded, ttl=251, 343 ms
#6 sl-bb21-stk-5-3.sprintlink.net (144.232.8.26): TTL Exceeded, ttl=250, 375 ms
#7 sl-bb20-sj-9-0.sprintlink.net (144.232.20.99): TTL Exceeded, ttl=249, 390 ms
#8 sl-bb25-sj-13-0.sprintlink.net (144.232.3.198): TTL Exceeded, ttl=248, 375 ms
#9 sl-st21-sj-12-0.sprintlink.net (144.232.9.240): TTL Exceeded, ttl=247, 390 ms
#10 Unavailable (144.232.9.90): TTL Exceeded, ttl=245, 390 ms
#11 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54): TTL Exceeded, ttl=245, 391 ms
#12 pos10-0.gsr12416.fmt.he.net (216.218.229.38): TTL Exceeded, ttl=244, 391 ms
#13 pos10-0.gsr12012.fmt.he.net (66.220.20.138): TTL Exceeded, ttl=243, 407 ms
#14 konaweb.com (64.62.225.181): Echo Reply, ttl=51, 391 ms
Statistics: Out 14, in 14, loss 0%, times (min/avg/max) 32/301/407 ms
The latency is utterly horrible.Hence the slow speeds.