Strange results on ADSL

rpm

rpm

Admin
Staff member
Joined
Jul 22, 2003
Messages
66,806
Reaction score
5,057
Location
Johannesburg
Hi guys

We have just received some information that pinging a site like mweb.co.za gives very high times (in comparison with other local sites) and that the trace route from Cape Town gives some strange hops on the way to MWeb. If you have some time can you please to a tracert to MWeb and publish your results?

Any idea what the issue may be?

Any feedback will be great.

Regards,

RPM
 
1 <1 ms <1 ms <1 ms [DELETED]
2 11 ms 10 ms 9 ms c1-1-1.tpr.isadsl.co.za [196.209.80.1]
3 15 ms 15 ms 15 ms 196.38.73.181
4 15 ms 15 ms 15 ms curp1-rba-gi6.isdsl.net [196.38.72.238]
5 14 ms 14 ms 15 ms 196.38.72.229
6 13 ms 12 ms 12 ms 196.26.96.203
7 12 ms 14 ms 12 ms core1a-rba-gi2-0-0.rtr.isnet.net [196.26.0.7]
8 37 ms 37 ms 36 ms 168.209.100.74
9 43 ms 38 ms 40 ms 168.209.0.190
10 47 ms 88 ms 55 ms 196.23.49.102
11 56 ms 55 ms 46 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
1 <1 ms <1 ms <1 ms
2 * * * Request timed out.
3 11 ms 11 ms 11 ms 196.38.73.169
4 11 ms 11 ms 11 ms 196.38.73.142
5 12 ms 11 ms 11 ms 196.38.73.137
6 11 ms 11 ms 12 ms 196.26.96.203
7 12 ms 24 ms 11 ms core1a-rba-gi2-0-0.rtr.isnet.net [196.26.0.7]
8 35 ms 36 ms 36 ms 168.209.100.74
9 37 ms 38 ms 37 ms 168.209.0.190
10 51 ms 39 ms 42 ms 196.23.49.102
11 41 ms 39 ms 62 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
From Saix network, Cape Town.

Code: 
ping -n 10 mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:

Reply from 196.2.63.110: bytes=32 time=36ms TTL=112
Reply from 196.2.63.110: bytes=32 time=28ms TTL=112
Reply from 196.2.63.110: bytes=32 time=46ms TTL=112
Reply from 196.2.63.110: bytes=32 time=26ms TTL=112
Reply from 196.2.63.110: bytes=32 time=24ms TTL=112
Reply from 196.2.63.110: bytes=32 time=23ms TTL=112
Reply from 196.2.63.110: bytes=32 time=25ms TTL=112
Reply from 196.2.63.110: bytes=32 time=24ms TTL=112
Reply from 196.2.63.110: bytes=32 time=69ms TTL=112
Reply from 196.2.63.110: bytes=32 time=48ms TTL=112

Ping statistics for 196.2.63.110:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 69ms, Average = 34ms

[-]waiting for tracert to complete...[/-]

Code: 
tracert mweb.co.za

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2    22 ms    21 ms    20 ms  dsl-241-0-01.telkomadsl.co.za [41.241.0.1]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    23 ms    21 ms    22 ms  wblv-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.4
3.11.78]
  6    31 ms    34 ms    39 ms  tiscali-gw.telkom-ipnet.co.za [196.25.55.178]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.
 
Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:

Reply from 196.2.63.110: bytes=32 time=19ms TTL=114
Reply from 196.2.63.110: bytes=32 time=26ms TTL=114
Reply from 196.2.63.110: bytes=32 time=23ms TTL=114
Reply from 196.2.63.110: bytes=32 time=30ms TTL=114

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 30ms, Average = 24ms


Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 18 ms 17 ms 18 ms dsl-240-64-01.telkomadsl.co.za [41.240.64.1]
2 16 ms 18 ms 15 ms wbs-ip-er-1-fe-12-0-1-612.telkom-ipnet.co.za [19
6.43.23.194]
3 19 ms 18 ms 17 ms wbs-ip-er-1-fe-12-0-1-612.telkom-ipnet.co.za [19
6.43.23.194]
4 18 ms 18 ms 19 ms wblv-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.4
3.11.78]
5 17 ms 21 ms 26 ms tiscali-gw.telkom-ipnet.co.za [196.25.55.178]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * ^C

Didn't look like it was going anywhere :P
 
SIAX is busy working on the IS peering links in Cape Town this week.
 
Call Reference ID : STT000000005630
Failure Type : Planned Work
Problem Description : Internet Solution Peering link Cape Town
Time Down : 27 Feb 2007, 19:00:00
Time Up : 27 Feb 2007, 20:00:00
Impact : Clients connecting to Internet Solution peering link Cape Town
Site : Internet Solution
Sites/Services Affected : Internet Solution peering linkCape Town
Estimated Time to Repair : N/A
Updates :

23 Feb 2007, 08:49:07 padayak
Planned maintenance will be performed on Internet Solution`s peering link in Cape Town during the maintenance window on Tuesday 27 February 2007 from 19;00 to 20:00. All customers connecting to Internet Solution`s peering link in Cape Town might experience intermittent service interruptions. Downtime will be kept to a minimum during the planned work. For any queries, please contact our Help Desk on 0800222772.

26 Feb 2007, 09:21:50 padayak
Planned maintenance will be performed on Internet Solution`s peering link in Cape Town during the maintenance window on Tuesday 27 February 2007 from 19;00 to 20:00. All customers connecting to Internet Solution`s peering link in Cape Town might experience intermittent service interruptions. Downtime will be kept to a minimum during the planned work. For any queries, please contact our Help Desk on 0800222772.

27 Feb 2007, 08:20:48 padayak
Planned maintenance will be performed on Internet Solution`s peering link in Cape Town during the maintenance window on Tuesday 27 February 2007 from 19;00 to 20:00. All customers connecting to Internet Solution`s peering link in Cape Town might experience intermittent service interruptions. Downtime will be kept to a minimum during the planned work. For any queries, please contact our Help Desk on 0800222772.


27 Feb 2007, 19:37:48 ndalatp
Planned work has commenced.

27 Feb 2007, 20:41:28 ndalatp
Planned work completed

Cause of Failure : Planned Maintenance
Status : Completed

I only see that one on saix notice board all of the others have in green resolved written on it :rolleyes:
 
Nope, nothing abnormal from Cape Town.

Oops, my mistake, on a diginet line and not ADSL.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X