BSNL FTTH Routing Improved?

AshikAliLive

AshikAliLive

Messages
117
Location
Mysore
ISP
BSNL
Airtel Fiber
Hey guys, From last 2 days I see my latency improved a lot, don't know what they improved/upgraded.

Location = Mysore, Karnataka.
Plan = 1277.

Usually this is what I used to get.
1.1.1.1 = 30 - 40ms.
8.8.8.8 = 25 - 30ms.
9.9.9.9 = 70 - 80ms.

but now
Screenshot 2020-06-21 at 2.46.59 PM.jpg



Generally I get 60 - 70 ping to Singapore servers.

but now
Screenshot 2020-06-21 at 3.01.47 PM.jpg


Pings to all the servers is improved a lot. I don't know, wheather it is normal or not for a fiber connection. It used to be worst before the national wide outage, but now I getting very stable connection and pings.

Anyone seeing any improvement?
 
Last edited:
Sort by date Sort by votes
Yep, getting 70ms to Singapore.
 
Upvote 0
AshikAliLive said:
Hey guys, From last 2 days I seeing my latency improved a lot, don't know what they improved/upgraded.

Location = Mysore, Karnataka.
Plan = 1277.

Usually this is what I used to get.
1.1.1.1 = 30 - 40ms.
8.8.8.8 = 25 - 30ms.
9.9.9.9 = 70 - 80ms.

but now
View attachment 2501


Generally I get 60 - 70 ping to Singapore servers.

but now
View attachment 2502

Pings to all the servers is improved a lot. I don't know, wheather it is normal or not for a fiber connection. It used to worst before the national wide outage, but now I getting very stable connection and pings.

Anyone seeing any improvement?
Click to expand...
Please post traceroutes too.
 
Upvote 0
It;s optimized for some routes and for other not so much:

1.1.1.1 is down from 50ms + to 18ms
8.8.8.8 is up from 13-15 ms to 16ms

9.9.9.9 is 90+ms

Google cloud : Up from 38 ms to 68 ms.

Datapacket Servers:
Europe is any location 200-220 ms( mostly 220ms for lots of locations)

Hongkong: 119 ms
Singapore: 214 ms
Tokyo : 275 ms
Los Angeles : 255 ms ?????
NewYork : 232 ms

London 218 ms
Frankfurt : 198 ms (Weirdly pings to Frankfurt has always been relatively better than other for me throughout)
Amsterdam : 210 ms

Linode:

London : 192 ms
Frankfurt 143 ms

DigitalOcean:
Frankfut : 150 ms.

GCP: worst pings...
Mumbai alone is 250+ms

AWS:


US-East (Virginia)247 ms
US East (Ohio)303 ms
US-West (California)276 ms
US-West (Oregon)314 ms
Canada (Central)273 ms
Europe (Ireland)212 ms
Europe (London)202 ms
Europe (Frankfurt)171 ms
Europe (Paris)199 ms
Europe (Stockholm)210 ms
Middle East (Bahrain)83 ms from 74 ms
Asia Pacific (Hong Kong)143 ms
Asia Pacific (Mumbai)68 ms from 60
Asia Pacific (Osaka-Local)184 ms
Asia Pacific (Seoul)197 ms
Asia Pacific (Singapore)123 ms
Asia Pacific (Sydney)228 ms
Asia Pacific (Tokyo)194 ms
South America (São Paulo)444 ms
China (Beijing)355 ms
China (Ningxia)310 ms
AWS GovCloud (US-East)312 ms
AWS GovCloud (US)300 ms

...so on
 
Upvote 0
AWS
RegionLatency
US-East (Virginia)297 ms
US East (Ohio)306 ms
US-West (California)255 ms
US-West (Oregon)262 ms
Canada (Central)300 ms
Europe (Ireland)186 ms
Europe (London)178 ms
Europe (Frankfurt)173 ms
Europe (Paris)179 ms
Europe (Stockholm)190 ms
Middle East (Bahrain)71 ms
Asia Pacific (Hong Kong)153 ms
Asia Pacific (Mumbai)41 ms
Asia Pacific (Osaka-Local)120 ms
Asia Pacific (Seoul)150 ms
Asia Pacific (Singapore)56 ms
Asia Pacific (Sydney)168 ms
Asia Pacific (Tokyo)123 ms
South America (São Paulo)411 ms
China (Beijing)407 ms
China (Ningxia)326 ms
AWS GovCloud (US-East)294 ms
AWS GovCloud (US)270 ms

London speedtest servers = ~ 145 - 160 ms

But mine is not capped though, BTW I have IPV6 enabled.

traceroute to 1.1.1.1
Screenshot 2020-06-21 at 8.33.44 PM.webp


traceroute to 8.8.8.8
Screenshot 2020-06-21 at 8.36.43 PM.webp
\

Getting this "@not a txt record" error, don't know how to get rid of this.
 

Upvote 0
Yes, routing seems to have improved for BSNL FTTH from here in tvm, Kerala. The problem is if it will be consistent. Since the last 6-8 months, the min ping when checking is quite low(er).

cloudflare23 ms
cf filtered 1.0.0.240 ms
google dns18
quad9*93
opendns45
valve csgo maa (155.133.232.98) @5trange 23
csgo bom43
bsnl dns5 ms

*quad9 trace below.
ping_quad9.webp
 
Upvote 0
GCP Pings
Global HTTP Load Balancer
global		39 ms
Mumbai
asia-south1		42 ms
Singapore
asia-southeast1		48 ms
Jakarta
asia-southeast2		62 ms
Hong Kong
asia-east2		83 ms
Taiwan
asia-east1		94 ms
Tokyo
asia-northeast1		114 ms
Seoul
asia-northeast3		118 ms
Osaka
asia-northeast2		128 ms
Sydney
australia-southeast1		139 ms
Oregon, USA
us-west1		198 ms
Los Angeles, USA
us-west2		208 ms
Las Vegas, USA
us-west4		214 ms
Salt Lake City, USA
us-west3		220 ms
Iowa, USA
us-central1		228 ms
Northern Virginia, USA
us-east4		257 ms
South Carolina, USA
us-east1		263 ms
Montreal, Canada
northamerica-northeast1		265 ms
London, UK
europe-west2		328 ms
Belgium
europe-west1		332 ms
Frankfurt, Germany
europe-west3		340 ms
Zurich, Switzerland
europe-west6		340 ms
Netherlands
europe-west4		342 ms
Hamina, Finland
europe-north1		364 ms
São Paulo
southamerica-east1		367 ms
 
Upvote 0
Still bad for me
REGIONMEDIAN LATENCY
Mumbai
asia-south1		84 ms
Global HTTP Load Balancer
global		85 ms
Singapore
asia-southeast1		90 ms
Jakarta
asia-southeast2		110 ms
Hong Kong
asia-east2		127 ms
Taiwan
asia-east1		141 ms
Tokyo
asia-northeast1		159 ms
Osaka
asia-northeast2		165 ms
Seoul
asia-northeast3		167 ms
Sydney
australia-southeast1		179 ms
Oregon, USA
us-west1		239 ms
Los Angeles, USA
us-west2		249 ms
Las Vegas, USA
us-west4		258 ms
Salt Lake City, USA
us-west3		263 ms
Iowa, USA
us-central1		275 ms
Northern Virginia, USA
us-east4		294 ms
Montreal, Canada
northamerica-northeast1		312 ms
South Carolina, USA
us-east1		314 ms
London, UK
europe-west2		370 ms
Netherlands
europe-west4		375 ms
Belgium
europe-west1		379 ms
Zurich, Switzerland
europe-west6		382 ms
Frankfurt, Germany
europe-west3		393 ms
Hamina, Finland
europe-north1		412 ms
São Paulo
southamerica-east1		421 ms
 
Upvote 0
AWS -

RegionLatency (ms)
CloudFront CDN31.2
Mumbai ap-south-149.4
Singapore ap-southeast-157.6
Bahrain me-south-182
Tokyo ap-northeast-1127.4
Osaka ap-northeast-3140
Sydney ap-southeast-2152
Seoul ap-northeast-2158.2
Frankfurt eu-central-1175.8
Paris eu-west-3182.4
London eu-west-2184.6
Milan eu-south-1189
Ireland eu-west-1190
Stockholm eu-north-1196.75
N. California us-west-1233
Oregon us-west-2242
Hong Kong ap-east-1251.6
Canada Central ca-central-1265.6
N. Virginia us-east-1273.6
Ohio us-east-2277.2
Cape Town af-south-1321
Beijing cn-north-1344
Ningxia cn-northwest-1353
São Paulo sa-east-1388.25
 
Upvote 0
eriek_halenx said:
Yes, routing seems to have improved for BSNL FTTH from here in tvm, Kerala. The problem is if it will be consistent. Since the last 6-8 months, the min ping when checking is quite low(er).

cloudflare23 ms
cf filtered 1.0.0.240 ms
google dns18
quad9*93
opendns45
valve csgo maa (155.133.232.98) @5trange23
csgo bom43
bsnl dns5 ms

*quad9 trace below.
View attachment 2518
Click to expand...

To add,

ping has remained stable at these values all of last week (checked abt 2-3 times a day.) Yey to Bsnl! 😀

Ping to sgp remains high(er) than expected. (read quad9 issues)

This is in 59.x. ip range that I usually get. The pings is 117.x. IP range were substantially higher the last time I checked.
 
Upvote 0

Similar threads

rohit267
BSNL has worst possible Routing.
2 3
Replies
31
Views
5,457
guywithproblems
Y
BSNL FTTH Syrotech bridge mode - working configuration
2
Replies
28
Views
4,952
!!..PD..!!
Zuke
  • Featured
  • Article Article
My experience so far with Reliance JioFiber
6 7 8 9 10
Replies
143
Views
19,412
victim
R
  • Question Question
Low International Speed on new connection.
Replies
2
Views
746
reaps
Top