Hi JasonAh this might explain why my server is unreachable from vodacom on my phone, thanks for the feedback @Jade @ Absolute Hosting
That should only have been the case earlier this morning and not last night?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Hi JasonAh this might explain why my server is unreachable from vodacom on my phone, thanks for the feedback @Jade @ Absolute Hosting
Hi Jason
That should only have been the case earlier this morning and not last night?
Thank you for the feedbackI'm not sure about last night, only noticed the issue connecting from vodacom today, but connectivity from my cool ideas connection still seems good![]()
Eish.. Hope you have done backups / snapshots... Yesterday I had to restore as something got corrupt. Any update crashed the vps... Even clearing the litespeed cache crashed the server...Hi @Jade @ Absolute Hosting having troube connecting to epyc server is it down? everything is timing. out! First day of a pmassive customers launch![]()
Please DM me your ticket number. Afaik no issues reported with clients VPS serversHi @Jade @ Absolute Hosting having troube connecting to epyc server is it down? everything is timing. out! First day of a pmassive customers launch![]()
No issues at the moment - please log a ticket and we can assistHi @Jade @ Absolute Hosting, are VPS machines down at the moment? Can't access ours for the past 10 minutes?
Best,
Yousha
Hi @Jade @ Absolute Hosting , i am struggling to log into my account. currently not getting the OTP. Please assist. You can email me at (redacted). Thanks
Morning, I have sent you a DMPlease help, I cant log in NO 2FA ?
Through my Lightstruck Fibre - Cannot connect
```
traceroute to 102.214.x.x (102.214.x.x), 30 hops max, 60 byte packets
1 _gateway (192.168.x.x) 3.717 ms 3.607 ms 3.578 ms
2 192.168.x.x (192.168.x.x) 3.755 ms 3.725 ms 3.698 ms
3 3.124.216.102.interworks.co.za (102.216.124.3) 26.249 ms 27.711 ms 27.690 ms
4 21.124.216.102.interworks.co.za (102.216.124.21) 27.716 ms 27.694 ms 27.672 ms
5 b-db1-2.interworks.co.za (160.19.112.137) 27.612 ms 27.590 ms 27.571 ms
6 142.112.19.160.interworks.co.za (160.19.112.142) 34.576 ms 30.500 ms 30.729 ms
7 napafricajhb.liquidtelecom.net (196.60.8.215) 32.561 ms 33.616 ms 33.548 ms
8 77.246.58.98.liquidtelecom.net (77.246.58.98) 33.493 ms 24.417 ms 53.548 ms
9 be-20.lza-pe2-jhb.liquidtelecom.net (41.60.135.93) 69.522 ms 69.755 ms 69.447 ms
10 41.175.247.151 (41.175.247.151) 56.006 ms 55.975 ms 55.938 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
```
Through a VM at Teraco - Can connect, no issues
```
traceroute to 102.214.x.x (102.214.x.x), 30 hops max, 60 byte packets
1 _gateway (192.168.x.x) 0.240 ms 0.194 ms 0.190 ms
2 zatjnb01-br04.syrex.co.za (41.79.22.37) 0.404 ms 0.379 ms 0.360 ms
3 198.19.37.157 (198.19.37.157) 0.649 ms 0.576 ms 0.673 ms
4 jinx.liquid.tech (196.60.96.55) 1.692 ms 1.805 ms 1.917 ms
5 be-20.lza-pe2-jhb.liquidtelecom.net (41.60.135.93) 1.124 ms 1.308 ms 1.120 ms
6 41.175.247.151 (41.175.247.151) 1.096 ms 1.160 ms 1.123 ms
7 zero-three.ah.africa (102.211.207.11) 1.158 ms 1.208 ms 1.173 ms
8 102-214-x-x.zadns.co.za (102.214.x.x) 1.346 ms 1.347 ms 1.403 ms
```
Through MTN Data - Can connect, no issues
```
traceroute to 102.214.x.x (102.214.x.x), 30 hops max, 60 byte packets
1 _gateway (10.x.x.x) 7.825 ms 7.701 ms 7.664 ms
2 172.16.x.x (172.16.x.x) 614.626 ms 614.597 ms 614.581 ms
3 10.x.x.x (10.x.x.x) 616.098 ms 10.x.x.x (10.x.x.x) 615.811 ms 10.x.x.x (10.x.x.x) 615.805 ms
4 10.x.x.x (10.x.x.x) 618.295 ms 618.273 ms 10.x.x.x (10.x.x.x) 615.394 ms
5 be21551.ng-p-01.za.mtnns.net (196.4.90.155) 633.918 ms 638.325 ms 638.919 ms
6 196-10-141-66.ixp.durban (196.10.141.66) 641.869 ms 633.073 ms 632.998 ms
7 xe-0-1-1.er-01-dur.za.seacomnet.com (105.16.10.205) 644.943 ms 252.877 ms 252.782 ms
8 105.25.162.117 (105.25.162.117) 252.739 ms 374.560 ms 374.495 ms
9 ce-1-0-2.er-02-jnb.za.seacomnet.com (105.16.29.10) 374.457 ms 374.434 ms 374.381 ms
10 105.22.40.218 (105.22.40.218) 374.362 ms 374.340 ms 374.320 ms
11 zero-three.ah.africa (102.211.207.11) 374.357 ms 374.334 ms 374.312 ms
12 102-214-x-x.zadns.co.za (102.214.x.x) 374.280 ms 374.254 ms 389.962 ms
```
HiNetworking isnt my forte but can anyone give me some advice
Connection to my VM hosted on Absolute Hosting
Code:Through my Lightstruck Fibre - Cannot connect ``` traceroute to 102.214.x.x (102.214.x.x), 30 hops max, 60 byte packets 1 _gateway (192.168.x.x) 3.717 ms 3.607 ms 3.578 ms 2 192.168.x.x (192.168.x.x) 3.755 ms 3.725 ms 3.698 ms 3 3.124.216.102.interworks.co.za (102.216.124.3) 26.249 ms 27.711 ms 27.690 ms 4 21.124.216.102.interworks.co.za (102.216.124.21) 27.716 ms 27.694 ms 27.672 ms 5 b-db1-2.interworks.co.za (160.19.112.137) 27.612 ms 27.590 ms 27.571 ms 6 142.112.19.160.interworks.co.za (160.19.112.142) 34.576 ms 30.500 ms 30.729 ms 7 napafricajhb.liquidtelecom.net (196.60.8.215) 32.561 ms 33.616 ms 33.548 ms 8 77.246.58.98.liquidtelecom.net (77.246.58.98) 33.493 ms 24.417 ms 53.548 ms 9 be-20.lza-pe2-jhb.liquidtelecom.net (41.60.135.93) 69.522 ms 69.755 ms 69.447 ms 10 41.175.247.151 (41.175.247.151) 56.006 ms 55.975 ms 55.938 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ``` Through a VM at Teraco - Can connect, no issues ``` traceroute to 102.214.x.x (102.214.x.x), 30 hops max, 60 byte packets 1 _gateway (192.168.x.x) 0.240 ms 0.194 ms 0.190 ms 2 zatjnb01-br04.syrex.co.za (41.79.22.37) 0.404 ms 0.379 ms 0.360 ms 3 198.19.37.157 (198.19.37.157) 0.649 ms 0.576 ms 0.673 ms 4 jinx.liquid.tech (196.60.96.55) 1.692 ms 1.805 ms 1.917 ms 5 be-20.lza-pe2-jhb.liquidtelecom.net (41.60.135.93) 1.124 ms 1.308 ms 1.120 ms 6 41.175.247.151 (41.175.247.151) 1.096 ms 1.160 ms 1.123 ms 7 zero-three.ah.africa (102.211.207.11) 1.158 ms 1.208 ms 1.173 ms 8 102-214-x-x.zadns.co.za (102.214.x.x) 1.346 ms 1.347 ms 1.403 ms ``` Through MTN Data - Can connect, no issues ``` traceroute to 102.214.x.x (102.214.x.x), 30 hops max, 60 byte packets 1 _gateway (10.x.x.x) 7.825 ms 7.701 ms 7.664 ms 2 172.16.x.x (172.16.x.x) 614.626 ms 614.597 ms 614.581 ms 3 10.x.x.x (10.x.x.x) 616.098 ms 10.x.x.x (10.x.x.x) 615.811 ms 10.x.x.x (10.x.x.x) 615.805 ms 4 10.x.x.x (10.x.x.x) 618.295 ms 618.273 ms 10.x.x.x (10.x.x.x) 615.394 ms 5 be21551.ng-p-01.za.mtnns.net (196.4.90.155) 633.918 ms 638.325 ms 638.919 ms 6 196-10-141-66.ixp.durban (196.10.141.66) 641.869 ms 633.073 ms 632.998 ms 7 xe-0-1-1.er-01-dur.za.seacomnet.com (105.16.10.205) 644.943 ms 252.877 ms 252.782 ms 8 105.25.162.117 (105.25.162.117) 252.739 ms 374.560 ms 374.495 ms 9 ce-1-0-2.er-02-jnb.za.seacomnet.com (105.16.29.10) 374.457 ms 374.434 ms 374.381 ms 10 105.22.40.218 (105.22.40.218) 374.362 ms 374.340 ms 374.320 ms 11 zero-three.ah.africa (102.211.207.11) 374.357 ms 374.334 ms 374.312 ms 12 102-214-x-x.zadns.co.za (102.214.x.x) 374.280 ms 374.254 ms 389.962 ms ```
Considering that its only my home fibre thats affected, this is something my ISP needs to fix
But could this also be an issue from AHs side?
Edit: Thank you to Jade for the excellent customer support, he found the issue and I've logged a ticket with my ISP
Networking isnt my forte but can anyone give me some advice
Connection to my VM hosted on Absolute Hosting
Code:Through my Lightstruck Fibre - Cannot connect ``` traceroute to 102.214.x.x (102.214.x.x), 30 hops max, 60 byte packets 1 _gateway (192.168.x.x) 3.717 ms 3.607 ms 3.578 ms 2 192.168.x.x (192.168.x.x) 3.755 ms 3.725 ms 3.698 ms 3 3.124.216.102.interworks.co.za (102.216.124.3) 26.249 ms 27.711 ms 27.690 ms 4 21.124.216.102.interworks.co.za (102.216.124.21) 27.716 ms 27.694 ms 27.672 ms 5 b-db1-2.interworks.co.za (160.19.112.137) 27.612 ms 27.590 ms 27.571 ms 6 142.112.19.160.interworks.co.za (160.19.112.142) 34.576 ms 30.500 ms 30.729 ms 7 napafricajhb.liquidtelecom.net (196.60.8.215) 32.561 ms 33.616 ms 33.548 ms 8 77.246.58.98.liquidtelecom.net (77.246.58.98) 33.493 ms 24.417 ms 53.548 ms 9 be-20.lza-pe2-jhb.liquidtelecom.net (41.60.135.93) 69.522 ms 69.755 ms 69.447 ms 10 41.175.247.151 (41.175.247.151) 56.006 ms 55.975 ms 55.938 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ``` Through a VM at Teraco - Can connect, no issues ``` traceroute to 102.214.x.x (102.214.x.x), 30 hops max, 60 byte packets 1 _gateway (192.168.x.x) 0.240 ms 0.194 ms 0.190 ms 2 zatjnb01-br04.syrex.co.za (41.79.22.37) 0.404 ms 0.379 ms 0.360 ms 3 198.19.37.157 (198.19.37.157) 0.649 ms 0.576 ms 0.673 ms 4 jinx.liquid.tech (196.60.96.55) 1.692 ms 1.805 ms 1.917 ms 5 be-20.lza-pe2-jhb.liquidtelecom.net (41.60.135.93) 1.124 ms 1.308 ms 1.120 ms 6 41.175.247.151 (41.175.247.151) 1.096 ms 1.160 ms 1.123 ms 7 zero-three.ah.africa (102.211.207.11) 1.158 ms 1.208 ms 1.173 ms 8 102-214-x-x.zadns.co.za (102.214.x.x) 1.346 ms 1.347 ms 1.403 ms ``` Through MTN Data - Can connect, no issues ``` traceroute to 102.214.x.x (102.214.x.x), 30 hops max, 60 byte packets 1 _gateway (10.x.x.x) 7.825 ms 7.701 ms 7.664 ms 2 172.16.x.x (172.16.x.x) 614.626 ms 614.597 ms 614.581 ms 3 10.x.x.x (10.x.x.x) 616.098 ms 10.x.x.x (10.x.x.x) 615.811 ms 10.x.x.x (10.x.x.x) 615.805 ms 4 10.x.x.x (10.x.x.x) 618.295 ms 618.273 ms 10.x.x.x (10.x.x.x) 615.394 ms 5 be21551.ng-p-01.za.mtnns.net (196.4.90.155) 633.918 ms 638.325 ms 638.919 ms 6 196-10-141-66.ixp.durban (196.10.141.66) 641.869 ms 633.073 ms 632.998 ms 7 xe-0-1-1.er-01-dur.za.seacomnet.com (105.16.10.205) 644.943 ms 252.877 ms 252.782 ms 8 105.25.162.117 (105.25.162.117) 252.739 ms 374.560 ms 374.495 ms 9 ce-1-0-2.er-02-jnb.za.seacomnet.com (105.16.29.10) 374.457 ms 374.434 ms 374.381 ms 10 105.22.40.218 (105.22.40.218) 374.362 ms 374.340 ms 374.320 ms 11 zero-three.ah.africa (102.211.207.11) 374.357 ms 374.334 ms 374.312 ms 12 102-214-x-x.zadns.co.za (102.214.x.x) 374.280 ms 374.254 ms 389.962 ms ```
Considering that its only my home fibre thats affected, this is something my ISP needs to fix
But could this also be an issue from AHs side?
|
The next hop is into into our network which is where @Waaiez is being blocked.
This ip belongs to Liquid, so they are the peeps blocking connection from routing further into AH network
41.175.247.151
Is this at a DC level where its being blocked, could be some routing issue via the XCThe next hop is into into our network which is where @Waaiez is being blocked.
I have provided him with some additional information that he can forward to his FTTH provider to hopefully get the issue permanently resolved.
Yeah he is being blocked at a DC level, ie on the first hop into our network.Is this at a DC level where its being blocked, could be some routing issue via the XC
9 be-20.lza-pe2-jhb.liquidtelecom.net (41.60.135.93) 69.522 ms 69.755 ms 69.447 ms
10 41.175.247.151 (41.175.247.151) 56.006 ms 55.975 ms 55.938 ms
5 be-20.lza-pe2-jhb.liquidtelecom.net (41.60.135.93) 1.124 ms 1.308 ms 1.120 ms
6 41.175.247.151 (41.175.247.151) 1.096 ms 1.160 ms 1.123 ms