Airtel Xstream Fiber Broadband in Patna/Bihar

@imdarkray I use Huawei router, previously the Telephone light on it used to blink continuously, but it isnt blinking now. Is it because of bridge mode or any other thing?
 
@nishantt6969 it stays steady when telephone is not in use (not on a call). When on a call, it blinks.
 
Got a call from a technician, He said the same thing. We do not have landline services started in Bihar.

Can anyone confirm if he has Airtel landline working in Patna or Bihar? I have a dial tone, the voice line shows up, the VOIP light is on and I can make calls to 121 but not any phone or mobile. Calling on the landline number from any other phone- it says the number is invalid.
 
@mordfustang geographical distance, LCO link load, Airtel link load, server load, route congestion among other things affect response times. Choose a server near you or upgrade your connection. What is the IP of that server? I'd like to check what ping times I get from Pune.
 
No one has the real valorant IP Address. You connect to the nearest global accelerator.
For a rough idea here is a sample mumbai aws ip: 3.6.0.0
 


I got in touch with the airtel technical team for patna like around 15-20 days ago and the person told me that they are setting up airtel server for bihar which he said will reduce our ping drastically. I tried contacting him toda but no one picked up the phone, I am gonna try contacting them tomorrow to get an answer.
 
FROM ROUTER:

Using Airtel:


PING 3.6.0.0 (3.6.0.0) from 171.50.239.58: 56 data bytes
64 bytes from 3.6.0.0: icmp_seq=0 ttl=243 time=8.652 ms
64 bytes from 3.6.0.0: icmp_seq=1 ttl=243 time=8.236 ms
64 bytes from 3.6.0.0: icmp_seq=2 ttl=243 time=8.123 ms
64 bytes from 3.6.0.0: icmp_seq=3 ttl=243 time=8.905 ms
64 bytes from 3.6.0.0: icmp_seq=4 ttl=243 time=8.385 ms

--- 3.6.0.0 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.123/8.460/8.905/0.284 ms

Using Tata Sky:

PING 3.6.0.0 (3.6.0.0) from 100.72.129.75: 56 data bytes
64 bytes from 3.6.0.0: icmp_seq=0 ttl=243 time=13.803 ms
64 bytes from 3.6.0.0: icmp_seq=1 ttl=243 time=11.447 ms
64 bytes from 3.6.0.0: icmp_seq=2 ttl=243 time=11.967 ms
64 bytes from 3.6.0.0: icmp_seq=3 ttl=243 time=12.915 ms
64 bytes from 3.6.0.0: icmp_seq=4 ttl=243 time=18.076 ms

--- 3.6.0.0 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.447/13.642/18.076/2.360 ms

From Windows Desktop (wired 1 Gbps LAN):

Airtel:


ping 3.6.0.0

Pinging 3.6.0.0 with 32 bytes of data:
Reply from 3.6.0.0: bytes=32 time=8ms TTL=242
Reply from 3.6.0.0: bytes=32 time=8ms TTL=242
Reply from 3.6.0.0: bytes=32 time=8ms TTL=242
Reply from 3.6.0.0: bytes=32 time=8ms TTL=242

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

Tata Sky:
ping 3.6.0.0

Pinging 3.6.0.0 with 32 bytes of data:
Reply from 3.6.0.0: bytes=32 time=14ms TTL=242
Reply from 3.6.0.0: bytes=32 time=27ms TTL=242
Reply from 3.6.0.0: bytes=32 time=15ms TTL=242
Reply from 3.6.0.0: bytes=32 time=14ms TTL=242

Ping statistics for 3.6.0.0:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 27ms, Average = 17ms
 
Last edited:
FROM Command prompt (200mbps plan)
Pinging 3.6.0.0 with 32 bytes of data:
Reply from 3.6.0.0: bytes=32 time=83ms TTL=242
Reply from 3.6.0.0: bytes=32 time=80ms TTL=242
Reply from 3.6.0.0: bytes=32 time=80ms TTL=242
Reply from 3.6.0.0: bytes=32 time=80ms TTL=242

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

NOTE- I am using ethernet
 
@Aarin MH has 10x better ping times possibly because gateways are in Mumbai or Pune, for e.g. via VSNL AKA Tata Sky AKA Tata Communications. Can you check ping values with friends/users of another BB provider? Also a trace route will pin point the problem.
 

Back