Airtel V-Fibre Chennai - Google DNS

[georgemp]

Hi,

Any airtel v-fiber users in Chennai facing issues pinging Google DNS? For some reason, "ping 8.8.8.8" has been timing out for me over the last couple of days. Most of the rest of the internet seems to be reachable though (although it takes a couple of tries to load a website at times). Thanks

 

[Karan]

You are not alone, although I can ping 8.8.8.8, and my browsing isn't affected. However, over the past week or so, the ping and the routing isn't the same as it used to be.

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=83ms TTL=47
Reply from 8.8.8.8: bytes=32 time=83ms TTL=47
Reply from 8.8.8.8: bytes=32 time=84ms TTL=47
Reply from 8.8.8.8: bytes=32 time=83ms TTL=47

My usual ping time is 3 to 4ms, it looks the same with google.co.in and .com as well

Pinging google.co.in [216.58.199.163] with 32 bytes of data:
Reply from 216.58.199.163: bytes=32 time=44ms TTL=55
Reply from 216.58.199.163: bytes=32 time=43ms TTL=55
Reply from 216.58.199.163: bytes=32 time=44ms TTL=55
Reply from 216.58.199.163: bytes=32 time=42ms TTL=55

Pinging google.com [216.58.199.174] with 32 bytes of data:
Reply from 216.58.199.174: bytes=32 time=47ms TTL=55
Reply from 216.58.199.174: bytes=32 time=47ms TTL=55
Reply from 216.58.199.174: bytes=32 time=47ms TTL=55
Reply from 216.58.199.174: bytes=32 time=47ms TTL=55

Again, instead of the usual 3 to 4 ms, I am getting this, on top of this the data is being routed to Mumbai instead of the usual Delhi server.

It gets really interesting when I do a traceroute to 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms abts-north-static-076.220.160.122.airtelbroadband.in [122.160.220.76]
3 2 ms 2 ms 3 ms abts-north-static-147.130.160.122.airtelbroadband.in [122.160.130.147]
4 * * * Request timed out.
5 3 ms 3 ms 2 ms 125.17.177.113
6 9 ms 9 ms 8 ms 72.14.205.93
7 4 ms 3 ms 3 ms 108.170.251.103
8 54 ms 58 ms 54 ms 216.239.41.153
9 114 ms 84 ms 85 ms 209.85.249.195
10 84 ms 85 ms 85 ms 216.239.51.57
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 83 ms 85 ms 84 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Just take a look at that! I don't know if airtel has screwed up the routing for Google's CDNs or if Google themselves have messed something up.

 

[Karan]

Just switched my primary DNS over to Google DNS B instead, getting the ping times that I expected. Still no luck with actual routing to google.co.in and .com. Will let that work itself out

Pinging 8.8.4.4 with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=4ms TTL=57
Reply from 8.8.4.4: bytes=32 time=3ms TTL=57
Reply from 8.8.4.4: bytes=32 time=4ms TTL=57
Reply from 8.8.4.4: bytes=32 time=3ms TTL=57

Tracing route to google-public-dns-b.google.com [8.8.4.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms abts-north-static-076.220.160.122.airtelbroadband.in [122.160.220.76]
3 * * * Request timed out.
4 2 ms 2 ms 3 ms 125.17.177.113
5 58 ms 55 ms 52 ms 72.14.205.93
6 3 ms 3 ms 3 ms 108.170.251.97
7 4 ms 3 ms 4 ms 108.170.228.227
8 3 ms 3 ms 4 ms google-public-dns-b.google.com [8.8.4.4]

Trace complete.

 

[georgemp]

Thanks Karan. It looks like it's back to (or close to) normal now. Pings aren't timing out (about 7-10ms) and trace routes are completing

 

[georgemp]

Guess I spoke too soon. Browsing is a PITA...takes multiple reloads to actually load a website

 

[Karan]

Are you getting the same issues if you switch to 8.8.4.4?

 

---

[georgemp]

Unfortunately yes. Not sure what the issue is. The pings and trace routes to google dns complete fine. But, browsing in general is a pain. Sites hang mid-load or I have to refresh few times. Hopefully it automagically resolves soon 🙂