Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
Well, lovely game without ping. Have 4k ms ping. It is a permanent reconnect.

Tracert:
Code: 
Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    64 ms    61 ms    62 ms  41.181.54.85
  4    62 ms    60 ms    60 ms  ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

  5    38 ms    36 ms    33 ms  tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
  6    46 ms    49 ms    52 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  7   225 ms   221 ms   244 ms  ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]

  8   180 ms   187 ms   186 ms  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
  9   232 ms   234 ms   242 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
 10   224 ms   217 ms   214 ms  xe-4-1-0-135.edge5.Amsterdam1.Level3.net [212.72
.41.89]
 11   276 ms   280 ms   283 ms  ae-0-11.bar2.Vienna1.Level3.net [4.69.153.150]
 12   231 ms   234 ms   230 ms  212.73.202.226
 13   204 ms   208 ms   211 ms  195.3.70.209
 14   262 ms   261 ms   261 ms  ^C

My exchange:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63

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

Was so nice having 189ms while it lasted for a game.

EDIT:
20150609_203813_HDR.jpg
24k ms :(
 
Last edited:
Johnatan56 said:
Well, lovely game without ping. Have 4k ms ping. It is a permanent reconnect.

Tracert:
Code: 
Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    64 ms    61 ms    62 ms  41.181.54.85
  4    62 ms    60 ms    60 ms  ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

  5    38 ms    36 ms    33 ms  tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
  6    46 ms    49 ms    52 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  7   225 ms   221 ms   244 ms  ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]

  8   180 ms   187 ms   186 ms  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
  9   232 ms   234 ms   242 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
 10   224 ms   217 ms   214 ms  xe-4-1-0-135.edge5.Amsterdam1.Level3.net [212.72
.41.89]
 11   276 ms   280 ms   283 ms  ae-0-11.bar2.Vienna1.Level3.net [4.69.153.150]
 12   231 ms   234 ms   230 ms  212.73.202.226
 13   204 ms   208 ms   211 ms  195.3.70.209
 14   262 ms   261 ms   261 ms  ^C

My exchange:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63

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

Was so nice having 189ms while it lasted for a game.

EDIT:
View attachment 223582
24k ms :(
Click to expand...

I hope you don't mind my asking - how do you ping your exchange?
 
Dianysis said:
I hope you don't mind my asking - how do you ping your exchange?
Click to expand...

That address that I am pinging, it is direct to the exchange. Depends on your exchange though (it's the IP of the device behind the port someone told me). So due to them setting it so the exchange does not respond to a tracert, you have to ping direct. There is a thread on it somewhere.

There are two IPs that are possible, depending on model of exchange that are known.

edit: back to 198ms. wtf is going on
 
Last edited:
Johnatan56 said:
That address that I am pinging, it is direct to the exchange. Depends on your exchange though (it's the IP of the device behind the port someone told me). So due to them setting it so the exchange does not respond to a tracert, you have to ping direct. There is a thread on it somewhere.

There are two IPs that are possible, depending on model of exchange that are known.

edit: back to 198ms. wtf is going on
Click to expand...

155.239.255.250 and?
 
Wow, what is going on in Durban, throughput is shot on everything. Can't game heroes and struggling with Google and maps?
 
Johnatan56 said:
Sorry,
http://mybroadband.co.za/vb/showthr...e-now-detect-exchange-congestion#post14935402
There was another thread with another IP, unable to find it atm.
If it doesn't work, you are most likely on an older DSLAM. You could also ask Telkom directly to check congestion on your exchange.
Click to expand...

MY CAPPED ACCOUNT IS VERY VERY SLOW WHEN DOWNLOADING TORRENTS FOR THE PAST WEEK NOW. WHATS UP WITH THAT?? IT USED TO PEFORM VERY WELL. I ONLY DOWNLOAD TORRENTS FROM ONE WEBSITE
 
Johnatan56 said:
Well, lovely game without ping. Have 4k ms ping. It is a permanent reconnect.

Tracert:
Code: 
Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    64 ms    61 ms    62 ms  41.181.54.85
  4    62 ms    60 ms    60 ms  ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

  5    38 ms    36 ms    33 ms  tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
  6    46 ms    49 ms    52 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  7   225 ms   221 ms   244 ms  ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]

  8   180 ms   187 ms   186 ms  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
  9   232 ms   234 ms   242 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
 10   224 ms   217 ms   214 ms  xe-4-1-0-135.edge5.Amsterdam1.Level3.net [212.72
.41.89]
 11   276 ms   280 ms   283 ms  ae-0-11.bar2.Vienna1.Level3.net [4.69.153.150]
 12   231 ms   234 ms   230 ms  212.73.202.226
 13   204 ms   208 ms   211 ms  195.3.70.209
 14   262 ms   261 ms   261 ms  ^C

My exchange:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63

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

Was so nice having 189ms while it lasted for a game.

EDIT:
View attachment 223582
24k ms :(
Click to expand...

I can't see this reflected in the trace route though, seems pretty normal. Could the issue be in-game? Is there any way to ping the server directly?
 
Johnatan56 said:
That address that I am pinging, it is direct to the exchange. Depends on your exchange though (it's the IP of the device behind the port someone told me). So due to them setting it so the exchange does not respond to a tracert, you have to ping direct. There is a thread on it somewhere.

There are two IPs that are possible, depending on model of exchange that are known.

edit: back to 198ms. wtf is going on
Click to expand...

I think it would be great to know more about how this works, because we seem to get different results when we use different ISP accounts as opposed to pinging this IP. I get that the BNG is setup to respond to that ping, but it's strange that it would not respond to a trace route ping but pings on that IP. I'm still trying to get more information about how this works.

I still think the most reliable way is to compare ISP accounts, because those use the routing that will ultimately affect your experience. Testing against the guest account, for example, is problematic as it doesn't appear to route through IPC, so it would not use the same backhaul as regular ISP accounts.
 
Kosmik said:
Wow, what is going on in Durban, throughput is shot on everything. Can't game heroes and struggling with Google and maps?
Click to expand...

everything should have returned to normal in Durbs after auth was resolved around 4pm. Did you run any general tests I can check out?
 
ID_10_T said:
Getting +300ms going through Afrihost network - whatsup?
Click to expand...

Latency should be at normal levels at the moment, where are you seeing this latency? Would you be able to post a traceroute to Afrihost.com perhaps?
 
Ok found the culprit on my network - Google photo's syncing


Tracing route to WWW.AFRIHOST.COM [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 347 ms 154 ms 190 ms 105-236-14-65-esr-lo.mtnbusiness.co.za [105.236.
14.65]
3 270 ms 253 ms 279 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 302 ms 331 ms 426 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 376 ms 502 ms 343 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 248 ms 240 ms 319 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 342 ms 410 ms 396 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.
 
Last edited:
Things have not been to great this past week on my 40mb line, ping is extremely high on local and international sites and some sites don't load at all.. And all is normal on my backup accounts so its not a VDSL issue.

speed test:


And Tracert:
traceroute to www.google.com (216.58.210.4), 30 hops max, 38 byte packets
1 * * *
2 41.181.221.217 (41.181.221.217) 376.798 ms 371.702 ms 365.137 ms
3 41.181.221.218 (41.181.221.218) 357.193 ms 371.441 ms 439.146 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 348.451 ms 393.218 ms 356.865 ms
5 rb-cr-1.za--rb-dca-2.mtnns.net (196.44.31.122) 353.978 ms 377.415 ms 357.636 ms
6 41.181.139.109 (41.181.139.109) 375.168 ms 372.060 ms 41.181.139.99 (41.181.139.99) 343.235 ms
7 72.14.194.74 (72.14.194.74) 378.707 ms 395.338 ms 420.649 ms
8 66.249.95.8 (66.249.95.8) 564.489 ms 542.015 ms 543.281 ms
9 216.239.51.7 (216.239.51.7) 534.474 ms 539.963 ms 553.905 ms
10 216.239.51.2 (216.239.51.2) 537.247 ms 526.876 ms 564.469 ms
11 209.85.250.169 (209.85.250.169) 537.441 ms 522.841 ms 528.186 ms
12 lhr08s06-in-f4.1e100.net (216.58.210.4) 549.879 ms 547.688 ms 551.770 ms

Some help would be greatly appreciated..
 
ID_10_T said:
Ok found the culprit on my network - Google photo's syncing


Tracing route to WWW.AFRIHOST.COM [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 347 ms 154 ms 190 ms 105-236-14-65-esr-lo.mtnbusiness.co.za [105.236.
14.65]
3 270 ms 253 ms 279 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 302 ms 331 ms 426 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 376 ms 502 ms 343 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 248 ms 240 ms 319 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 342 ms 410 ms 396 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.
Click to expand...

Really?! Has that really made a big difference on your connection?
 
tuneme said:
Things have not been to great this past week on my 40mb line, ping is extremely high on local and international sites and some sites don't load at all.. And all is normal on my backup accounts so its not a VDSL issue.

speed test:


And Tracert:
traceroute to www.google.com (216.58.210.4), 30 hops max, 38 byte packets
1 * * *
2 41.181.221.217 (41.181.221.217) 376.798 ms 371.702 ms 365.137 ms
3 41.181.221.218 (41.181.221.218) 357.193 ms 371.441 ms 439.146 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 348.451 ms 393.218 ms 356.865 ms
5 rb-cr-1.za--rb-dca-2.mtnns.net (196.44.31.122) 353.978 ms 377.415 ms 357.636 ms
6 41.181.139.109 (41.181.139.109) 375.168 ms 372.060 ms 41.181.139.99 (41.181.139.99) 343.235 ms
7 72.14.194.74 (72.14.194.74) 378.707 ms 395.338 ms 420.649 ms
8 66.249.95.8 (66.249.95.8) 564.489 ms 542.015 ms 543.281 ms
9 216.239.51.7 (216.239.51.7) 534.474 ms 539.963 ms 553.905 ms
10 216.239.51.2 (216.239.51.2) 537.247 ms 526.876 ms 564.469 ms
11 209.85.250.169 (209.85.250.169) 537.441 ms 522.841 ms 528.186 ms
12 lhr08s06-in-f4.1e100.net (216.58.210.4) 549.879 ms 547.688 ms 551.770 ms

Some help would be greatly appreciated..
Click to expand...

Our Team is already looking into the increased latency in the East, something is definitely off there, they should have things sorted out pronto!
 
AfriMan said:
I think it would be great to know more about how this works, because we seem to get different results when we use different ISP accounts as opposed to pinging this IP. I get that the BNG is setup to respond to that ping, but it's strange that it would not respond to a trace route ping but pings on that IP. I'm still trying to get more information about how this works.

I still think the most reliable way is to compare ISP accounts, because those use the routing that will ultimately affect your experience. Testing against the guest account, for example, is problematic as it doesn't appear to route through IPC, so it would not use the same backhaul as regular ISP accounts.
Click to expand...

The problem with using different ISP accounts is that the ports reset. Then we get a blame game from you guys. The only reason why I post it is to show that it is not exchange congestion related.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X