BSNL is making me go INSANE !!

  • Thread starter Thread starter Orion Pax
  • Start date Start date
  • Replies Replies 10
  • Views Views 208
Messages
16
Location
KL
ISP
BSNL FTTH
The MTNL ips assigned by bsnl is messing up the routing so bad, for eg return path from aws tokyo: tokyo->singapore->us(los angeles) via GTT . wtf is that
Why the hell bsnl took mtnl in, it should have burned to the ground. Im seriously going insane. The international routing is messed up and its been months.

Guys share your thoughts
 
If the problem is the return path, then the problem is with AWS. You cannot really control inbound traffic.

MTNL, i.e., BSNL, uses Airtel or Tata for their upstream (the best available in India for international transit).

I tested a few MTNL IPs from Mumbai, and it seems to be routed correctly. What's yours?

Code:
 1. AS???   _gateway (244.5.0.235)                                   0.0%    0   3  32.6   36.3  43.9
 2. AS???   240.1.56.8 (240.1.56.8)                                  0.0%    0   3   1.0    0.5   0.8
 3. AS???   242.3.96.87 (242.3.96.87)                                0.0%    0   3   1.2    0.1   0.7
 4. AS???   240.1.168.14 (240.1.168.14)                              0.0%    0   3  67.8    0.2  34.1
 5. AS???   242.4.77.7 (242.4.77.7)                                  0.0%    0   3  67.7    1.3  34.7
 6. AS16509 52.46.167.158 (52.46.167.158)                            0.0%    0   3  68.7    0.3  34.5
 7. AS16509 52.46.167.159 (52.46.167.159)                           33.3%    1   2  70.4    1.8   3.6
 8. AS???   116.119.161.114 (116.119.161.114)                        0.0%    0   3 146.2    1.5  74.2
 9. AS9498  nsg-static-074.107.72.182.airtel.in (182.72.107.74)      0.0%    0   3 144.2    0.2  72.1
10. AS???   (waiting for reply)
 
@Orion Pax Which district are you from? Are you getting a public IP?
I’m from Kerala, and I’m on CGNAT, which has been much more stable and reliable than a public IP for me.

You can DM me on Telegram: @sanemi0558

Previously, my inbound traffic was routed through SLT, which resulted in poor inbound latency. I requested them to switch my inbound to Airtel or Jio, and now I have Airtel, Jio, and three Tier-1(Cogent,PCCW,Sparkle) inbound provider as well.
 
Last edited:
I would also advise to raise the issue with BSNL Jto as well along with all the other responses
 
Here's mine from bhopal reigon BSNL.

Region Latency (ms)
Mumbai ap-south-1 24.5
CloudFront CDN 27
Hyderabad ap-south-2 37.5
London eu-west-2 154.5
Paris eu-west-3 161.5
Ireland eu-west-1 165.5
UAE me-central-1 167
Frankfurt eu-central-1 168
Zürich eu-central-2 171.5
Milan eu-south-1 177.5
Stockholm eu-north-1 177.5
Spain eu-south-2 183
Singapore ap-southeast-1 188.5
Malaysia ap-southeast-5 210
Israel il-central-1 215
Jakarta ap-southeast-3 215.5
Thailand ap-southeast-7 220
Hong Kong ap-east-1 245
Seoul ap-northeast-2 261.5
 
Back