Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Undersea cables cut near Jeddah (Saudi), connectivity to/from Europe-MiddleEast-SouthAsia affected

sh97sh97 Member, Host Rep
edited September 2025 in Outages

The cable failures occurred near Jeddah, Saudi Arabia, and affected major systems, such as the South East Asia–Middle East–Western Europe 4 (SMW4) and the India-Middle East-Western Europe (IMEWE) cables. These cables are critical arteries for internet traffic connecting Europe, the Middle East, and Asia.

The South East Asia–Middle East–Western Europe 4 cable is run by Tata Communications, part of the Indian conglomerate. The India-Middle East-Western Europe cable is run by another consortium overseen by Alcatel-Lucent.

Some links here:

https://timesofindia.indiatimes.com/business/international-business/undersea-cables-cut-in-red-sea-internet-disrupted-across-asia-middle-east-india-pakistan-among-affected/articleshow/123744508.cms

https://www.businesstoday.in/world/story/internet-disrupted-across-mideast-south-asia-after-subsea-cable-cuts-near-jeddah-492917-2025-09-07

https://gulfnews.com/technology/uae-internet-users-report-slowdowns-after-red-sea-cable-cuts-1.500259922


Personally, can confirm increased latency and packet loss to Europe from my probe in UAE.


Comments

  • OhJohnOhJohn Member
    edited September 2025

    Yes, no fun.

    But to distinct the good from the bad:

    @leapswitch immediately informed me by mail.

    @ovh (Mumbai DC, Singapore, etc.) just sucks atm, esp. Mumbai (which btw always sucks networkwise, but now it sucks even more)

    Host Universal (used by @ShockHosting) now uses PCCW for Asia<->Europe which - in comparison to e.g. any TATA line - is really stable atm while TATA is at ~ 25% packet loss and high latency.

  • That's why my internet speed has reduced quite significantly. Southeast Asia.

  • NeoonNeoon Community Contributor, Veteran

    Takes kinda a detour but rerouting works fine.

  • DediRockDediRock Member, Patron Provider

    Well hopefully it gets fixed soon, and not a deliberate attack. That is wild though, never thought of anchors being a possible reason they get cut or damaged.

  • ovh france servers latency increased from 120ms from my place in india to 450ms traffic routing through singapore

  • @diwakerd if latency is important for you:

    Europe to Singapore Shockhosting is about 180ms atm via Host Universal via PCCW. OVH Europe to OVH Singapore 250ms to 350ms meanwhile (using TATA) ....

    @Neoon would sure find a better route even.

    But this still might be an idea to use a tiny proxy in Europe and one in Singapore to re-route traffic.

    Thanked by 2sh97 ShockHosting
  • @OhJohn said:
    @diwakerd if latency is important for you:

    Europe to Singapore Shockhosting is about 180ms atm via Host Universal via PCCW. OVH Europe to OVH Singapore 250ms to 350ms meanwhile (using TATA) ....

    @Neoon would sure find a better route even.

    But this still might be an idea to use a tiny proxy in Europe and one in Singapore to re-route traffic.

    Singapore to Marseille is roughly 135ms via GSL, can't get any better than that. (or that's what I think ;) )

  • SaahibSaahib Host Rep, Veteran

    Interestingly when this happened, was not able to find any news about this, I thought something wrong with services I use.

  • borkedasciiborkedascii Member
    edited September 2025

    @OhJohn said:
    @diwakerd if latency is important for you:

    Europe to Singapore Shockhosting is about 180ms atm via Host Universal via PCCW. OVH Europe to OVH Singapore 250ms to 350ms meanwhile (using TATA) ....

    @Neoon would sure find a better route even.

    But this still might be an idea to use a tiny proxy in Europe and one in Singapore to re-route traffic.

    How did you get 250-350 on OVH SG? Marseille to Singapore is mostly unaffected if the express routes (AAE-1 and Sea-ME-WE 5) are being used to bypass the hop at Middle East or India.

    Start: 2025-09-07T13:05:36+0000
    HOST: lil1.lg.ovh.net                                     Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS16276  vss-9a-6k.fr.eu (5.135.137.253)              0.0%     3    0.5   0.6   0.5   0.6   0.0
      2. AS???    10.17.81.26                                  0.0%     3    0.7   0.6   0.6   0.7   0.1
      3. AS???    10.73.16.110                                 0.0%     3    0.4   0.3   0.3   0.4   0.0
      4. AS???    172.20.8.0                                   0.0%     3    2.7   2.5   1.6   3.0   0.7
      5. AS16276  37.59.16.13                                  0.0%     3    1.7   1.3   1.1   1.7   0.3
      6. AS16276  par-th2-sbb1-nc5.fr.eu (54.36.50.226)        0.0%     3    4.6   4.6   4.5   4.6   0.1
      7. AS16276  par-dpa1-sbb1-8k.fr.eu (57.128.121.10)       0.0%     3    6.8   7.0   6.7   7.5   0.4
      8. AS16276  mrs-mrs2-sbb1-nc5.fr.eu (57.128.121.185)     0.0%     3   15.0  15.1  15.0  15.1   0.1
      9. AS16276  sin-gss1-sbb1-8k.sgp.asia (91.121.131.211)  33.3%     3  152.6 152.0 151.3 152.6   0.9
     10. AS16276  sin-sgcs2-g2-nc5.sgp.asia (103.5.15.17)      0.0%     3  147.9 147.9 147.9 147.9   0.0
     11. AS???    10.75.248.17                                 0.0%     3  147.4 147.5 147.4 147.6   0.1
     12. AS???    10.75.0.93                                   0.0%     3  147.7 147.8 147.7 147.9   0.1
     13. AS???    10.133.65.57                                 0.0%     3  147.6 147.6 147.6 147.6   0.0
     14. AS???    10.29.135.103                                0.0%     3  147.7 147.7 147.6 147.7   0.1
     15. AS???    10.29.193.137                                0.0%     3  147.7 147.6 147.6 147.7   0.0
     16. AS???    10.29.219.202                                0.0%     3  147.6 147.6 147.6 147.7   0.1
     17. AS???    192.168.140.183                              0.0%     3  147.7 147.7 147.7 147.8   0.1
     18. AS16276  sgp.lg.ovh.net (51.79.140.79)                0.0%     3  147.9 147.9 147.8 147.9   0.1
    
  • It seems to only affect routing over TATA and not other T1 providers.

    If your provider has more upstreams than just TATA, you can ask them to reroute to those instead.

  • NeoonNeoon Community Contributor, Veteran

    @zGato said:

    @OhJohn said:
    @diwakerd if latency is important for you:

    Europe to Singapore Shockhosting is about 180ms atm via Host Universal via PCCW. OVH Europe to OVH Singapore 250ms to 350ms meanwhile (using TATA) ....

    @Neoon would sure find a better route even.

    But this still might be an idea to use a tiny proxy in Europe and one in Singapore to re-route traffic.

    Singapore to Marseille is roughly 135ms via GSL, can't get any better than that. (or that's what I think ;) )

    Indeed, pretty nice.

      2.|-- unn-84-17-33-202.cdn77.co  0.0%     5    0.3   0.7   0.3   1.4   0.5
      3.|-- ???                       100.0     5    0.0   0.0   0.0   0.0   0.0
      4.|-- 149.11.241.130             0.0%     5    0.3   0.3   0.3   0.4   0.1
      5.|-- po9.sg-eqxsg3-bb2.globals  0.0%     5  132.9 133.0 132.9 133.1   0.1
      6.|-- po6.sg-eqxsg3-cr7.globals  0.0%     5  133.2 133.2 133.1 133.2   0.1
      7.|-- e53.sg-eqxsg3-cr3.globals  0.0%     5  132.8 133.0 132.8 133.3   0.2
      8.|-- 149020.globalsecurelayer.  0.0%     5  134.2 134.2 134.1 134.2   0.1
    
    Thanked by 1borkedascii
  • sh97sh97 Member, Host Rep

    @OhJohn said: Host Universal (used by @ShockHosting) now uses PCCW for Asia<->Europe

    Interesting, for me it is routed via America lol.

    HOST: sgp2-layer-7950X                              Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS136557 core.rc.sgp.sg.hostuniversal.com.au    0.0%    10    0.2   0.3   0.2   0.3   0.0
      2. AS136557 cr1.rc.sgp.sg.hostuniversal.com.au     0.0%    10    0.2   0.3   0.2   0.3   0.0
      3. AS136557 cr1.sg3.sgp.sg.hostuniversal.com.au    0.0%    10    0.5   0.5   0.5   0.6   0.0
      4. AS???    unn-45-134-214-214.cdn77.com           0.0%    10    0.5   0.5   0.5   0.6   0.0
      5. AS2914   ae-95.a03.sngpsi07.sg.bb.gin.ntt.net   0.0%    10    0.6   0.6   0.6   0.7   0.0
      6. AS2914   ae-3.r24.sngpsi07.sg.bb.gin.ntt.net   10.0%    10    0.6   0.6   0.5   0.6   0.0
      7. AS2914   ae-4.r27.osakjp02.jp.bb.gin.ntt.net   70.0%    10   80.5  78.3  77.0  80.5   2.0
      8. AS2914   ae-0.r26.osakjp02.jp.bb.gin.ntt.net   20.0%    10   69.5  71.5  69.5  77.0   2.8
      9. AS2914   ae-4.r26.snjsca04.us.bb.gin.ntt.net    0.0%    10  171.8 171.9 171.8 172.1   0.1
     10. AS2914   ae-8.a04.snjsca04.us.bb.gin.ntt.net    0.0%    10  175.3 175.3 175.2 175.4   0.1
     11. AS1299   sjo-b23-link.ip.twelve99.net           0.0%    10  173.6 173.1 172.4 174.0   0.6
     12. AS1299   palo-bb2-link.ip.twelve99.net          0.0%    10  175.4 175.1 174.1 175.8   0.6
     13. AS1299   den-bb2-link.ip.twelve99.net           0.0%    10  197.7 197.8 197.7 198.1   0.1
     14. AS1299   kanc-bb2-link.ip.twelve99.net          0.0%    10  229.5 229.1 228.1 229.7   0.6
     15. AS1299   chi-bb2-link.ip.twelve99.net           0.0%    10  235.9 237.0 235.9 238.0   1.0
     16. AS1299   ewr-bb2-link.ip.twelve99.net          90.0%    10  507.3 507.3 507.3 507.3   0.0
     17. AS1299   ldn-bb2-link.ip.twelve99.net           0.0%    10  229.8 230.7 229.7 232.1   1.0
     18. AS1299   prs-bb2-link.ip.twelve99.net          10.0%    10  229.7 229.2 228.3 229.8   0.6
     19. AS1299   prs-b3-link.ip.twelve99.net           10.0%    10  229.8 229.3 228.2 229.8   0.5
     20. AS34309  80.95.153.138                          0.0%    10  236.1 235.8 235.1 236.5   0.6
     21. AS29066  92.204.249.109                         0.0%    10  236.9 236.9 236.6 237.9   0.4
     22. AS29066  lg-fr.racknerd.com                     0.0%    10  234.8 235.2 234.7 236.2   0.6
    
  • sh97sh97 Member, Host Rep

    @gremeyer said:
    It seems to only affect routing over TATA and not other T1 providers.

    If your provider has more upstreams than just TATA, you can ask them to reroute to those instead.

    TATA seems to be fine? Not sure.
    Below is from Leaseweb SG.

    HOST: SG04-GC                                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS59253  167.253.158.3                                      0.0%    10    0.3   0.3   0.2   0.4   0.0
      2. AS59253  be-2.br02.sin-01.sg.leaseweb.net                   0.0%    10    0.6   0.6   0.6   0.8   0.1
      3. AS59253  ae-1002.br01.sin-10.sg.leaseweb.net                0.0%    10    0.8   1.0   0.8   2.3   0.5
      4. AS4637   unknown.telstraglobal.net                          0.0%    10    1.8   2.1   1.5   3.8   0.9
      5. AS6453   ix-be-8.ecore4.esin4-singapore.as6453.net         10.0%    10    1.1  13.1   1.1  53.4  22.3
      6. AS6453   if-be-18-2.ecore2.esin4-singapore.as6453.net      90.0%    10  151.6 151.6 151.6 151.6   0.0
      7. AS???    ???                                               100.0    10    0.0   0.0   0.0   0.0   0.0
      8. AS???    ???                                               100.0    10    0.0   0.0   0.0   0.0   0.0
      9. AS6453   if-bundle-2-2.qcore2.emrs2-marseille.as6453.net   90.0%    10  156.1 156.1 156.1 156.1   0.0
     10. AS6453   if-bundle-14-2.qcore2.fnm-frankfurt.as6453.net    90.0%    10  157.6 157.6 157.6 157.6   0.0
     11. AS6453   if-ae-55-2.tcore2.fnm-frankfurt.as6453.net         0.0%    10  156.5 156.8 156.4 158.0   0.5
     12. AS6453   if-ae-35-10.tcore1.fr0-frankfurt.as6453.net        0.0%    10  157.1 157.8 157.0 160.0   1.0
     13. AS6453   if-bundle-35-2.qcore1.fr0-frankfurt.as6453.net    90.0%    10  157.3 157.3 157.3 157.3   0.0
     14. AS6453   195.219.223.22                                     0.0%    10  157.8 157.7 157.6 157.9   0.1
     15. AS34309  80.95.144.185                                      0.0%    10  163.7 163.9 163.7 164.1   0.1
     16. AS34309  80.95.153.134                                      0.0%    10  163.8 163.8 163.8 163.9   0.1
     17. AS29066  po250.ds1-right.2b.strasbourg.fr.velia.net         0.0%    10  167.4 168.0 167.2 169.4   0.7
     18. AS29066  lg-fr.racknerd.com                                 0.0%    10  163.8 163.8 163.7 163.9   0.0
    
    Thanked by 1borkedascii
  • OhJohnOhJohn Member
    edited September 2025

    @borkedascii said: How did you get 250-350 on OVH SG?

    Had this yesterday, it got better again. OVH GRA<->OVH SGP is now 150ms while e.g. OVH GRA<->Shockhosting SGP is now at 160ms.

    But OVH GRA<->OVH BOM is still at >210ms as they re-route via SGP atm but much better as yesterday also. So they finally shuffled around their backbones at bit.

    As @sh97 observed, even TATA seems to work again somewhat. But yesterday was not nice*.

    (*still better than DTAG<->CF free tier)

    Thanked by 2ShockHosting sh97
  • trewqtrewq Administrator, Patron Provider
    edited September 2025

    @sh97 said:

    @OhJohn said: Host Universal (used by @ShockHosting) now uses PCCW for Asia<->Europe

    Interesting, for me it is routed via America lol.

    HOST: sgp2-layer-7950X                              Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS136557 core.rc.sgp.sg.hostuniversal.com.au    0.0%    10    0.2   0.3   0.2   0.3   0.0
      2. AS136557 cr1.rc.sgp.sg.hostuniversal.com.au     0.0%    10    0.2   0.3   0.2   0.3   0.0
      3. AS136557 cr1.sg3.sgp.sg.hostuniversal.com.au    0.0%    10    0.5   0.5   0.5   0.6   0.0
      4. AS???    unn-45-134-214-214.cdn77.com           0.0%    10    0.5   0.5   0.5   0.6   0.0
      5. AS2914   ae-95.a03.sngpsi07.sg.bb.gin.ntt.net   0.0%    10    0.6   0.6   0.6   0.7   0.0
      6. AS2914   ae-3.r24.sngpsi07.sg.bb.gin.ntt.net   10.0%    10    0.6   0.6   0.5   0.6   0.0
      7. AS2914   ae-4.r27.osakjp02.jp.bb.gin.ntt.net   70.0%    10   80.5  78.3  77.0  80.5   2.0
      8. AS2914   ae-0.r26.osakjp02.jp.bb.gin.ntt.net   20.0%    10   69.5  71.5  69.5  77.0   2.8
      9. AS2914   ae-4.r26.snjsca04.us.bb.gin.ntt.net    0.0%    10  171.8 171.9 171.8 172.1   0.1
     10. AS2914   ae-8.a04.snjsca04.us.bb.gin.ntt.net    0.0%    10  175.3 175.3 175.2 175.4   0.1
     11. AS1299   sjo-b23-link.ip.twelve99.net           0.0%    10  173.6 173.1 172.4 174.0   0.6
     12. AS1299   palo-bb2-link.ip.twelve99.net          0.0%    10  175.4 175.1 174.1 175.8   0.6
     13. AS1299   den-bb2-link.ip.twelve99.net           0.0%    10  197.7 197.8 197.7 198.1   0.1
     14. AS1299   kanc-bb2-link.ip.twelve99.net          0.0%    10  229.5 229.1 228.1 229.7   0.6
     15. AS1299   chi-bb2-link.ip.twelve99.net           0.0%    10  235.9 237.0 235.9 238.0   1.0
     16. AS1299   ewr-bb2-link.ip.twelve99.net          90.0%    10  507.3 507.3 507.3 507.3   0.0
     17. AS1299   ldn-bb2-link.ip.twelve99.net           0.0%    10  229.8 230.7 229.7 232.1   1.0
     18. AS1299   prs-bb2-link.ip.twelve99.net          10.0%    10  229.7 229.2 228.3 229.8   0.6
     19. AS1299   prs-b3-link.ip.twelve99.net           10.0%    10  229.8 229.3 228.2 229.8   0.5
     20. AS34309  80.95.153.138                          0.0%    10  236.1 235.8 235.1 236.5   0.6
     21. AS29066  92.204.249.109                         0.0%    10  236.9 236.9 236.6 237.9   0.4
     22. AS29066  lg-fr.racknerd.com                     0.0%    10  234.8 235.2 234.7 236.2   0.6
    

    This is just that specific far network due to Telia's shitty peering in APAC and Telia being the only T1 the far network is directly connected to/advertising this prefix over.

    Have pushed it via Cogent, via the far network's T2 upstream. Will monitor.

    Thanked by 2sh97 borkedascii
  • jsgjsg Member, Resident Benchmarker

    FWIW:

    I see significantly higher latency and lower download speed from @HostDZire's Mumbai DC to most of my european targets. Funnily though I also see a few targets with actually better results than usually (ie. before the current fiber problem), e.g. and particularly plusline.net (DE) which has over 100ms lower latency currently as well as about 50% higher DL speed!

    Thanked by 1sh97
  • sh97sh97 Member, Host Rep

    @trewq said:

    @sh97 said:

    @OhJohn said: Host Universal (used by @ShockHosting) now uses PCCW for Asia<->Europe

    Interesting, for me it is routed via America lol.

    HOST: sgp2-layer-7950X                              Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS136557 core.rc.sgp.sg.hostuniversal.com.au    0.0%    10    0.2   0.3   0.2   0.3   0.0
      2. AS136557 cr1.rc.sgp.sg.hostuniversal.com.au     0.0%    10    0.2   0.3   0.2   0.3   0.0
      3. AS136557 cr1.sg3.sgp.sg.hostuniversal.com.au    0.0%    10    0.5   0.5   0.5   0.6   0.0
      4. AS???    unn-45-134-214-214.cdn77.com           0.0%    10    0.5   0.5   0.5   0.6   0.0
      5. AS2914   ae-95.a03.sngpsi07.sg.bb.gin.ntt.net   0.0%    10    0.6   0.6   0.6   0.7   0.0
      6. AS2914   ae-3.r24.sngpsi07.sg.bb.gin.ntt.net   10.0%    10    0.6   0.6   0.5   0.6   0.0
      7. AS2914   ae-4.r27.osakjp02.jp.bb.gin.ntt.net   70.0%    10   80.5  78.3  77.0  80.5   2.0
      8. AS2914   ae-0.r26.osakjp02.jp.bb.gin.ntt.net   20.0%    10   69.5  71.5  69.5  77.0   2.8
      9. AS2914   ae-4.r26.snjsca04.us.bb.gin.ntt.net    0.0%    10  171.8 171.9 171.8 172.1   0.1
     10. AS2914   ae-8.a04.snjsca04.us.bb.gin.ntt.net    0.0%    10  175.3 175.3 175.2 175.4   0.1
     11. AS1299   sjo-b23-link.ip.twelve99.net           0.0%    10  173.6 173.1 172.4 174.0   0.6
     12. AS1299   palo-bb2-link.ip.twelve99.net          0.0%    10  175.4 175.1 174.1 175.8   0.6
     13. AS1299   den-bb2-link.ip.twelve99.net           0.0%    10  197.7 197.8 197.7 198.1   0.1
     14. AS1299   kanc-bb2-link.ip.twelve99.net          0.0%    10  229.5 229.1 228.1 229.7   0.6
     15. AS1299   chi-bb2-link.ip.twelve99.net           0.0%    10  235.9 237.0 235.9 238.0   1.0
     16. AS1299   ewr-bb2-link.ip.twelve99.net          90.0%    10  507.3 507.3 507.3 507.3   0.0
     17. AS1299   ldn-bb2-link.ip.twelve99.net           0.0%    10  229.8 230.7 229.7 232.1   1.0
     18. AS1299   prs-bb2-link.ip.twelve99.net          10.0%    10  229.7 229.2 228.3 229.8   0.6
     19. AS1299   prs-b3-link.ip.twelve99.net           10.0%    10  229.8 229.3 228.2 229.8   0.5
     20. AS34309  80.95.153.138                          0.0%    10  236.1 235.8 235.1 236.5   0.6
     21. AS29066  92.204.249.109                         0.0%    10  236.9 236.9 236.6 237.9   0.4
     22. AS29066  lg-fr.racknerd.com                     0.0%    10  234.8 235.2 234.7 236.2   0.6
    

    This is just that specific far network due to Telia's shitty peering in APAC and Telia being the only T1 the far network is directly connected to/advertising this prefix over.

    Have pushed it via Cogent, via the far network's T2 upstream. Will monitor.

    Can confirm latency dropped to ~155ms.
    Curious - do you have a direct link to Cogent, or is it via CDN77?

    Thanked by 1borkedascii
  • trewqtrewq Administrator, Patron Provider

    @sh97 said:

    @trewq said:

    @sh97 said:

    @OhJohn said: Host Universal (used by @ShockHosting) now uses PCCW for Asia<->Europe

    Interesting, for me it is routed via America lol.

    HOST: sgp2-layer-7950X                              Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS136557 core.rc.sgp.sg.hostuniversal.com.au    0.0%    10    0.2   0.3   0.2   0.3   0.0
      2. AS136557 cr1.rc.sgp.sg.hostuniversal.com.au     0.0%    10    0.2   0.3   0.2   0.3   0.0
      3. AS136557 cr1.sg3.sgp.sg.hostuniversal.com.au    0.0%    10    0.5   0.5   0.5   0.6   0.0
      4. AS???    unn-45-134-214-214.cdn77.com           0.0%    10    0.5   0.5   0.5   0.6   0.0
      5. AS2914   ae-95.a03.sngpsi07.sg.bb.gin.ntt.net   0.0%    10    0.6   0.6   0.6   0.7   0.0
      6. AS2914   ae-3.r24.sngpsi07.sg.bb.gin.ntt.net   10.0%    10    0.6   0.6   0.5   0.6   0.0
      7. AS2914   ae-4.r27.osakjp02.jp.bb.gin.ntt.net   70.0%    10   80.5  78.3  77.0  80.5   2.0
      8. AS2914   ae-0.r26.osakjp02.jp.bb.gin.ntt.net   20.0%    10   69.5  71.5  69.5  77.0   2.8
      9. AS2914   ae-4.r26.snjsca04.us.bb.gin.ntt.net    0.0%    10  171.8 171.9 171.8 172.1   0.1
     10. AS2914   ae-8.a04.snjsca04.us.bb.gin.ntt.net    0.0%    10  175.3 175.3 175.2 175.4   0.1
     11. AS1299   sjo-b23-link.ip.twelve99.net           0.0%    10  173.6 173.1 172.4 174.0   0.6
     12. AS1299   palo-bb2-link.ip.twelve99.net          0.0%    10  175.4 175.1 174.1 175.8   0.6
     13. AS1299   den-bb2-link.ip.twelve99.net           0.0%    10  197.7 197.8 197.7 198.1   0.1
     14. AS1299   kanc-bb2-link.ip.twelve99.net          0.0%    10  229.5 229.1 228.1 229.7   0.6
     15. AS1299   chi-bb2-link.ip.twelve99.net           0.0%    10  235.9 237.0 235.9 238.0   1.0
     16. AS1299   ewr-bb2-link.ip.twelve99.net          90.0%    10  507.3 507.3 507.3 507.3   0.0
     17. AS1299   ldn-bb2-link.ip.twelve99.net           0.0%    10  229.8 230.7 229.7 232.1   1.0
     18. AS1299   prs-bb2-link.ip.twelve99.net          10.0%    10  229.7 229.2 228.3 229.8   0.6
     19. AS1299   prs-b3-link.ip.twelve99.net           10.0%    10  229.8 229.3 228.2 229.8   0.5
     20. AS34309  80.95.153.138                          0.0%    10  236.1 235.8 235.1 236.5   0.6
     21. AS29066  92.204.249.109                         0.0%    10  236.9 236.9 236.6 237.9   0.4
     22. AS29066  lg-fr.racknerd.com                     0.0%    10  234.8 235.2 234.7 236.2   0.6
    

    This is just that specific far network due to Telia's shitty peering in APAC and Telia being the only T1 the far network is directly connected to/advertising this prefix over.

    Have pushed it via Cogent, via the far network's T2 upstream. Will monitor.

    Can confirm latency dropped to ~155ms.
    Curious - do you have a direct link to Cogent, or is it via CDN77?

    Direct + Telstra Global. Blend in SG/JP will likely change over the next 6 months as we move towards picking up more T1 capacity directly in these metros. Nothing locked in yet though.

    Thanked by 2sh97 borkedascii
  • sh97sh97 Member, Host Rep

    @trewq said:

    @sh97 said:

    @trewq said:

    @sh97 said:

    @OhJohn said: Host Universal (used by @ShockHosting) now uses PCCW for Asia<->Europe

    Interesting, for me it is routed via America lol.

    HOST: sgp2-layer-7950X                              Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS136557 core.rc.sgp.sg.hostuniversal.com.au    0.0%    10    0.2   0.3   0.2   0.3   0.0
      2. AS136557 cr1.rc.sgp.sg.hostuniversal.com.au     0.0%    10    0.2   0.3   0.2   0.3   0.0
      3. AS136557 cr1.sg3.sgp.sg.hostuniversal.com.au    0.0%    10    0.5   0.5   0.5   0.6   0.0
      4. AS???    unn-45-134-214-214.cdn77.com           0.0%    10    0.5   0.5   0.5   0.6   0.0
      5. AS2914   ae-95.a03.sngpsi07.sg.bb.gin.ntt.net   0.0%    10    0.6   0.6   0.6   0.7   0.0
      6. AS2914   ae-3.r24.sngpsi07.sg.bb.gin.ntt.net   10.0%    10    0.6   0.6   0.5   0.6   0.0
      7. AS2914   ae-4.r27.osakjp02.jp.bb.gin.ntt.net   70.0%    10   80.5  78.3  77.0  80.5   2.0
      8. AS2914   ae-0.r26.osakjp02.jp.bb.gin.ntt.net   20.0%    10   69.5  71.5  69.5  77.0   2.8
      9. AS2914   ae-4.r26.snjsca04.us.bb.gin.ntt.net    0.0%    10  171.8 171.9 171.8 172.1   0.1
     10. AS2914   ae-8.a04.snjsca04.us.bb.gin.ntt.net    0.0%    10  175.3 175.3 175.2 175.4   0.1
     11. AS1299   sjo-b23-link.ip.twelve99.net           0.0%    10  173.6 173.1 172.4 174.0   0.6
     12. AS1299   palo-bb2-link.ip.twelve99.net          0.0%    10  175.4 175.1 174.1 175.8   0.6
     13. AS1299   den-bb2-link.ip.twelve99.net           0.0%    10  197.7 197.8 197.7 198.1   0.1
     14. AS1299   kanc-bb2-link.ip.twelve99.net          0.0%    10  229.5 229.1 228.1 229.7   0.6
     15. AS1299   chi-bb2-link.ip.twelve99.net           0.0%    10  235.9 237.0 235.9 238.0   1.0
     16. AS1299   ewr-bb2-link.ip.twelve99.net          90.0%    10  507.3 507.3 507.3 507.3   0.0
     17. AS1299   ldn-bb2-link.ip.twelve99.net           0.0%    10  229.8 230.7 229.7 232.1   1.0
     18. AS1299   prs-bb2-link.ip.twelve99.net          10.0%    10  229.7 229.2 228.3 229.8   0.6
     19. AS1299   prs-b3-link.ip.twelve99.net           10.0%    10  229.8 229.3 228.2 229.8   0.5
     20. AS34309  80.95.153.138                          0.0%    10  236.1 235.8 235.1 236.5   0.6
     21. AS29066  92.204.249.109                         0.0%    10  236.9 236.9 236.6 237.9   0.4
     22. AS29066  lg-fr.racknerd.com                     0.0%    10  234.8 235.2 234.7 236.2   0.6
    

    This is just that specific far network due to Telia's shitty peering in APAC and Telia being the only T1 the far network is directly connected to/advertising this prefix over.

    Have pushed it via Cogent, via the far network's T2 upstream. Will monitor.

    Can confirm latency dropped to ~155ms.
    Curious - do you have a direct link to Cogent, or is it via CDN77?

    Direct + Telstra Global. Blend in SG/JP will likely change over the next 6 months as we move towards picking up more T1 capacity directly in these metros. Nothing locked in yet though.

    Thanks, looks like this is incorrect then: https://bgp.tools/prefix/207.2.122.0/24#connectivity

  • trewqtrewq Administrator, Patron Provider

    @sh97 said:

    @trewq said:

    @sh97 said:

    @trewq said:

    @sh97 said:

    @OhJohn said: Host Universal (used by @ShockHosting) now uses PCCW for Asia<->Europe

    Interesting, for me it is routed via America lol.

    HOST: sgp2-layer-7950X                              Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. AS136557 core.rc.sgp.sg.hostuniversal.com.au    0.0%    10    0.2   0.3   0.2   0.3   0.0
      2. AS136557 cr1.rc.sgp.sg.hostuniversal.com.au     0.0%    10    0.2   0.3   0.2   0.3   0.0
      3. AS136557 cr1.sg3.sgp.sg.hostuniversal.com.au    0.0%    10    0.5   0.5   0.5   0.6   0.0
      4. AS???    unn-45-134-214-214.cdn77.com           0.0%    10    0.5   0.5   0.5   0.6   0.0
      5. AS2914   ae-95.a03.sngpsi07.sg.bb.gin.ntt.net   0.0%    10    0.6   0.6   0.6   0.7   0.0
      6. AS2914   ae-3.r24.sngpsi07.sg.bb.gin.ntt.net   10.0%    10    0.6   0.6   0.5   0.6   0.0
      7. AS2914   ae-4.r27.osakjp02.jp.bb.gin.ntt.net   70.0%    10   80.5  78.3  77.0  80.5   2.0
      8. AS2914   ae-0.r26.osakjp02.jp.bb.gin.ntt.net   20.0%    10   69.5  71.5  69.5  77.0   2.8
      9. AS2914   ae-4.r26.snjsca04.us.bb.gin.ntt.net    0.0%    10  171.8 171.9 171.8 172.1   0.1
     10. AS2914   ae-8.a04.snjsca04.us.bb.gin.ntt.net    0.0%    10  175.3 175.3 175.2 175.4   0.1
     11. AS1299   sjo-b23-link.ip.twelve99.net           0.0%    10  173.6 173.1 172.4 174.0   0.6
     12. AS1299   palo-bb2-link.ip.twelve99.net          0.0%    10  175.4 175.1 174.1 175.8   0.6
     13. AS1299   den-bb2-link.ip.twelve99.net           0.0%    10  197.7 197.8 197.7 198.1   0.1
     14. AS1299   kanc-bb2-link.ip.twelve99.net          0.0%    10  229.5 229.1 228.1 229.7   0.6
     15. AS1299   chi-bb2-link.ip.twelve99.net           0.0%    10  235.9 237.0 235.9 238.0   1.0
     16. AS1299   ewr-bb2-link.ip.twelve99.net          90.0%    10  507.3 507.3 507.3 507.3   0.0
     17. AS1299   ldn-bb2-link.ip.twelve99.net           0.0%    10  229.8 230.7 229.7 232.1   1.0
     18. AS1299   prs-bb2-link.ip.twelve99.net          10.0%    10  229.7 229.2 228.3 229.8   0.6
     19. AS1299   prs-b3-link.ip.twelve99.net           10.0%    10  229.8 229.3 228.2 229.8   0.5
     20. AS34309  80.95.153.138                          0.0%    10  236.1 235.8 235.1 236.5   0.6
     21. AS29066  92.204.249.109                         0.0%    10  236.9 236.9 236.6 237.9   0.4
     22. AS29066  lg-fr.racknerd.com                     0.0%    10  234.8 235.2 234.7 236.2   0.6
    

    This is just that specific far network due to Telia's shitty peering in APAC and Telia being the only T1 the far network is directly connected to/advertising this prefix over.

    Have pushed it via Cogent, via the far network's T2 upstream. Will monitor.

    Can confirm latency dropped to ~155ms.
    Curious - do you have a direct link to Cogent, or is it via CDN77?

    Direct + Telstra Global. Blend in SG/JP will likely change over the next 6 months as we move towards picking up more T1 capacity directly in these metros. Nothing locked in yet though.

    Thanks, looks like this is incorrect then: https://bgp.tools/prefix/207.2.122.0/24#connectivity

    Intentionally using Datapacket for Cogent inbound paths in SG, keeps the AS PATH length nice with the other T1s that see us as peering routes (via other T1s) so we don't drag traffic in over the Cogent direct path when it may not be the best. All prefixes are still advertised to Cogent directly for redundancy, the local pref is just dropped down.

    Trying to avoid the exact issue the far network we were discussing before has.

    Thanked by 2sh97 borkedascii
  • jsgjsg Member, Resident Benchmarker
    edited September 2025

    FWIW:

    The current state, as seen from Mumbai, didn't change (not significantly anyway). Most european targets show around 200 (tendency 250) ms to about 300 ms - now with 2 exceptions, both DE: plusline and core-backbone the latter even better (ca. 10%) than the former, both in latency and download speed.

    Somewhat strange because AFAIK usually cables (from ASOC) land in FR, Marseille or in the UK. So, maybe in NL (which is very near DE), but nope, the NL results are very similar to the UK results and many others.

    A look at the route shows that it seems to go via SGP, Reliance directly to DE, FRA core-backbone; latency is about 110 ms.

    Then, for comparison, I checked the route to NL, AMS (@Clouvider and xtom). Those routes also go via Reliance and SGP but are over 100 ms (actually more like 150 ms) slower.

    So it looks like most routes to Europe (from India), at least currently, go via SGP, but a few like e.g. core-backbone and plusline have found a way better route "around" the Saudi Arabia bottleneck.

  • NeoonNeoon Community Contributor, Veteran
    edited September 2025

    @jsg said:
    FWIW:

    The current state, as seen from Mumbai, didn't change (not significantly anyway). Most european targets show around 200 (tendency 250) ms to about 300 ms - now with 2 exceptions, both DE: plusline and core-backbone the latter even better (ca. 10%) than the former, both in latency and download speed.

    No, I had a stable 130ms link to Mumbai from Europe.
    Right now it sits at 174ms for me, was 182ms earlier today.

    Bengaluru is lower than Mumbai right now, interestingly.

  • jsgjsg Member, Resident Benchmarker

    @Neoon said:

    @jsg said:
    FWIW:

    The current state, as seen from Mumbai, didn't change (not significantly anyway). Most european targets show around 200 (tendency 250) ms to about 300 ms - now with 2 exceptions, both DE: plusline and core-backbone the latter even better (ca. 10%) than the former, both in latency and download speed.

    No, I had a stable 130ms link to Mumbai from Europe.

    Congrats - wherever in Europe you tested ...
    In case this is a pissing contest, I win because I see even better numbers than you (to at least two providers/DC's)

    Right now it sits at 174ms for me, was 182ms earlier today.

    Nice.

    Bengaluru is lower than Mumbai right now, interestingly.

    Maybe because Bengaluru is closer to the main undersea cable (a side arm of which goes along the indian coasts). Just a guess, I don't pretend to know for sure.

    I tested only Mumbai that is, from Mumbai to diverse european locations.

  • NeoonNeoon Community Contributor, Veteran
    edited September 2025

    @jsg said:

    @Neoon said:

    @jsg said:
    FWIW:

    The current state, as seen from Mumbai, didn't change (not significantly anyway). Most european targets show around 200 (tendency 250) ms to about 300 ms - now with 2 exceptions, both DE: plusline and core-backbone the latter even better (ca. 10%) than the former, both in latency and download speed.

    No, I had a stable 130ms link to Mumbai from Europe.

    Congrats - wherever in Europe you tested ...
    In case this is a pissing contest, I win because I see even better numbers than you (to at least two providers/DC's)

    Marseille, not just kidding, central europe, Frankfurt.
    Yes of course, depending from where you test, you get better results.

    I just wanted to show, that the cable cut isn't as worse as it sounds.

    Maybe because Bengaluru is closer to the main undersea cable (a side arm of which goes along the indian coasts). Just a guess, I don't pretend to know for sure.

    I tested only Mumbai that is, from Mumbai to diverse european locations.

    Nah, most of the cables land in Mumbai.

  • jsgjsg Member, Resident Benchmarker

    @Neoon said:

    @jsg said:

    @Neoon said:

    @jsg said:
    FWIW:

    The current state, as seen from Mumbai, didn't change (not significantly anyway). Most european targets show around 200 (tendency 250) ms to about 300 ms - now with 2 exceptions, both DE: plusline and core-backbone the latter even better (ca. 10%) than the former, both in latency and download speed.

    No, I had a stable 130ms link to Mumbai from Europe.

    Congrats - wherever in Europe you tested ...
    In case this is a pissing contest, I win because I see even better numbers than you (to at least two providers/DC's)

    Marseille, not just kidding, central europe, Frankfurt.
    Yes of course, depending from where you test, you get better results.

    I just wanted to show, that the cable cut isn't as worse as it sounds.

    Well, around 250 ms from Mumbai to most of Europe does look quite bad to me.
    But again, my main point is how come that 2 european providers/networks are very significantly better/lower latency than the rest?
    One suspicion I have is that they simply react quicker and quite likely have alternative routes ready "in the drawer" if needed.

    Maybe because Bengaluru is closer to the main undersea cable (a side arm of which goes along the indian coasts). Just a guess, I don't pretend to know for sure.

    I tested only Mumbai that is, from Mumbai to diverse european locations.

    Nah, most of the cables land in Mumbai.

    Yes, but there also is ICE IV which lands in IN, Kochi and has a direct fiber from there across land to IN, Chennai which might well explain your a.m. observation (as Bengaluru is situated roughly on that axis) and also is significantly faster than going around the southern part of India possibly even via Sri Lanka.

    That said, I still wonder how a cable problem in Jeddah can harm Europe - ASOC connectivity that much.

  • NeoonNeoon Community Contributor, Veteran

    @jsg said:

    @Neoon said:

    @jsg said:

    @Neoon said:

    @jsg said:
    FWIW:

    The current state, as seen from Mumbai, didn't change (not significantly anyway). Most european targets show around 200 (tendency 250) ms to about 300 ms - now with 2 exceptions, both DE: plusline and core-backbone the latter even better (ca. 10%) than the former, both in latency and download speed.

    No, I had a stable 130ms link to Mumbai from Europe.

    Congrats - wherever in Europe you tested ...
    In case this is a pissing contest, I win because I see even better numbers than you (to at least two providers/DC's)

    Marseille, not just kidding, central europe, Frankfurt.
    Yes of course, depending from where you test, you get better results.

    I just wanted to show, that the cable cut isn't as worse as it sounds.

    Well, around 250 ms from Mumbai to most of Europe does look quite bad to me.
    But again, my main point is how come that 2 european providers/networks are very significantly better/lower latency than the rest?
    One suspicion I have is that they simply react quicker and quite likely have alternative routes ready "in the drawer" if needed.

    Maybe because Bengaluru is closer to the main undersea cable (a side arm of which goes along the indian coasts). Just a guess, I don't pretend to know for sure.

    I tested only Mumbai that is, from Mumbai to diverse european locations.

    Nah, most of the cables land in Mumbai.

    Yes, but there also is ICE IV which lands in IN, Kochi and has a direct fiber from there across land to IN, Chennai which might well explain your a.m. observation (as Bengaluru is situated roughly on that axis) and also is significantly faster than going around the southern part of India possibly even via Sri Lanka.

    That said, I still wonder how a cable problem in Jeddah can harm Europe - ASOC connectivity that much.

    It just goes directly to India instead of going via SG,I just checked.

  • jsgjsg Member, Resident Benchmarker

    @Neoon said:

    @jsg said:

    @Neoon said:

    @jsg said:

    @Neoon said:

    @jsg said:
    FWIW:

    The current state, as seen from Mumbai, didn't change (not significantly anyway). Most european targets show around 200 (tendency 250) ms to about 300 ms - now with 2 exceptions, both DE: plusline and core-backbone the latter even better (ca. 10%) than the former, both in latency and download speed.

    No, I had a stable 130ms link to Mumbai from Europe.

    Congrats - wherever in Europe you tested ...
    In case this is a pissing contest, I win because I see even better numbers than you (to at least two providers/DC's)

    Marseille, not just kidding, central europe, Frankfurt.
    Yes of course, depending from where you test, you get better results.

    I just wanted to show, that the cable cut isn't as worse as it sounds.

    Well, around 250 ms from Mumbai to most of Europe does look quite bad to me.
    But again, my main point is how come that 2 european providers/networks are very significantly better/lower latency than the rest?
    One suspicion I have is that they simply react quicker and quite likely have alternative routes ready "in the drawer" if needed.

    Maybe because Bengaluru is closer to the main undersea cable (a side arm of which goes along the indian coasts). Just a guess, I don't pretend to know for sure.

    I tested only Mumbai that is, from Mumbai to diverse european locations.

    Nah, most of the cables land in Mumbai.

    Yes, but there also is ICE IV which lands in IN, Kochi and has a direct fiber from there across land to IN, Chennai which might well explain your a.m. observation (as Bengaluru is situated roughly on that axis) and also is significantly faster than going around the southern part of India possibly even via Sri Lanka.

    That said, I still wonder how a cable problem in Jeddah can harm Europe - ASOC connectivity that much.

    It just goes directly to India instead of going via SG,I just checked.

    That could explain it indeed.

  • davidobrik567davidobrik567 Member
    edited September 2025

    seems to be impacting UAE/india/TATA traffic only.

    SMW4 is an old cable and most transit have redundancies on SMW5-AAE1, SG<>FR is relatively fine.

  • Protocol903Protocol903 Member
    edited September 2025

    @jsg said: The current state, as seen from Mumbai, didn't change (not significantly anyway). Most european targets show around 200 (tendency 250) ms to about 300 ms - now with 2 exceptions, both DE: plusline and core-backbone the latter even better (ca. 10%) than the former, both in latency and download speed.

    I can confirm it has gotten much worse in Mumbai. I have a home connection, and 2 servers in Mumbai and both are reporting significantly higher latency to my Netcup Vienna chicken. Normally the ping is 150ms and yesterday after this underseas cable news, it was 220ms+ and today it has gone worse to 300ms. It is now being routed via singapore to US, Santa Clara and then to Europe.

    Edit: If I use Cloudflare WARP, the Cloudflare routing takes me through normal EU route but I'm still seeing elevated latency. Netcup's IPv6, however, is still showing 262ms ping.

    Thanked by 3borkedascii sh97 jsg
  • sh97sh97 Member, Host Rep

    Couple of good reads here


    I think the situation is even worse in UAE, as compared to my indian chickens. Everything is super slow. DU (AS15802) routing has taken a big hit, and they're now passing a lot of traffic through China Mobile, taking more precedence over even IX traffic.

    Etisalat UAE (AS8966) seems to have done a good job of working around this problem, they've got the latencies down by smarter BGP selections I guess.

    Thanked by 2borkedascii oloke
Sign In or Register to comment.