Is this website accessible from Reliance Jio Mobile? Please check?

  • Thread starter Thread starter eagle2
  • Start date Start date
  • Replies Replies 13
  • Views Views 1,623
Messages
9
Location
India/USA
ISP
Airtel
Hi thanks for mods for approving my registration!

I work for this website Bollywood.com (Network Engineer). We are currently investigating a very low traffic scenario to our website Bollywood.com from India.

It seems the website could be blocked for visitors from India. Can anyone using Jio Mobile, or Jio Fibre connection check connectivity to Bollywood.com please?

Or even connectivity from non Jio mobile services (Airtel, VI, BSNL etc.)

I would really appreciate any feedback, or help from anyone here. Thanks!
 
Likely due to incorrect web server configuration.
Code:
miyuzaki@oreimo-ent:~$ nslookup bollywood.com 10.13.14.10
Server:         10.13.14.10
Address:        10.13.14.10#53

Non-authoritative answer:
Name:   bollywood.com
Address: 54.218.199.113

miyuzaki@oreimo-ent:~$ curl bollywood.com
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>

There is nothing a network engineer could do.
Code:
[[email protected]] > tool/traceroute vrf=usr-v1 Bollywood.com
Columns: ADDRESS, LOSS, SENT, LAST, AVG, BEST, WORST, STD-DEV, STATUS
 #  ADDRESS          LOSS   SENT  LAST     AVG    BEST   WORST  STD-DEV  STATUS
 1  100.68.0.1       0%       18  1ms      1.1    0.9    1.4    0.1
 2  203.192.217.37   0%       18  1.2ms    1.2    1      2      0.3
 3  115.117.107.141  0%       18  2.8ms    2.7    2      3.2    0.3
 4  172.31.244.45    0%       18  30.2ms   20.3   18.1   34.6   4.4
 5  180.87.37.1      11.1%    18  22.4ms   22.5   21.8   24.1   0.5
 6  180.87.37.114    50%      18  238.4ms  238.8  238.4  239.4  0.3      <MPLS:L=45749,E=1>
 7  180.87.15.238    77.8%    18  timeout  243.8  243.5  244    0.2      <MPLS:L=917641,E=1>
 8  180.87.3.128     82.4%    18  timeout  258.4  258.1  258.8  0.3      <MPLS:L=343207,E=1>
 9  180.87.3.131     58.8%    17  258.4ms  258.3  257.8  259.2  0.5      <MPLS:L=327070,E=1>
10  64.86.252.32     82.4%    17  timeout  258.2  258.2  258.2  0        <MPLS:L=252,E=1>
11                   100%     17  timeout
12                   100%     16  timeout
13                   100%     16  timeout
14  54.218.199.113   0%       16  266.7ms  267.3  266.7  267.7  0.3

[[email protected]] > put [:resolve bollywood.com]
54.218.199.113
 
Last edited:
So you confirm the traffic is unreachable? It seems to be this way. It seems that hop where it's timing out is owned by Tata Communications.

Your cmd output seems strange. It can curl the website. But not traceroute. What does this mean? Can you visit the website using your browser from your location or Ping the website from cmd prompt?
 
Last edited:
It opens fine on Airtel but slow. A lot of it seems like poor optimisation at the developer's end esp. big images, unminified CSS, etc. Also, I noticed you are redirecting from the non-www version to the www version of the site. Most people now type the site name without www which means almost everyone would be redirected.

The redirect should be the other way around i.e. the www version should be redirected to the non-www version.
 


$ ping www.bollywood.com

Pinging wp1725.host.pressdns.com [54.218.199.113] with 32 bytes of data:
Reply from 54.218.199.113: bytes=32 time=283ms TTL=55
Reply from 54.218.199.113: bytes=32 time=284ms TTL=55
Reply from 54.218.199.113: bytes=32 time=282ms TTL=55
Reply from 54.218.199.113: bytes=32 time=283ms TTL=55

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

$ tracert www.bollywood.com

Tracing route to wp1725.host.pressdns.com [54.218.199.113]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.31.1
2 1 ms <1 ms <1 ms 192.168.1.1
3 3 ms 9 ms 5 ms 223.182.79.255
4 8 ms 2 ms 3 ms nsg-corporate-5.30.187.122.airtel.in [122.187.30.5]
5 259 ms 256 ms 256 ms 116.119.57.43
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 282 ms 283 ms 284 ms ec2-54-218-199-113.us-west-2.compute.amazonaws.com [54.218.199.113]

I see you are not using Cloudflare to serve the site.
 

Back