Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
AfriMan said:
Yeah, looking like it. We're busy waiting for confirmation on this though :(
Click to expand...

Ouch, PE here. Something is definitely wrong. Barely getting 200kbps on a 4mb line when speedtest actually loads (dies most times).

Ping

Pinging google.com [173.194.34.162] with 32 bytes of data:
Reply from 173.194.34.162: bytes=32 time=613ms TTL=52
Reply from 173.194.34.162: bytes=32 time=614ms TTL=52
Reply from 173.194.34.162: bytes=32 time=612ms TTL=52
Reply from 173.194.34.162: bytes=32 time=612ms TTL=52

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


Tracert

Tracing route to google.com [173.194.34.162]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms login.router [10.0.0.2]
2 8 ms 8 ms 7 ms 105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.
8.129]
3 508 ms 458 ms 462 ms 41.181.51.182
4 464 ms 469 ms 465 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 * 462 ms 458 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 621 ms 632 ms 610 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]

7 620 ms 621 ms 623 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
8 650 ms 650 ms 649 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
9 617 ms 616 ms 619 ms core2.ams.net.google.com [195.69.145.100]
10 609 ms * 611 ms 209.85.254.90
11 625 ms 625 ms 667 ms 72.14.238.153
12 620 ms 618 ms 615 ms 209.85.246.155
13 616 ms 612 ms 611 ms 209.85.253.197
14 607 ms 607 ms 603 ms 209.85.253.175
15 * 614 ms 613 ms google.com [173.194.34.162]

Trace complete.
Click to expand...
 
From the Plug Uncapped thread.

"Some of IS' IPC links in Cape Town are currently down; they have been reported to SAIX and currently waiting on feedback.

You might experience some packet loss & increased latency if you find yourself connecting from the Cape region.

No ETA at this stage."
 
Phinix said:
From the Plug Uncapped thread.

"Some of IS' IPC links in Cape Town are currently down; they have been reported to SAIX and currently waiting on feedback.

You might experience some packet loss & increased latency if you find yourself connecting from the Cape region.

No ETA at this stage."
Click to expand...

We're also seeing reports from other ISPs also having issues. We still don't have confirmation on what the cause is until Telkom confirm from their side. Seeing as more than one ISP is having a problem, it's unlikely to be IPC - but we'll need to confirm.

As far as we can see throughput is still fine, but latency is awful - we're still seeing a huge drop off in traffic though :(
 
Hell no throughput is not fine. 4mb turned into sludge. Cannot stream anything to save my life...not even gonna try downloading.
 
Network Notice

There is currently a major issue affecting all clients in the Western Cape, Eastern Cape and Surrounds.

2 of the 4 x Telkom IPC links are down.

Engineers are attending.

We apologise for the inconvenience
 
Pretty weird, Telkom have confirmed with MTN that there is an IPC issue, so not sure how other ISP's are having the exact same issue at the same time.

Telkom are investigating though, let's see what they say when it looks like they've identified the problem :(
 
Mine started at 5pm yesterday.

Richmond KZN, I thought it was just me, but Gmail, Skype everything is slow and timing out!

even myBB is slow...... :whistle:
 
AfriMan said:
Pretty weird, Telkom have confirmed with MTN that there is an IPC issue, so not sure how other ISP's are having the exact same issue at the same time.
Click to expand...

Why is it weird?? Just taking a guess here, but maybe it is because all the IPCs in CTN from Telkom originates from the same place ;-)

So if there is say, a SDH down on Telkom's side, why would it not affect all ISPs?

Michael
 
Network Notice

There is currently a major issue affecting all clients in the Western Cape, Eastern Cape and Surrounds.

2 of the 4 x Telkom IPC links are down.

Engineers are attending.

We apologise for the inconvenience
 
Grizz said:
Network Notice

There is currently a major issue affecting all clients in the Western Cape, Eastern Cape and Surrounds.

2 of the 4 x Telkom IPC links are down.

Engineers are attending.

We apologise for the inconvenience
Click to expand...

Well that is pretty pointless to Afrihost customers. Why would an outage notification from Internet Solutions have any bearing on Afrihost customers seeing that AH uses MTN's backbone ??

Michael
 
mikeygza said:
Why is it weird?? Just taking a guess here, but maybe it is because all the IPCs in CTN from Telkom originates from the same place ;-)

So if there is say, a SDH down on Telkom's side, why would it not affect all ISPs?

Michael
Click to expand...

I'm not sure how it works in CT, but our IPC is physically at the MTN Tygerberg data centre, even though the IPC ultimately belongs to Telkom and we are not allowed to touch it. It could be that links correspond to Telkom links elsewhere, but my understanding is that this is where traffic breaks out of the network directly from Telkom, so there would be no further link to another ISPs IPC.

Also, usually IPC going down usually kills all connectivity, not just partially like we're seeing. Definitely unusual, not that this kind of thing should happen often enough to be considered "usual" :(
 
I keep getting "Unable to contact Gmail"
Skype is dropping calls every 2 -5 Mins

But my latency is fine, no packet loss either.....

Does not make sense, Afriman are you sure there is not a wider problem then initially thought?
Vodacom 3G is doing the same as my Afrihost DSL......
 
Awesome, thanks for the feedback guys :)
Things do look to be normalising on our end. We're continuing to monitor though.
 
Not looking good at hop 6

Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 7 ms 7 ms 8 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.10.1]
3 23 ms 25 ms 22 ms ipc-recieve-ng-1a.mtnbusiness.net [41.181.201.14]
4 46 ms 18 ms 18 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]
5 19 ms 18 ms 19 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]
6 134 ms 128 ms 123 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
7 221 ms 220 ms 224 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.165.119]
8 219 ms 20 ms 22 ms 196.30.1.53
9 219 ms 23 ms 118 ms tengigabitethernet9-1.gw21.jnb6.za.mtnbusiness.net [196.31.220.27]
10 249 ms 21 ms * tengigabitethernet5-2.hr15.jnb6.za.mtnbusiness.net [196.31.63.194]
11 327 ms * 25 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57

Reply from 197.242.144.102: bytes=32 time=48ms TTL=57
Request timed out.
Reply from 197.242.144.102: bytes=32 time=51ms TTL=57
Request timed out.
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=57ms TTL=57
Request timed out.
Request timed out.
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Request timed out.
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=26ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Request timed out.
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=30ms TTL=57
Request timed out.
Request timed out.
Reply from 197.242.144.102: bytes=32 time=104ms TTL=57
Reply from 197.242.144.102: bytes=32 time=125ms TTL=57
Reply from 197.242.144.102: bytes=32 time=122ms TTL=57
Reply from 197.242.144.102: bytes=32 time=223ms TTL=57
Reply from 197.242.144.102: bytes=32 time=122ms TTL=57
Reply from 197.242.144.102: bytes=32 time=222ms TTL=57
Reply from 197.242.144.102: bytes=32 time=223ms TTL=57
Reply from 197.242.144.102: bytes=32 time=222ms TTL=57
Reply from 197.242.144.102: bytes=32 time=222ms TTL=57
 
Hummercellc said:
Not looking good at hop 6

Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 7 ms 7 ms 8 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.10.1]
3 23 ms 25 ms 22 ms ipc-recieve-ng-1a.mtnbusiness.net [41.181.201.14]
4 46 ms 18 ms 18 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]
5 19 ms 18 ms 19 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]
6 134 ms 128 ms 123 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
7 221 ms 220 ms 224 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.165.119]
8 219 ms 20 ms 22 ms 196.30.1.53
9 219 ms 23 ms 118 ms tengigabitethernet9-1.gw21.jnb6.za.mtnbusiness.net [196.31.220.27]
10 249 ms 21 ms * tengigabitethernet5-2.hr15.jnb6.za.mtnbusiness.net [196.31.63.194]
11 327 ms * 25 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57

Reply from 197.242.144.102: bytes=32 time=48ms TTL=57
Request timed out.
Reply from 197.242.144.102: bytes=32 time=51ms TTL=57
Request timed out.
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=57ms TTL=57
Request timed out.
Request timed out.
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Request timed out.
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=26ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Request timed out.
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=30ms TTL=57
Request timed out.
Request timed out.
Reply from 197.242.144.102: bytes=32 time=104ms TTL=57
Reply from 197.242.144.102: bytes=32 time=125ms TTL=57
Reply from 197.242.144.102: bytes=32 time=122ms TTL=57
Reply from 197.242.144.102: bytes=32 time=223ms TTL=57
Reply from 197.242.144.102: bytes=32 time=122ms TTL=57
Reply from 197.242.144.102: bytes=32 time=222ms TTL=57
Reply from 197.242.144.102: bytes=32 time=223ms TTL=57
Reply from 197.242.144.102: bytes=32 time=222ms TTL=57
Reply from 197.242.144.102: bytes=32 time=222ms TTL=57
Click to expand...

I can't seem to replicate this on my end, maybe it just needed a bit more time normalise?
Could you test again for me please.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X