JioFiber performance for gaming in Kolkata

[sumantrab99]

Don't worry, I'll check them tomorrow (technically today) and get back to you.

 

[bridgekids88]

Thank you
Looking forward to it.

 

[sumantrab99]

No need to thank me. This is what this great forum is for.

 

[Netmagic]

@sumantrab99 I am from Agarpara, if you want any specific ping and trace route result from jio fiber. I will share with you.

 

[sumantrab99]

Sure.
These are the few IP addresses that I usually do tests on.

13.233.48.5
3.6.70.89 (might not respond to pingtests now)
3.6.0.0
8.8.8.8

Would be great if you can check them on Alliance and JioFiber as well. I usually see loses when I run them 200-300 responses.

Thanks in advance

@Netmagic these are the IPs that you can use.

 

[sumantrab99]

@preetam88 Just got them Jio ping results back. Location: Sodepur. Here you go:

13.233.48.5 Ping (AWS Mumbai):

13.233.48.5 Traceroute (AWS Mumbai):

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

3.6.0.0 Ping (AWS Mumbai):

3.6.0.0 Traceroute (AWS Mumbai):

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

8.8.8.8 Ping:

8.8.8.8 Traceroute:

 

[Netmagic]

@Netmagic these are the IPs that you can use.

okay

 

[Netmagic]

@sumantrab99

3.6.0.0

Pinging 3.6.0.0 with 32 bytes of data:
Reply from 3.6.0.0: bytes=32 time=43ms TTL=235
Reply from 3.6.0.0: bytes=32 time=43ms TTL=235
Reply from 3.6.0.0: bytes=32 time=42ms TTL=235
Reply from 3.6.0.0: bytes=32 time=42ms TTL=235

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

---------------------------------------------------------------------------------
13.233.48.5

Pinging 13.233.48.5 with 32 bytes of data:
Reply from 13.233.48.5: bytes=32 time=51ms TTL=235
Reply from 13.233.48.5: bytes=32 time=51ms TTL=235
Reply from 13.233.48.5: bytes=32 time=51ms TTL=235
Reply from 13.233.48.5: bytes=32 time=53ms TTL=235

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

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


traceroute 13.233.48.5

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 reliance.reliance [192.168.29.1]
2 2 ms 2 ms 2 ms 10.25.200.1
3 2 ms 2 ms 2 ms 172.16.19.1
4 2 ms 2 ms 2 ms 192.168.105.52
5 2 ms 2 ms 2 ms 172.26.110.149
6 3 ms 3 ms 2 ms 172.26.110.162
7 2 ms 2 ms 2 ms 192.168.37.23
8 3 ms 2 ms 3 ms 192.168.37.24
9 44 ms 43 ms 43 ms 172.16.18.33
10 31 ms 31 ms 30 ms 172.16.19.2
11 35 ms 35 ms 35 ms 172.16.0.82
12 35 ms 36 ms 35 ms 172.16.0.36
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 61 ms 61 ms 61 ms 52.95.66.78
18 58 ms 58 ms 58 ms 52.95.64.178
19 52 ms 52 ms 55 ms 52.95.64.185
20 56 ms 54 ms 87 ms 52.95.66.153
21 53 ms 52 ms 52 ms 52.95.67.208
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 59 ms 59 ms 58 ms ec2-13-233-48-5.ap-south-1.compute.amazonaws.com [13.233.48.5]

 

[Netmagic]

@sumantrab99


8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=44ms TTL=111
Reply from 8.8.8.8: bytes=32 time=44ms TTL=111
Reply from 8.8.8.8: bytes=32 time=44ms TTL=111
Reply from 8.8.8.8: bytes=32 time=44ms TTL=111

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



------------------------------------------------------------
8.8.8.8 traceroute

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

1 <1 ms <1 ms <1 ms reliance.reliance [192.168.29.1]
2 2 ms 1 ms 1 ms 10.25.200.1
3 2 ms 2 ms 2 ms 172.16.19.1
4 3 ms 3 ms 2 ms 192.168.105.46
5 2 ms 2 ms 2 ms 172.26.110.149
6 2 ms 2 ms 2 ms 172.26.110.162
7 2 ms 2 ms 2 ms 192.168.37.19
8 3 ms 2 ms 2 ms 192.168.37.20
9 28 ms 28 ms 28 ms 172.26.14.73
10 29 ms 29 ms 30 ms 172.16.19.2
11 35 ms 35 ms 35 ms 172.16.0.82
12 35 ms 35 ms 35 ms 172.16.0.36
13 37 ms 37 ms 37 ms 172.253.67.101
14 44 ms 44 ms 44 ms dns.google [8.8.8.8]

 

[bridgekids88]

@sumantrab99 Thank you for this. As expected, the response time for the AWS Mumbai server is a bit higher than Alliance. But good to see no issue with packet losses.