How much ping and reliability are you getting from Alliance ?

Don't worry, Airtel will soon reach out there. They're expanding their network in Kolkata very aggressively since the last few months. They've recently covered the entire stretch from Chandannagar all the way to Uttarpara. Uttarpara's where I live BTW.

Don't know about now but I've used Hathway before, from 2018 to 2020. My experience was extremely good. I've written an article about them on this forum itself. Then super cyclone Amphan came and snatched Hathway away from me.

Hoping that Airtel comes soon!

@preetam88 @sumantrab99 Airtel recently installed OFC cable near Agarpara Mahajati School, might be airtel fiber connect sodepur agarpara belghoria..

Alliance latency from Bolpur to Kolkata (approx 180 Km) was 6 ms last year. This January, it got increased to 12 ms. Problem started when it went upto 20 ms.

I raised a ticket to get their attention. The TECHNICIAN who called me blamed it on the BTS and started lecturing ME that people take fiber connection for lower latency than a mobile network. When I asked him to do something about it, he logged me out and logged me in but nothing improved. He was like, that's all I can do for you, nothing more. Nowadays, during peak hours, I get speeds less than 10 mbps. You guys are lucky to have some competition in your market.

@preetam88 Here are the ping results from my friend using Alliance in Baghbazar area.

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

Tracing route to ec2-13-233-48-5.ap-south-1.compute.amazonaws.com [13.233.48.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms <1 ms 10.19.133.1
3 89 ms 4 ms 32 ms node-150-107-176-1.alliancebroadband.in [150.107.176.1]
4 15 ms 18 ms 2 ms 192.168.199.57
5 2 ms 2 ms 2 ms 192.168.199.138
6 1 ms 1 ms 2 ms 99.83.64.160
7 2 ms 1 ms <1 ms 150.222.220.116
8 5 ms 9 ms 8 ms 150.222.220.121
9 * * * Request timed out.
10 25 ms 26 ms 27 ms 150.222.243.171
11 * * * Request timed out.
12 29 ms 29 ms 31 ms 52.95.67.76
13 38 ms 32 ms 29 ms 52.95.64.230
14 25 ms 26 ms 25 ms 52.95.64.225
15 25 ms 26 ms 26 ms 52.95.67.21
16 26 ms 27 ms 25 ms 52.95.67.210
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 25 ms 24 ms 25 ms ec2-13-233-48-5.ap-south-1.compute.amazonaws.com [13.233.48.5]

-------------------------------------------------------------------------------------------------------------------------------------------------------

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

Tracing route to ec2-3-6-0-0.ap-south-1.compute.amazonaws.com [3.6.0.0]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms <1 ms 10.19.133.1
3 * 29 ms 100 ms node-150-107-176-1.alliancebroadband.in [150.107.176.1]
4 3 ms 1 ms 1 ms 192.168.199.57
5 2 ms 2 ms 1 ms 192.168.199.138
6 1 ms 1 ms 1 ms 99.83.64.160
7 1 ms 1 ms <1 ms 150.222.220.132
8 1 ms 2 ms 1 ms 150.222.220.143
9 * * * Request timed out.
10 25 ms 26 ms 25 ms 150.222.243.171
11 * * * Request timed out.
12 28 ms 29 ms 29 ms 52.95.67.100
13 30 ms 29 ms 29 ms 52.95.64.248
14 26 ms 26 ms 26 ms 52.95.64.251
15 26 ms 26 ms 27 ms 52.95.67.129
16 26 ms 25 ms 26 ms 52.95.65.139
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 25 ms 26 ms 25 ms ec2-3-6-0-0.ap-south-1.compute.amazonaws.com [3.6.0.0]

-----------------------------------------------------------------------------------------------------------------------------------------------------------

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

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms <1 ms 10.19.133.1
3 55 ms * 55 ms node-150-107-176-1.alliancebroadband.in [150.107.176.1]
4 35 ms 28 ms 28 ms 192.168.199.222
5 28 ms 28 ms 30 ms 72.14.197.2
6 45 ms 45 ms 45 ms 108.170.248.177
7 53 ms 53 ms 53 ms 72.14.237.139
8 51 ms 51 ms 51 ms dns.google [8.8.8.8]

@sumantrab99 That's good to see and surprising as well. There seems to be no loss at all here on Amazon AWS Mumbai server with Alliance whereas I face a minimum 1% loss. I don't know what to say! The Alliance Broadband technical team doesn't seem to acknowledge the issue.

@sumantrab99 Hi, sorry to bother again with this.
I did some tests by directly connecting my laptop with GPON Terminal and these are the ping test results that I got.

Ping statistics for 3.6.0.0:
Packets: Sent = 973, Received = 958, Lost = 15 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 43ms, Average = 26ms


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

Ping statistics for 208.67.222.222:
Packets: Sent = 477, Received = 476, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 57ms, Average = 39ms

I am seeing considerable losses in 3.6.0.0 but none on Google DNS.
Does this mean that Alliance backend routing has some issue with the AWS server?

I can't tell the guys at Alliance Broadband much as they will point out that there are no losses from Google DNS so fault must be with AWS Server.

Alliance connects to AWS via transit (TATA, Airtel/Vodafone) and to Google via IX (DE-CIX).

The problem could either be at the transit provider or between alliance and the transit provider.

Okay got it. Makes sense then as to why some IP addresses are giving losses and some not. But still confused why others are not facing the same issue :/ My troubles with Alliance are never ending 🙂