Frogfoot Port Elizabeth

Interesting watching the congestion on my node during lock down
Screenshot 2020-04-23 at 14.37.44.png
Speedtest-cli to Vodacom CT server , I also test rocketnet JHB which looks the same
 
joshsparkie said:
@AfriFella @AfriMan any reason why everyone else on Frogfoot in PE are being routed through Cape Town but I am still being routed via Joburg?

View attachment 809833

As above my pings to 1.1.1.1 and 1.0.0.1 are clearly routed to Joburg instead of CPT hence the +-27ms ping average, here's a traceroute to prove CPT traffic being routed via Joburg too (when 196.41.143.37 and 1.1.1.1 used to be +-11ms):
traceroute to 196.41.143.37 (196.41.143.37), 30 hops max, 60 byte packets
1 192.168.2.1 (192.168.2.1) 0.342 ms 0.357 ms 0.362 ms
2 102-182-159-1.ip.afrihost.joburg (102.182.159.1) 27.743 ms 27.679 ms 27.635 ms
3 169-1-21-91.ip.afrihost.co.za (169.1.21.91) 28.247 ms 28.175 ms 28.152 ms
4 optinet.ixp.joburg (196.60.8.120) 28.507 ms mweb.ixp.joburg (196.60.8.145) 28.510 ms 28.461 ms
5 197-80-4-96.jhb.mweb.co.za (197.80.4.96) 46.335 ms 197-80-4-23.jhb.mweb.co.za (197.80.4.23) 47.926 ms 197-80-5-64.jhb.mweb.co.za (197.80.5.64) 48.169 ms
6 bu-ether1.vic-pe-2.optinet.net (197.80.4.8) 46.344 ms 197-80-5-61.jhb.mweb.co.za (197.80.5.61) 50.578 ms bu-ether1.vic-pe-2.optinet.net (197.80.4.8) 49.377 ms
7 tengig0-0-0-3.vic-p-2.mweb.co.za (197.80.7.2) 91.913 ms bu-ether2.mca-pe-1.optinet.net (197.80.4.225) 44.746 ms tengig0-0-0-3.vic-p-2.mweb.co.za (197.80.7.2) 58.480 ms
8 te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 47.019 ms 46.966 ms 197-80-5-59.jhb.mweb.co.za (197.80.5.59) 45.825 ms
9 tengig0-0-0-3.vic-p-2.mweb.co.za (197.80.7.2) 46.870 ms te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 46.642 ms 197-84-7-58.cpt.mweb.co.za (197.84.7.58) 45.120 ms
10 197-84-7-58.cpt.mweb.co.za (197.84.7.58) 45.124 ms 197-84-247-89.cpt.mweb.co.za (197.84.247.89) 46.379 ms 47.187 ms
11 196.41.143.37 (196.41.143.37) 45.031 ms 101.te0-0-0-0.cpt-pe-1.optinet.net (197.84.7.21) 46.265 ms 46.078 ms

@Frogfoot Fibre am I correct in saying that this is a routing issue on Afrihost's side?
Click to expand...

Is this still happening? Did you get any feedback from AH or FF?

It seems like I am in exactly the same boat.
 
russellO said:
Is this still happening? Did you get any feedback from AH or FF?

It seems like I am in exactly the same boat.
Click to expand...

Yeah still happening to me, the last update I got from AH was on 6 April and was:
Here's your update:

I trust you are well.

Thank you for your valued email. This is correct, Frogfoot has diverted traffic from Port Elizabeth going to the Capetown ENNI to the Johannesburg ENNI as the link between Capetown and PE is almost at full capacity and traffic for PE has thus been rerouted to JHB to allow Frogfoot to upgrade the Capetown Link.

If you have any questions or concerns please let us know.

Kind regards

Afrihost Fibre Ops
Click to expand...

FF also confirmed I was being routed through the Jo'burg ENNI.

Spoke to AH Whatsapp support yesterday and they said they have no updates for me. Haven't seen anything on FF's website regarding the upgrade of the PE-CPT link.
 
I saw some maintenance on FF website last week for the CT-PE NLD (National Long Distance - I think) links, also PE-DBN
 
Yes, up the pole.

Line went down for a few minutes around 20:20.

FF (Vox) Fernglen.
 
Crawling on FF in Fernglen this morning. 1.5mbps on a 100 line.

Anyone else ?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X