-
Amazon Deals - ToS - Like us?
Netflix is not working on Excitel Broadband
- Thread starter a.c
- Start date
- Replies 69
- Views 11,381
D
Deleted member 70865
Internet completely offline now.
Nice.
Nice.
D
Deleted member 70865
Pinging netflix.com [34.253.104.7] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 34.253.104.7:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 34.253.104.7:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
D
Deleted member 70865
Is this normal?
Tracing route to netflix.com [34.249.125.167]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 4 ms 3 ms 103.57.85.1
3 * * * Request timed out.
4 * * 11 ms 103.56.228.1
5 7 ms 2 ms 3 ms 14.141.116.229.static-Delhi.vsnl.net.in [14.141.116.229]
6 27 ms 28 ms 27 ms 172.29.250.33
7 155 ms 155 ms 156 ms ix-ae-2-591.tcore2.l78-london.as6453.net [80.231.131.81]
8 145 ms 145 ms * if-ae-15-2.tcore2.ldn-london.as6453.net [80.231.131.118]
9 156 ms 151 ms 153 ms 80.231.20.82
10 160 ms 155 ms 158 ms 54.239.100.228
11 159 ms 156 ms 157 ms 54.239.101.61
12 * * * Request timed out.
13 170 ms 164 ms 164 ms 54.239.44.146
14 * * * Request timed out.
15 172 ms 169 ms 170 ms 52.93.6.130
16 166 ms 167 ms 167 ms 52.93.101.11
17 * 186 ms 183 ms 52.93.101.26
18 164 ms 166 ms 169 ms 52.93.7.55
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Tracing route to netflix.com [34.249.125.167]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 4 ms 3 ms 103.57.85.1
3 * * * Request timed out.
4 * * 11 ms 103.56.228.1
5 7 ms 2 ms 3 ms 14.141.116.229.static-Delhi.vsnl.net.in [14.141.116.229]
6 27 ms 28 ms 27 ms 172.29.250.33
7 155 ms 155 ms 156 ms ix-ae-2-591.tcore2.l78-london.as6453.net [80.231.131.81]
8 145 ms 145 ms * if-ae-15-2.tcore2.ldn-london.as6453.net [80.231.131.118]
9 156 ms 151 ms 153 ms 80.231.20.82
10 160 ms 155 ms 158 ms 54.239.100.228
11 159 ms 156 ms 157 ms 54.239.101.61
12 * * * Request timed out.
13 170 ms 164 ms 164 ms 54.239.44.146
14 * * * Request timed out.
15 172 ms 169 ms 170 ms 52.93.6.130
16 166 ms 167 ms 167 ms 52.93.101.11
17 * 186 ms 183 ms 52.93.101.26
18 164 ms 166 ms 169 ms 52.93.7.55
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
D
Deleted member 70865
tried it 7-8 times
still the same.
This is what I am looking at right now on the win 10 app and on browser.
still the same.
This is what I am looking at right now on the win 10 app and on browser.
looks like connectivity with local cdn is dead or messed up 
file a complaint on my excitel. though they do not respond within hours.
few days ago i got a call from them regarding issues with imgur. they wanted to use remote viewing to collect route data to see why i was facing issues. but it took them 2 days to respond. so not really the optimal route for this issue
file a complaint on my excitel. though they do not respond within hours.
few days ago i got a call from them regarding issues with imgur. they wanted to use remote viewing to collect route data to see why i was facing issues. but it took them 2 days to respond. so not really the optimal route for this issue
D
Deleted member 70865
lodged a complaint on my excitel portal.
