Changes between Initial Version and Version 3 of Ticket #101


Ignore:
Timestamp:
25 Mar 2009, 15:56:57 (10 years ago)
Author:
randy@…
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #101

    • Property Priority changed from tbd to major
  • Ticket #101 – Description

    initial v3  
    1 Since logging on at the "ietf" SSID at 9 this morning I have experienced slow connections to many sites. Most of the sites I have noticed this with are in Norway, e.g. www.vg.no (largest newspaper in Norway).
    2 
    3 My system is a IBM X40 laptop, WinXP SP3, builtin wireless a/b/g.
    4 
    5 A short while ago I decided to do some ping and tracert tests and got, as examples, the pingtimes below, and helpdesk got various results some similar to these, others looking normal.
    6 
    7 C:\Documents and Settings\Administrator>ping www.vg.no
    8 
    9 Pinging www.vg.no [193.69.165.21] with 32 bytes of data:
    10 
    11 Reply from 193.69.165.21: bytes=32 time=327ms TTL=238
    12 Reply from 193.69.165.21: bytes=32 time=380ms TTL=238
    13 Request timed out.
    14 Reply from 193.69.165.21: bytes=32 time=207ms TTL=238
    15 
    16 Ping statistics for 193.69.165.21:
    17     Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
    18 Approximate round trip times in milli-seconds:
    19     Minimum = 207ms, Maximum = 380ms, Average = 304ms
    20 
    21 
    22 
    23 C:\Documents and Settings\Administrator>ping www.wired.com
    24 
    25 Pinging a867.g.akamai.net [208.50.79.41] with 32 bytes of data:
    26 
    27 Reply from 208.50.79.41: bytes=32 time=22ms TTL=57
    28 Request timed out.
    29 Reply from 208.50.79.41: bytes=32 time=127ms TTL=57
    30 Reply from 208.50.79.41: bytes=32 time=19ms TTL=57
    31 
    32 Ping statistics for 208.50.79.41:
    33     Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
    34 Approximate round trip times in milli-seconds:
    35     Minimum = 19ms, Maximum = 127ms, Average = 56ms
    36 
    37 Traceroutes showed the following:
    38 
    39 C:\Documents and Settings\Administrator>tracert www.vg.no
    40 
    41 Tracing route to www.vg.no [193.69.165.21]
    42 over a maximum of 30 hops:
    43 
    44   1     1 ms    <1 ms    <1 ms  130.129.16.2
    45   2     9 ms    16 ms    22 ms  66.114.246.1
    46   3    12 ms    13 ms    10 ms  t3-3-1-0-3.edge7.SanJose1.Level3.net [4.53.20.13
    47 ]
    48   4   134 ms     *       14 ms  ae-15-15.car1.SanJose1.Level3.net [4.68.106.249]
    49 
    50   5     *        9 ms    31 ms  vlan79.csw2.SanJose1.Level3.net [4.68.18.126]
    51   6     *       33 ms     *     ae-74-74.ebr4.SanJose1.Level3.net [4.69.134.245]
    52 
    53   7     *       97 ms   101 ms  ae-2.ebr4.NewYork1.Level3.net [4.69.135.186]
    54   8     *        *       96 ms  ae-94-94.csw4.NewYork1.Level3.net [4.69.134.126]
    55 
    56   9     *        *       83 ms  ae-93-93.ebr3.NewYork1.Level3.net [4.69.134.109]
    57 
    58  10    92 ms    92 ms    88 ms  ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
    59 
    60  11   187 ms   183 ms     *     ae-44-44.ebr2.Frankfurt1.Level3.net [4.69.137.61
    61 ]
    62  12   187 ms   183 ms   190 ms  ae-2-2.ebr1.Dusseldorf1.Level3.net [4.69.132.137
    63 ]
    64  13   394 ms   435 ms   436 ms  ae-6-6.car1.Copenhagen1.Level3.net [4.69.134.29]
    65 
    66  14   186 ms     *      191 ms  ae-11-11.car2.Copenhagen1.Level3.net [4.69.134.2
    67 6]
    68  15   210 ms   203 ms   208 ms  213.242.108.18
    69  16   202 ms     *        *     c10G-ge-7-1-0.cr1.osls.no.catchbone.net [81.0.12
    70 8.245]
    71  17   212 ms   201 ms   213 ms  v4092.rs2.m323.no.catchbone.net [193.75.1.142]
    72  18   410 ms   210 ms   207 ms  193.69.165.11
    73  19   207 ms     *      192 ms  193.69.165.21
    74 
    75 Trace complete.
    76 
    77 C:\Documents and Settings\Administrator>tracert www.wired.com
    78 
    79 Tracing route to a867.g.akamai.net [195.215.37.46]
    80 over a maximum of 30 hops:
    81 
    82   1     1 ms    <1 ms    <1 ms  130.129.16.2
    83   2    18 ms    21 ms    24 ms  66.114.246.1
    84   3    21 ms    19 ms    20 ms  t3-3-1-0-3.edge7.SanJose1.Level3.net [4.53.20.13
    85 ]
    86   4    43 ms    19 ms    22 ms  ae-15-15.car1.SanJose1.Level3.net [4.68.106.249]
    87 
    88   5    28 ms    18 ms    36 ms  vlan99.csw4.SanJose1.Level3.net [4.68.18.254]
    89   6     6 ms    21 ms    21 ms  ae-94-94.ebr4.SanJose1.Level3.net [4.69.134.253]
    90 
    91   7     *      102 ms    90 ms  ae-2.ebr4.NewYork1.Level3.net [4.69.135.186]
    92   8    93 ms    81 ms     *     ae-64-64.csw1.NewYork1.Level3.net [4.69.134.114]
    93 
    94   9    89 ms     *       91 ms  ae-1-69.edge2.NewYork2.Level3.net [4.68.16.12]
    95  10    84 ms     *       81 ms  TDC-SOLUTIO.edge2.NewYork2.Level3.net [4.71.190.
    96 14]
    97  11   188 ms   181 ms   188 ms  te1-1.arcnxc7.dk.ip.tdc.net [83.88.20.218]
    98  12   181 ms   185 ms   184 ms  a195-215-37-46.deploy.akamaitechnologies.com [19
    99 5.215.37.46]
    100 
    101 Trace complete.
    102 
    103 -------------------
    104 
    105 At the time of sending this, wired.com seem to be behaving itself.
     1an issue with an upstream router config has been worked.  are you still seeing a problem?