Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
Code:
traceroute to www.google.co.za (74.125.233.95), 64 hops max, 52 byte packets
 1  router.i.nt (192.168.88.1)  1.951 ms  0.812 ms  0.637 ms
 2  105-236-9-65-esr-lo.mtnbusiness.co.za (105.236.9.65)  9.074 ms  9.281 ms  10.497 ms
 3  ipc-send-tb-3a.mtnbusiness.net (41.181.53.214)  577.116 ms  662.445 ms  614.094 ms
 4  41.181.198.188 (41.181.198.188)  613.619 ms  621.032 ms  564.702 ms
 5  compj-cpt-1.mtnns.net (196.44.18.2)  654.499 ms
    unc-cpt-1.mtnns.net (196.44.18.8)  587.096 ms
    compj-cpt-1.mtnns.net (196.44.18.2)  563.434 ms
 6  196.44.31.106 (196.44.31.106)  567.870 ms
    ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134)  595.803 ms
    196.44.31.106 (196.44.31.106)  573.158 ms
 7  pb-ad-1.za--pb-sla-1-a.mtnns.net (196.44.31.128)  733.520 ms  668.875 ms  657.494 ms
 8  41.181.139.109 (41.181.139.109)  608.327 ms
    41.181.139.99 (41.181.139.99)  595.120 ms  592.349 ms
 9  72.14.194.74 (72.14.194.74)  676.070 ms  719.436 ms  715.889 ms
10  64.233.174.57 (64.233.174.57)  586.887 ms  588.229 ms  579.370 ms
11  jnb01s02-in-f31.1e100.net (74.125.233.95)  600.855 ms  612.698 ms  616.927 ms

something very broken at the moment.. Afriman?

Business 4MB Uncapped.
 
Broken for me too.

Business Uncapped.

Code:
1     1 ms     1 ms     1 ms  10.0.0.2
2    10 ms    10 ms    10 ms  105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3   614 ms   599 ms   579 ms  ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4   599 ms   587 ms   659 ms  41.181.198.188
5   619 ms   613 ms   592 ms  compj-cpt-1.mtnns.net [196.44.18.2]
6   607 ms   601 ms   606 ms  tb-cr-2.za--tb-cr-1.za-a.mtn.net [196.44.31.159]
7   569 ms   576 ms   592 ms  196.7.21.35
8   608 ms   599 ms     *     core-router1.cpt2.host-h.net [196.40.104.66]
9   677 ms   676 ms     *     core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70]
 
Internet extremely slow for some reason :wtf: CPT 10Meg

Both capped and uncapped. Cant manage to get speedtest working long enough for a test :/

1EiP9.jpg


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

1 7 ms 6 ms 7 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
2 604 ms 608 ms * ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
3 612 ms 579 ms 584 ms 41.181.198.188
4 645 ms 615 ms 616 ms unc-cpt-1.mtnns.net [196.44.18.8]
5 583 ms 590 ms * 196.44.31.106
6 * 607 ms * ct-cr-2.za--rb-cr-2.za-a.mtnns.net [196.44.31.30]
7 591 ms 601 ms 614 ms 41.181.139.99
8 682 ms * 687 ms 72.14.194.74
9 594 ms 602 ms 585 ms 64.233.174.21
10 623 ms 633 ms 621 ms jnb01s01-in-f23.1e100.net [74.125.233.55]

Trace complete.


Also, clientzone died on me
5qjNy.jpg
 
Code:
traceroute to www.google.co.za (74.125.233.95), 64 hops max, 52 byte packets
 1  router.i.nt (192.168.88.1)  1.951 ms  0.812 ms  0.637 ms
 2  105-236-9-65-esr-lo.mtnbusiness.co.za (105.236.9.65)  9.074 ms  9.281 ms  10.497 ms
 3  ipc-send-tb-3a.mtnbusiness.net (41.181.53.214)  577.116 ms  662.445 ms  614.094 ms
 4  41.181.198.188 (41.181.198.188)  613.619 ms  621.032 ms  564.702 ms
 5  compj-cpt-1.mtnns.net (196.44.18.2)  654.499 ms
    unc-cpt-1.mtnns.net (196.44.18.8)  587.096 ms
    compj-cpt-1.mtnns.net (196.44.18.2)  563.434 ms
 6  196.44.31.106 (196.44.31.106)  567.870 ms
    ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134)  595.803 ms
    196.44.31.106 (196.44.31.106)  573.158 ms
 7  pb-ad-1.za--pb-sla-1-a.mtnns.net (196.44.31.128)  733.520 ms  668.875 ms  657.494 ms
 8  41.181.139.109 (41.181.139.109)  608.327 ms
    41.181.139.99 (41.181.139.99)  595.120 ms  592.349 ms
 9  72.14.194.74 (72.14.194.74)  676.070 ms  719.436 ms  715.889 ms
10  64.233.174.57 (64.233.174.57)  586.887 ms  588.229 ms  579.370 ms
11  jnb01s02-in-f31.1e100.net (74.125.233.95)  600.855 ms  612.698 ms  616.927 ms

something very broken at the moment.. Afriman?

Business 4MB Uncapped.

Yip...mine looks the same. Looks like IPC problems in Cape Town ? Almost not usable at the moment.
 
Dead for me too! I'm in Somerset West too. Blunt, where are you based?

C:\Users\chris>ping google.co.za

Pinging google.co.za [74.125.233.56] with 32 bytes of data:
Request timed out.
Reply from 74.125.233.56: bytes=32 time=639ms TTL=51
Reply from 74.125.233.56: bytes=32 time=635ms TTL=51
Reply from 74.125.233.56: bytes=32 time=632ms TTL=51

Ping statistics for 74.125.233.56:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 632ms, Maximum = 639ms, Average = 635ms
 
Dead for me too! I'm in Somerset West too. Blunt, where are you based?

C:\Users\chris>ping google.co.za

Pinging google.co.za [74.125.233.56] with 32 bytes of data:
Request timed out.
Reply from 74.125.233.56: bytes=32 time=639ms TTL=51
Reply from 74.125.233.56: bytes=32 time=635ms TTL=51
Reply from 74.125.233.56: bytes=32 time=632ms TTL=51

Ping statistics for 74.125.233.56:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 632ms, Maximum = 639ms, Average = 635ms

Plumstead
 
Im in Somerset West - Link 2 between the Cape Town IPC and the MTN line is broken I think
 
I had to switch to a Telkom account. Mybroadband is very slow as well. Something that side has broken.
 
Mine has come back to life too! I guess IPC was the issue, although I can't be certain. Bloody Telkom!
 
(At time of writing.... still checking)
Gone again! Both through put and Afri* Capped and uncapped.
 
Looks like something broke on the Southern IPC. Not an outage as such, but some sort of network anomaly that sent contention through the roof. That's why throughput and latency went bananas.

We've isolated the cause and killed it, so this shouldn't happen again :)
 
Looks like something broke on the Southern IPC. Not an outage as such, but some sort of network anomaly that sent contention through the roof. That's why throughput and latency went bananas.

We've isolated the cause and killed it, so this shouldn't happen again :)

@AfriMan, can you elaborate on exactly what happened?
 
@AfriMan, can you elaborate on exactly what happened?

It's looks like something went wrong with one of our policies, and allowed completely unrestricted throughput, causing massive contention. We had to kill those sessions and restore the correct policies to normalise network performance.
 
well now how are you going to make a movie with the approval of the Humanity for Data Foundation: "no sessions were killed in the making of this film" carries weight among some film goers
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X