Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Wonder if one of you AfriFolk can assist. Do you keep track on your system when you request/do port resets or moving of ports on the exchange?
On 5 Aug I spoke to telkom directly, because I was troubleshooting why I was not getting 10Mbps on a Telkom capped account. The support person said he's going to move me to another port (did not even know they could do that remotely) and do a a reset. After he did that my exchange latency went down drastically. When pinging bras.afrihost.com I was usually getting 20-25ms and after his actions it was down to 6-8ms.
Then on 19 Aug it all went back to 20-25ms again. The only thing I can think of is that you guys requested a port move, because I have an open support ticket regarding issues in the evening.
 
standerr said:
Wonder if one of you AfriFolk can assist. Do you keep track on your system when you request/do port resets or moving of ports on the exchange?
On 5 Aug I spoke to telkom directly, because I was troubleshooting why I was not getting 10Mbps on a Telkom capped account. The support person said he's going to move me to another port (did not even know they could do that remotely) and do a a reset. After he did that my exchange latency went down drastically. When pinging bras.afrihost.com I was usually getting 20-25ms and after his actions it was down to 6-8ms.
Then on 19 Aug it all went back to 20-25ms again. The only thing I can think of is that you guys requested a port move, because I have an open support ticket regarding issues in the evening.
Click to expand...

Any Telkom faults that are logged onto our system are tracked, but we can't track something that Telkom do - only what's actioned on our end.

As mentioned, please chat to Critical Care to see any pending queries resolved.
 
Why would Afrihost move your port - if you have a Telkom capped account?

Maybe a Telkom call centre agent switched your port out ("remotely ported") with another person's port a few calls later, to get that customer off their neck? That I expect happens a lot - there are only so many ports...to port to.
 
AfriGuy said:
Hhmm, not really sure what this means.
I can tell you it's coming from one of our DNS servers, but shouldn't be anything malicious.

How often does this appear in the logs?
Click to expand...

I dont check my logs often, just opened it today and saw.

But I will keep monitoring it.


Also any price decreases in the works? A while ago you told me to <watch this space>.
 
DeSLAM said:
Why would Afrihost move your port - if you have a Telkom capped account?

Maybe a Telkom call centre agent switched your port out ("remotely ported") with another person's port a few calls later, to get that customer off their neck? That I expect happens a lot - there are only so many ports...to port to.
Click to expand...

Because I'm an Afrihost client with an Afrihost logged ticket, and they might be trying things their side to sort it out. They also manage my line.
I was only testing with a Telkom account.
 
standerr said:
Because I'm an Afrihost client with an Afrihost logged ticket, and they might be trying things their side to sort it out. They also manage my line.
I was only testing with a Telkom account.
Click to expand...

OK now that makes sense...
 
Rickster said:
I dont check my logs often, just opened it today and saw.

But I will keep monitoring it.


Also any price decreases in the works? A while ago you told me to <watch this space>.
Click to expand...

Fibre's taking all the action at the moment, any changes will be broadcast though :)
 
Tracing route to www.afrihost.co.za [41.86.112.68]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 368 ms 461 ms 448 ms 169-0-49-1.ip.afrihost.co.za [169.0.49.1]
3 330 ms 350 ms 404 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 383 ms 405 ms 542 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 371 ms 369 ms 437 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 319 ms 366 ms 405 ms optinet.ixp.capetown [196.10.140.145]
7 471 ms 452 ms 457 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
8 507 ms 484 ms 454 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
9 453 ms 460 ms 493 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
10 489 ms 513 ms * 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
11 508 ms 485 ms 408 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
12 463 ms 534 ms 532 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
13 420 ms 438 ms 492 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
14 * 493 ms 480 ms www.afrihost.co.za [41.86.112.68]
 
Gonzo.B said:
Tracing route to www.afrihost.co.za [41.86.112.68]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 368 ms 461 ms 448 ms 169-0-49-1.ip.afrihost.co.za [169.0.49.1]
3 330 ms 350 ms 404 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 383 ms 405 ms 542 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 371 ms 369 ms 437 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 319 ms 366 ms 405 ms optinet.ixp.capetown [196.10.140.145]
7 471 ms 452 ms 457 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
8 507 ms 484 ms 454 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
9 453 ms 460 ms 493 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
10 489 ms 513 ms * 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
11 508 ms 485 ms 408 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
12 463 ms 534 ms 532 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
13 420 ms 438 ms 492 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
14 * 493 ms 480 ms www.afrihost.co.za [41.86.112.68]
Click to expand...

Looks like the latency is coming in at your exchange.
Any services running in the background?
 
Yeah just checked a couple times,guess the dslam is congested. Not lus to deal with telkom now.
 
Rickster said:
Why are the exchanges congested all of a sudden?


#bringinLLU
Click to expand...

Not sure about exchange congestion outside of planned fibre areas, but I know that Telkom aren't upgrading areas that are planned for fibre.
 
Last edited:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Dell>ping mybroadband.co.za

Pinging mybroadband.co.za [104.20.72.110] with 32 bytes of data:
Reply from 104.20.72.110: bytes=32 time=137ms TTL=56
Reply from 104.20.72.110: bytes=32 time=164ms TTL=56
Reply from 104.20.72.110: bytes=32 time=181ms TTL=56
Reply from 104.20.72.110: bytes=32 time=96ms TTL=56

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

C:\Users\Dell>tracert google.co.za

Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 11 ms 10 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 15 ms 11 ms 11 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 12 ms 13 ms 9 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 11 ms 11 ms 11 ms 41.164.52.40
7 62 ms 73 ms 94 ms 172.18.1.162
8 * 32 ms 33 ms 72.14.194.206
9 33 ms * 33 ms 72.14.239.129
10 72 ms 74 ms 76 ms jnb01s08-in-f35.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Dell>
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X