Afrihost New Network Feedback - Part 2

[Devo1]

Excellent! Which DSL line speed are you thinking of upgrading to?

Just to 4mbps. Dont really need anything higher right now. Will maybe consider it later on.

Telkom said that the traffic to the DSLAM was low and has been optimized?

 

[LaraC]

Just to 4mbps. Dont really need anything higher right now. Will maybe consider it later on.

Telkom said that the traffic to the DSLAM was low and has been optimized?

I'm glad your line issues were solved.

 

[User52]

Anyone here not able to load news24.com website or just me?

 

[AfriGuy]

Anyone here not able to load news24.com website or just me?

Loads up OK on my end

 

[User52]

Must be UnoTelly dns service...

 

[Hummercellc]

Anyone here not able to load news24.com website or just me?

I had the same problem earlier, would not open on Afrihost, but fine on Mweb. Working for now as well.

 

[AfriGuy]

Must be UnoTelly dns service...

I had the same problem earlier, would not open on Afrihost, but fine on Mweb. Working for now as well.

If you're still seeing issues, would you mind posting a traceroute/ MTR?

 

[Hummercellc]

If you're still seeing issues, would you mind posting a traceroute/ MTR?

It's working again, Standard Bank still slow to respond on Afrihost, but fast on other ISP's. Trace Routes show no problems to Standard Bank.

 

[User52]

Tested using 8.8.8.8 DNS and still not working. Here is a traceroute to news24.com:

1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.10.1]
2 <1 ms <1 ms <1 ms 192.168.0.1
3 * * * Request timed out.
4 25 ms 23 ms 23 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 27 ms 23 ms 23 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 23 ms 23 ms 23 ms optinet.db1.napafrica.net [196.10.141.75]
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.

 

[AfriGuy]

It's working again, Standard Bank still slow to respond on Afrihost, but fast on other ISP's. Trace Routes show no problems to Standard Bank.

http://www.standardbank.co.za/standardbank/ loads up pretty quickly for me.
Does an MTR show any packet-loss along the way?

 

[AfriGuy]

Tested using 8.8.8.8 DNS and still not working. Here is a traceroute to news24.com:

1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.10.1]
2 <1 ms <1 ms <1 ms 192.168.0.1
3 * * * Request timed out.
4 25 ms 23 ms 23 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 27 ms 23 ms 23 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 23 ms 23 ms 23 ms optinet.db1.napafrica.net [196.10.141.75]
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.

Odd. Things seem to be a bit wonky after NAPAfrica.
Here's my traceroute from CPT, mind testing auto-DNS to see if this helps?

traceroute to news24.com (41.86.110.143), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.1) 1.463 ms 1.135 ms 1.002 ms
2 * * *
3 cpt-up1.ip.adsl.co.za (169.1.5.105) 16.344 ms 11.859 ms 13.094 ms
4 cpt-up2.ip.adsl.co.za (169.1.5.106) 15.464 ms 13.346 ms 14.025 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 14.862 ms 15.029 ms 15.974 ms
6 optinet.ct1.napafrica.net (196.10.140.145) 36.902 ms 38.313 ms 47.378 ms
7 te0-0-0-1.cpt-p-2.optinet.net (197.84.7.34) 16.259 ms
te0-7-0-3.cpt-p-2.optinet.net (197.84.7.2) 15.725 ms
bu-ether1.cpt-p-1.optinet.net (197.84.7.33) 126.695 ms
8 vl12.cpt-hscore-2.optinet.net (197.84.5.254) 15.200 ms 15.785 ms 14.735 ms
9 vp-02-14.bb.ctn.c27.za.net (196.28.178.70) 25.119 ms
196.28.178.66 (196.28.178.66) 44.560 ms 46.331 ms
10 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 91.411 ms 105.429 ms 98.212 ms
11 opti-cpt-n1-hosting.optinet.net (197.84.196.6) 18.594 ms 16.419 ms 15.402 ms
12 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 18.096 ms 16.139 ms 16.811 ms
13 41-86-110-143.mweb.co.za (41.86.110.143) 125.555 ms 126.164 ms 122.202 ms

 

[User52]

This is with DNS set to auto (Afrihost):

1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.10.1]
2 <1 ms <1 ms <1 ms DGND3800B.lan [192.168.0.1]
3 * * * Request timed out.
4 41 ms 25 ms 27 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 62 ms 65 ms 56 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 24 ms 24 ms 23 ms optinet.db1.napafrica.net [196.10.141.75]
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.

 

[User52]

Had this issue last night as well. Was fine in the day/ morning today.

 

[AfriGuy]

This is with DNS set to auto (Afrihost):

1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.10.1]
2 <1 ms <1 ms <1 ms DGND3800B.lan [192.168.0.1]
3 * * * Request timed out.
4 41 ms 25 ms 27 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 62 ms 65 ms 56 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 24 ms 24 ms 23 ms optinet.db1.napafrica.net [196.10.141.75]
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.

Hhhmm, the same results
Battling to see what's wrong here - monitoring shows up all good from our end.

Anyone else in DBN able to test news24.com?

 

[User52]

On Vodacom 4g works just fine. Not an issue for me, just something I noticed.

 

[wingnut771]

tracert www.news24.com

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

1 * * * Request timed out.
2 15 ms 33 ms 16 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
3 34 ms 44 ms 31 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
4 27 ms 23 ms 19 ms optinet.db1.napafrica.net [196.10.141.75]
5 72 ms 72 ms 71 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
6 155 ms 153 ms 161 ms te0-7-0-1.vic-p-2.optinet.net [197.84.4.44]
7 47 ms 45 ms 43 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
8 43 ms 42 ms 42 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 45 ms 42 ms 43 ms 196.28.178.66
10 42 ms 41 ms 41 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]

11 145 ms 148 ms 146 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
12 146 ms 149 ms 149 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
13 131 ms 127 ms 131 ms 41-86-110-200.mweb.co.za [41.86.110.200]

Trace complete.

EDIT: Auto DNS
169.1.1.4
169.1.1.10

EDIT 2: Last 3 hops seem high.

 

[Rickster]

Is it me or does browsing feel sloppy now?

 

[Hummercellc]

Is it me or does browsing feel sloppy now?

Speeds do seem to a little lower than usual, Latency also slightly higher.

 

[Dianysis]

Anyone else having wonky p2p, international throughput and Google play store updates?
My vox account however runs nice and smooth.....

 

[pvanheus]

Anyone else having wonky p2p, international throughput and Google play store updates?
My vox account however runs nice and smooth.....

I'm having problems with slack (and with my connection to our work network that runs on neotel). Haven't tried play store and other international sites like facebook are running fine right now.

slack.com ping results:

100 packets transmitted, 100 received, 0% packet loss, time 99091ms
rtt min/avg/max/mdev = 177.165/234.119/1010.670/113.874 ms, pipe 2


As to the problem connecting to Neotel, there seems to be packet loss between cpt-net1.ip.adsl.co.za (169.1.5.128) and 41.164.52.40. Possibly congestion at a peering point?

Peter