Afrihost - Pure Fibre Feedback Thread Part 2

MakoPC said:
Getting less than 50 download on Playstation on a gigabit line
Click to expand...
Hi

I have followed up with MFN on the NLD fault.

At this stage, the issue is still being worked on, and MFN has not been able to provide an estimated time of resolution. As a result, you may continue to experience latency or intermittent service interruptions until the fault has been resolved. We apologise for the inconvenience caused during this period.
 
Hi @Afrigirl,

I have just completed the live target traceroutes using Net Analyzer on my iPhone 13 Pro directly to the official AWS matchmaking servers. The data confirms an absolute routing disaster for the Middle East path.

As you can see below, my traffic to Bahrain is being heavily misrouted through France and then into London before it even attempts to reach the Middle East:

Traceroute to Middle East (Bahrain AWS - 15.185.0.1):

  • Hop 1: 192.168.0.1 (Local Router)
  • Hop 2: 41.170.75.1 (Afrihost Gateway)
  • Hop 3: 165.73.14.17 (165-73-14-17.ip.ahisp.co.za)
  • Hop 4: 100.127.6.58 (Core Internal)
  • Hop 5: 100.127.6.59 (Core Internal)
  • Hop 6: 41.175.242.116 (Core Transit)
  • Hop 7 (JHB): 41.175.222.250 (hu-0-5-0-9.Iza-p4-jhb.liquidtelecom.net) - 42.8 ms
  • Hop 8 (Marseille): 5.11.12.113 (hu-0-o-0-1.Ifr-p1-mrs.liquidtelecom.com) - 268.9 ms (Massive 226ms Loop Spike)
  • Hop 9 (Marseille): 5.11.14.135 (hu-0-0-0-15.Ifr-p2-mrs.liquidtelecom.net) - 235.2 ms
  • Hop 10 (Marseille): 195.219.186.182 (ix-hge-0-0-0-30.ecore1.emrs2-marseille.as6453.net)
  • Hop 11 (Marseille): 80.231.165.48 (if-bundle-33-2.qcore1.emrs2-marseille.as6453.net)
  • Hop 12 (Marseille): 195.219.174.129 (if-be-21-2.ecore4.emrs2-marseille.as6453.net)
  • Hop 13 (London): 195.219.186.169 (if-bundle-35-2.qcore5.Idn-london.as6453.net) - 212.2 ms
  • Hop 14 (London): 195.219.16.136 (if-bundle-51-2.qcore2.Idn-london.as6453.net)
  • Hop 15 (London): 195.219.16.129 (if-ae-67-2.tcore2.Idn-london.as6453.net)
Traceroute to Europe (Frankfurt AWS - 3.120.0.1):

  • Hop 1: 192.168.0.1 - 30.4 ms
  • Hop 2: 41.170.75.1 - 107.0 ms
  • Hop 3: 165.73.14.41 (165-73-14-41.ip.ahisp.co.za) - 27.5 ms
  • Hop 4: 100.127.6.58 - 64.0 ms
  • Hop 5: 100.127.6.59 - 58.2 ms
The Middle East data explicitly proves that the BGP routing policy override for account B620000052 is completely inactive or broken on Liquid Telecom's upstream side.

Please push this directly to the senior network engineers at the NOC. They need to manually apply a BGP communities flag to force my prefix out over the East Coast undersea cables (Seacom/EASSy) instead of leaking onto the West Coast transit path.

Thank you!
 

Attachments

  • IMG_2683.jpeg
    IMG_2683.jpeg
    184.9 KB · Views: 13
  • IMG_2684.jpeg
    IMG_2684.jpeg
    166.9 KB · Views: 12
  • IMG_2685.jpeg
    IMG_2685.jpeg
    117.9 KB · Views: 11
Joslyn_ said:
Hi @Afrigirl,

I have just completed the live target traceroutes using Net Analyzer on my iPhone 13 Pro directly to the official AWS matchmaking servers. The data confirms an absolute routing disaster for the Middle East path.

As you can see below, my traffic to Bahrain is being heavily misrouted through France and then into London before it even attempts to reach the Middle East:

Traceroute to Middle East (Bahrain AWS - 15.185.0.1):

  • Hop 1: 192.168.0.1 (Local Router)
  • Hop 2: 41.170.75.1 (Afrihost Gateway)
  • Hop 3: 165.73.14.17 (165-73-14-17.ip.ahisp.co.za)
  • Hop 4: 100.127.6.58 (Core Internal)
  • Hop 5: 100.127.6.59 (Core Internal)
  • Hop 6: 41.175.242.116 (Core Transit)
  • Hop 7 (JHB): 41.175.222.250 (hu-0-5-0-9.Iza-p4-jhb.liquidtelecom.net) - 42.8 ms
  • Hop 8 (Marseille): 5.11.12.113 (hu-0-o-0-1.Ifr-p1-mrs.liquidtelecom.com) - 268.9 ms (Massive 226ms Loop Spike)
  • Hop 9 (Marseille): 5.11.14.135 (hu-0-0-0-15.Ifr-p2-mrs.liquidtelecom.net) - 235.2 ms
  • Hop 10 (Marseille): 195.219.186.182 (ix-hge-0-0-0-30.ecore1.emrs2-marseille.as6453.net)
  • Hop 11 (Marseille): 80.231.165.48 (if-bundle-33-2.qcore1.emrs2-marseille.as6453.net)
  • Hop 12 (Marseille): 195.219.174.129 (if-be-21-2.ecore4.emrs2-marseille.as6453.net)
  • Hop 13 (London): 195.219.186.169 (if-bundle-35-2.qcore5.Idn-london.as6453.net) - 212.2 ms
  • Hop 14 (London): 195.219.16.136 (if-bundle-51-2.qcore2.Idn-london.as6453.net)
  • Hop 15 (London): 195.219.16.129 (if-ae-67-2.tcore2.Idn-london.as6453.net)
Traceroute to Europe (Frankfurt AWS - 3.120.0.1):

  • Hop 1: 192.168.0.1 - 30.4 ms
  • Hop 2: 41.170.75.1 - 107.0 ms
  • Hop 3: 165.73.14.41 (165-73-14-41.ip.ahisp.co.za) - 27.5 ms
  • Hop 4: 100.127.6.58 - 64.0 ms
  • Hop 5: 100.127.6.59 - 58.2 ms
The Middle East data explicitly proves that the BGP routing policy override for account B620000052 is completely inactive or broken on Liquid Telecom's upstream side.

Please push this directly to the senior network engineers at the NOC. They need to manually apply a BGP communities flag to force my prefix out over the East Coast undersea cables (Seacom/EASSy) instead of leaking onto the West Coast transit path.

Thank you!
Click to expand...

That is not how it works. Liquid only has capacity to Fujairah and even then it needs transit to reach AWS Bahrain. AWS is not announcing that prefix at NAP so they don't have their own route to that destination which means the route your traffic follows is the best route available.
 
Thank you to the network team for the clear explanation regarding Liquid's network termination in Fujairah and the lack of an AWS prefix announcement at NAP Africa. That completely explains the routing behavior.
Since Liquid does not have a direct peering or transit path to AWS Bahrain via the East Coast, my traffic is defaulting to the long West Coast/Europe transit path, making the Middle East region unplayable for competitive gaming.
Does Afrihost utilize any alternative upstream transit providers or alternative routing blends (such as via Seacom or intermediate transit partners in Europe) that can cleanly route to the Middle East without dropping the packets all the way into London first? If not, is there any timeline on AWS prefix optimization or peering adjustments for SA gamers trying to target the Bahrain AWS cloud?
Thank you again for the transparency!
 
Joslyn_ said:
Thank you to the network team for the clear explanation regarding Liquid's network termination in Fujairah and the lack of an AWS prefix announcement at NAP Africa. That completely explains the routing behavior.
Since Liquid does not have a direct peering or transit path to AWS Bahrain via the East Coast, my traffic is defaulting to the long West Coast/Europe transit path, making the Middle East region unplayable for competitive gaming.
Does Afrihost utilize any alternative upstream transit providers or alternative routing blends (such as via Seacom or intermediate transit partners in Europe) that can cleanly route to the Middle East without dropping the packets all the way into London first? If not, is there any timeline on AWS prefix optimization or peering adjustments for SA gamers trying to target the Bahrain AWS cloud?
Thank you again for the transparency!
Click to expand...
cavedog said:
That is not how it works. Liquid only has capacity to Fujairah and even then it needs transit to reach AWS Bahrain. AWS is not announcing that prefix at NAP so they don't have their own route to that destination which means the route your traffic follows is the best route available.
Click to expand...
@cavedog thank you for the reply. @Joslyn_ Cavedog is one of our NOC Engineers.
 
Something weird is going on with the Afrihost (Android) app.

All the Openserve fibre products are indicated as 500/250 Mbps.

491b68b1b2a511bbe13fe1a45a911d80.jpg


@Afrigirl If it helps, this is on version 3.4.23 which is the latest available Android version, published on the 13th of July.
 
Last edited:
When will the 1 Gbps option be available for us on Openserve?

Or are wanting to push loyal customers away from Afrihost to other ISP's?
 
Apogee said:
Something weird is going on with the Afrihost (Android) app.

All the Openserve fibre products are indicated as 500/250 Mbps.

491b68b1b2a511bbe13fe1a45a911d80.jpg


@Afrigirl If it helps, this is on version 3.4.23 which is the latest available Android version, published on the 13th of July.
Click to expand...
Hi. I will check with Dev.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X