Questions about Airtel Xstream Broadband

[hallow2087]

@Abhi_VNS You don't need to be a gamer to check the latency to different servers across the world which gives an overall idea about the quality of the connection. Latency matters in everything not only gaming. If possible please check this and post the result here: CS:GO Ping Test — Ping Test Live

Also, mention where you are residing.

 

[Makino]

Airtel Guwahati

 

[nishantt6969]

@Khalidahmed8 this is done through lan cable or over wifi? 75ms to mumbai is bad.

 

[hallow2087]

Yeah those are pretty bad results. Pretty sure that was done on LAN otherwise it defeats the purpose of checking latency at first place.

 

[nishantt6969]

This is mine. Btw in csgo I get 27-32 to mumbai servers.

Source

 

[Anurag Bhatia]

Airtel Guwahati

Can you please share result of ping and trace to mumbaispeedtest1.airtel.in

That's speedtest server within their network and thus eBGP won't have an impact here. This should help us in setting expectation of best possible latency one can get to Mumbai.

 

---

[ankurm]

Airtel is still providing VDSL connection in my area. Can you please let me know what plans are applicable to me?

 

[Makino]

Can you please share result of ping and trace to mumbaispeedtest1.airtel.in

That's speedtest server within their network and thus eBGP won't have an impact here. This should help us in setting expectation of best possible latency one can get to Mumbai.

@Anurag Bhatia

Pinging mumbaispeedtest1.airtel.in [223.224.134.122] with 32 bytes of data:
Reply from 223.224.134.122: bytes=32 time=58ms TTL=59
Reply from 223.224.134.122: bytes=32 time=60ms TTL=59
Reply from 223.224.134.122: bytes=32 time=59ms TTL=59
Reply from 223.224.134.122: bytes=32 time=60ms TTL=59
Reply from 223.224.134.122: bytes=32 time=59ms TTL=59
Reply from 223.224.134.122: bytes=32 time=60ms TTL=59
Reply from 223.224.134.122: bytes=32 time=60ms TTL=59
Reply from 223.224.134.122: bytes=32 time=59ms TTL=59
Reply from 223.224.134.122: bytes=32 time=59ms TTL=59
Reply from 223.224.134.122: bytes=32 time=58ms TTL=59

Tracing route to mumbaispeedtest1.airtel.in [223.224.134.122]
over a maximum of 30 hops:

1 38 ms 1 ms 2 ms dsldevice.lan [192.168.1.1]
2 40 ms 21 ms 21 ms abts-mh-dynamic-001.35.169.122.airtelbroadband.in [122.169.35.1]
3 52 ms 22 ms 21 ms 59.144.120.201
4 61 ms 60 ms 68 ms 116.119.44.226
5 62 ms 62 ms 61 ms 61.95.151.6
6 60 ms 58 ms 61 ms 223.224.134.122

Trace complete.

 

[Makino]

@Khalidahmed8 this is done through lan cable or over wifi? 75ms to mumbai is bad.

Yes it was done on LAN.

 

[Anurag Bhatia]

@Anurag Bhatia

Interesting. So lowest you can get is 58ms to Mumbai. Bit high if we look purely based on distance but again path would be quite odd considering the hard terrain.

Now you can focus on why server in Mumbai was giving you 75ms as you shared earlier. That's 17ms more than expected.