BSNL Bad Routing

  • Thread starter Thread starter Orion Pax
  • Start date Start date
  • Replies Replies 8
  • Views Views 132
I am experiencing significant latency issues caused by a damaged undersea fiber-optic cable connecting India to Europe. I’ve had persistent trouble with my Excitel connection and have opened multiple tickets to improve the routing, but the issue remains unresolved.

Previously, BSNL’s FTTH latency was much better; for example, Excitel showed an RTT (Round Trip Time) of 230ms to a specific IP, while BSNL was only 160ms. However, about two months ago, BSNL services went down. When I contacted my Local Cable Operator (LCO), he requested a traceroute from a functioning connection. I provided the traceroute from my Excitel line. Since then, it appears BSNL has adopted the same routing as Excitel, resulting in both providers now showing high latency of over 200ms for that same IP.
 
image.png

Current Jio Fiber Latency.
 
@Orion Pax yes, still not resolved. All data traffic of Europe is routed via Singapore, we don't have direct fiber-optic connectivity. Just run the trace route for any server hosted in the EU you can see it will be routed via Chennai-Singapore.
 
Back