High page load time on Airtel Broadband

[droidrex]

@nishantt6969 I have already tried complaining. All that they say is, your ping to Guwahati server in speed test is ok. Speed is ok. So we can't consider other sites. I've hearing the same since months now
Also Can I DM you?

 

[Lolita_Magnum]

Then according to this method, Airtel Hyderabad is showing up as 6km, while Airtel Mumbai is 624km.
And my gateway is showing up as Delhi.
122.186.210.9

 

[nishantt6969]

@Lolita_Magnum sometimes this works sometimes not. I was just trying to open possibilities.

 

[sloj]

@sloj I used to get better latency few months back. 30-40ms . So this doesn't seem normal

30-40 ms to where, google dns? Yeah, it was possible about a month or so back. Even now it can be achieved but not constant. But something changed recently. Cloudflare still stays in the range of 50-ish ms.

C:\Users\Dell>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=52ms TTL=58
Reply from 8.8.8.8: bytes=32 time=53ms TTL=58
Reply from 8.8.8.8: bytes=32 time=53ms TTL=58
Reply from 8.8.8.8: bytes=32 time=52ms TTL=58

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 53ms, Average = 52ms

C:\Users\dell>ping 8.8.4.4

Pinging 8.8.4.4 with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=35ms TTL=58
Reply from 8.8.4.4: bytes=32 time=36ms TTL=58
Reply from 8.8.4.4: bytes=32 time=37ms TTL=58
Reply from 8.8.4.4: bytes=32 time=36ms TTL=58

Ping statistics for 8.8.4.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 37ms, Average = 36ms

The above 2 were done about 2 hours ago.

C:\Users\dell>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=54ms TTL=58
Reply from 8.8.8.8: bytes=32 time=54ms TTL=58
Reply from 8.8.8.8: bytes=32 time=54ms TTL=58
Reply from 8.8.8.8: bytes=32 time=53ms TTL=58

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 54ms, Average = 53ms

C:\Users\dell>ping 8.8.4.4

Pinging 8.8.4.4 with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=46ms TTL=58
Reply from 8.8.4.4: bytes=32 time=46ms TTL=58
Reply from 8.8.4.4: bytes=32 time=47ms TTL=58
Reply from 8.8.4.4: bytes=32 time=46ms TTL=58

Ping statistics for 8.8.4.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 47ms, Average = 46ms

And these just now.

 

[Lolita_Magnum]

ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=2ms TTL=118
Reply from 8.8.8.8: bytes=32 time=2ms TTL=118
Reply from 8.8.8.8: bytes=32 time=2ms TTL=118
Reply from 8.8.8.8: bytes=32 time=2ms TTL=118

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

ping 8.8.4.4

Pinging 8.8.4.4 with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=7ms TTL=59
Reply from 8.8.4.4: bytes=32 time=6ms TTL=59
Reply from 8.8.4.4: bytes=32 time=6ms TTL=59
Reply from 8.8.4.4: bytes=32 time=6ms TTL=59

Ping statistics for 8.8.4.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 7ms, Average = 6ms

8.8.4.4 is having higher latency than 8.8.8.8. I guess unless google, spreads out its servers into more regions than just metro cities, a slight change in the gateway location will affect ping times.

 

[sloj]

The thread topic is already derailing but what can we do. So I went to do a few (a lot of) speedtest and dns hunting. Last month it was like 23 ms (lowest) to Kolkata Airtel Broadband speedtest server and 37 ms (lowest) to Guwahati Bharti Airtel Ltd. speedtest server. This month it went from 23 ms to 75 ms and 37 ms to 123 ms. Just wow.
Now onto DNS. I just found Alternate DNS to be faster at 25 ms than Google DNS at 36 ms lowest. The heck.

Update - Alternate DNS isn't working. While the IP Address is reachable the DNS isn't working.

 

---

[Lolita_Magnum]

@sloj Try DnsBench, https://www.grc.com/dns/benchmark.htm using this I realized sometimes that latencies are not everything. Since a lot of DNS IPs are just recursive, this also tests their performance and stability.

 

[Aashish.007]

@Lolita_Magnum backed, this grc dns benchmark is good indeed. Best way to eliminate dns slowdowns would be to run your own recursive caching server, wouldn't it?

 

[sloj]

@Lolita_Magnum Been there done that, long ago.

 

[droidrex]

30-40 ms to where, google dns? Yeah, it was possible about a month or so back. Even now it can be achieved but not constant. But something changed recently. Cloudflare still stays in the range of 50-ish ms.

yeah google dns. Yeah it was much bettery few months back. What happened