Looks alright, but there is definitely a jump now and then. Please would you run it when there are evident issues on your line!
Z
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Which is the most hair-raising South African mountain pass you've driven?
Afrihost New Network Feedback
- Thread starter AfriMan
- Start date
- Status
Looks alright, but there is definitely a jump now and then. Please would you run it when there are evident issues on your line!
Z
Why the routing through Lisbon - London - Is that normal?Seeing huge latency to your exchange here, possibly due to congestion
Will do.
Why the routing through Lisbon - London - Is that normal?Seeing huge latency to your exchange here, possibly due to congestion
It depends on the destination, you shouldn't be routing internationally for MyBB though.
Here are my results:
Code:
traceroute to mybroadband.co.za (104.20.71.110), 64 hops max
1 192.168.1.1 0.470ms 0.361ms 0.367ms
2 * * *
3 * 169.1.5.105 18.781ms 17.777ms
4 169.1.5.106 18.425ms 17.896ms 17.942ms
5 169.1.5.128 17.478ms 16.891ms 17.259ms
6 196.10.140.7 18.187ms 18.158ms 18.436ms
7 41.84.13.228 33.874ms 34.140ms 33.778ms
8 41.66.181.59 34.460ms 33.359ms 34.192ms
9 104.20.71.110 34.124ms 33.959ms 35.317msWell that trace was to MyBB - any idea what's up then with the international route over 17 hops?
Everything's pretty crap at the moment.
There could be some Cloudflare weirdness there. You mind running a ping to see what IP is resolving?
I presume you mean a ping to MyBB?
Pinging mybroadband.co.za [104.20.71.110] with 32 bytes of data:
Request timed out.
Reply from 104.20.71.110: bytes=32 time=1692ms TTL=42
Reply from 104.20.71.110: bytes=32 time=2513ms TTL=43
Reply from 104.20.71.110: bytes=32 time=3050ms TTL=43
Ping statistics for 104.20.71.110:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1692ms, Maximum = 3050ms, Average = 2418ms
Indeed I did.
That's a CloudFlare IP, shouldn't be going internationally though. Quite hard to troubleshoot with all this exchange latency
What DNS servers are you using?
ghostR
Executive Member
- Joined
- Feb 11, 2015
- Messages
- 6,142
- Reaction score
- 39
If you PM me a Line Number, I can post a DSLAM graph...
roadcat
Expert Member
Just got home to this 
Nice.
[/URL][/IMG]
Nice.
LaraC
Honorary Master
- Joined
- Mar 11, 2014
- Messages
- 42,673
- Reaction score
- 1,847
Test with Afrihost's network tool.
Code:
Ping Test:
ping 197.242.144.102
64 bytes from 197.242.144.102: icmp_req=1 ttl=53 time=54 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=53 time=54 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=53 time=54 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=53 time=54 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=53 time=55 ms
ping 8.8.8.8
Request timeout for icmp_seq 1
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=39 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=39 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=38 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=38 ms
Trace Test:
traceroute -n 197.242.144.102
1 192.168.1.1 1 ms 1 ms 1 ms
2 Request timed out * * *
3 169.1.5.8 23 ms 23 ms 24 ms
4 169.1.5.9 24 ms 24 ms 24 ms
5 169.1.5.1 23 ms 23 ms 24 ms
6 41.164.52.4 24 ms 24 ms 24 ms
7 172.18.32.3 25 ms 24 ms 24 ms
8 196.223.22.3 25 ms 25 ms 25 ms
9 196.44.0.7 25 ms 26 ms 25 ms
10 196.44.31.9 54 ms
196.44.0.2 55 ms 54 ms
11 196.30.1.5 48 ms 48 ms 48 ms
12 196.30.1.5 48 ms
196.31.220.2 54 ms 54 ms 54 ms
13 196.31.220.2 55 ms
196.31.63.2 47 ms 47 ms 47 ms
14 196.30.42.1 61 ms 62 ms
197.242.144.1 54 ms 54 ms
15 197.242.144.1 54 ms 54 ms
traceroute -n 8.8.8.8
1 192.168.1.1 1 ms 1 ms
2 Request timed out * *
3 169.1.5.8 17 ms 16 ms
4 169.1.5.8 24 ms 23 ms
5 169.1.5.1 16 ms
6 41.164.52.4 17 ms
7 172.18.1.1 37 ms
8 72.14.194.2 46 ms
9 8.8.8.8 39 ms
DNS Test:
nslookup www.afrihost.com
Name: www.afrihost.com
Address: 41.181.185.18
nslookup www.google.com
Name: www.google.com
Address: 216.58.223.4
nslookup thishouldfail.afrihost.com
** server can't find thisshouldfail.com: NXDOMAINIndeed I did.
That's a CloudFlare IP, shouldn't be going internationally though. Quite hard to troubleshoot with all this exchange latency
What DNS servers are you using?
How do I see what DNS servers are being used?
cortexenslaver
Senior Member
YES, it is specific to Afrihost.... I proved it via pm to you. Secondly, my host did NOT change a thing on their side. They in fact gave the same response as you regarding the range of IP. If it were not an AH issue, then how do you explain the other clients getting SMTP errors on AH (see post #1325 above)... are you now trying to say this is mere coincidence?
All the posts for the last 3 days have covered a range of issues in the SOUTH. In the last 2 days I have had 5 random resets/loss of sync, and when the line came back up, I saw your pm that it was now working.
I can assure you that NOTHING changed on the host side - if it had, they would be obligated to inform me, and get consent to access my VPS. I have been with them for 3 years without even ONE issue after initial setup. The SMTP errors, delayed emails, etc. have only been present since your POC, and only when I connect with an AH account.
How else do you explain that NO OTHER ISP ACCOUNT could reproduce the error, even once? Many tried to telnet to the box from AH, and NONE could get through.... but on Axxess, Telkom, WA, VOX, MWEB and CW, port 587 is open and working. Nevertheless, it is now "sort of" working... the errors are appearing less frequently, and port 587 is accessible from both AH user names (AH & AG).
If it's a setting that hasn't been changed you're probably using auto-assigned DNS entries.
Could you double check the router though? They're usually under the same settings page as your DSL username/ password.
You mentioned the host uses a 169 IP range as internal traffic, which in turn blocks or implements port knocking from internal requests.
Either way, the issue is fixed. Whether it was a fix from our team reaching our, a change on our end or theirs - it's working.
- Status