Has anyone else spotted this? Users on both flow and cwjamaica (moreso CWJ) have been since this morning it seems, having problems connecting to, or maintaining connections to servers. Overally browsing speed is also slow. Take a look at these speeds from our location (our customers are having the same problem and CWJ has not yet, sent out an advisory.. as usual):
1) Pinging google.com [64.233.167.99] with 32 bytes of data:
Reply from 64.233.167.99: bytes=32 time=750ms TTL=238
Reply from 64.233.167.99: bytes=32 time=748ms TTL=238
Reply from 64.233.167.99: bytes=32 time=874ms TTL=238
Reply from 64.233.167.99: bytes=32 time=835ms TTL=238
Ping statistics for 64.233.167.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 748ms, Maximum = 874ms, Average = 801ms
2) Pinging yahoo.com [216.109.112.135] with 32 bytes of data:
Reply from 216.109.112.135: bytes=32 time=893ms TTL=47
Reply from 216.109.112.135: bytes=32 time=829ms TTL=47
Request timed out.
Reply from 216.109.112.135: bytes=32 time=922ms TTL=47
Ping statistics for 216.109.112.135:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 829ms, Maximum = 922ms, Average = 881ms
3) On further investigation, i did a tracert:
Tracing route to yahoo.com [216.109.112.135]
over a maximum of 30 hops:
1 726 ms 850 ms 843 ms 10.0.0.2
2 857 ms 864 ms 682 ms bsn2-loopback.cwjamaica.com [208.138.43.82]
3 810 ms 852 ms 764 ms 208.138.43.89
4 769 ms 790 ms 827 ms 200.10.152.214
5 585 ms 979 ms 687 ms so-0-2-2-nmi-core01.nwnnetwork.net [63.245.40.9]
6 874 ms 865 ms 806 ms v4-nmi-edge01.nwnnetwork.net [63.245.5.129]
7 451 ms 782 ms 1040 ms border5.ge3-2.asurnet-10.mia003.pnap.net [69.25.
2.49]
8 847 ms 523 ms 651 ms core1.t6-2.bbnet2.mia003.pnap.net [69.25.0.65]
9 919 ms 917 ms 872 ms ge-4-2.r03.miamfl02.us.bb.gin.ntt.net [130.94.19
5.117]
10 853 ms 708 ms 891 ms ae-1.r01.miamfl02.us.bb.gin.ntt.net [129.250.2.1
61]
11 948 ms 802 ms 694 ms as-0.r20.asbnva01.us.bb.gin.ntt.net [129.250.4.1
16]
12 943 ms 951 ms * ae-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.1
7]
13 869 ms 760 ms 626 ms so6-2-0-2488M.ar1.DCA3.gblx.net [208.51.6.33]
14 911 ms 658 ms 846 ms yahoo-2.ar1.DCA3.gblx.net [208.51.74.182]
15 827 ms 830 ms 776 ms ge-1-0-0-p101.msr1.dcn.yahoo.com [216.115.108.43
]
16 793 ms 843 ms 914 ms ge7-1.bas1-m.dcn.yahoo.com [216.109.120.205]
17 675 ms 821 ms 918 ms w2.rc.vip.dcn.yahoo.com [216.109.112.135]
Trace complete.
As much as I am not a fan of CWJ's ADSL offering, this problem seems to be above and beyond them. I'd love it if some more fortunate Flow customers could do the same tests and post here. Our customers (hosting) are complaining of course, of slow connection speeds to our servers and, it's difficult to explain, especially to users who are not tech-savvvy in the least (I'm only partially so), that there is clearly something larger at work now, and since this morning.
By the way, a ping of yahoo.com by way of dnsstuff.com (outside of Jamaica) returns this rather good result:
Pinging www.yahoo.com [209.191.93.52]:
Ping #1: Got reply from 209.191.93.52 in 51ms [TTL=57]
Ping #2: Got reply from 209.191.93.52 in 62ms [TTL=57]
Ping #3: Got reply from 209.191.93.52 in 77ms [TTL=57]
Ping #4: Got reply from 209.191.93.52 in 47ms [TTL=57]
Variation: 30ms (+/- 50%)
Shortest Time: 47ms
Average: 59ms
Longest Time: 77ms
Done pinging www.yahoo.com!