Orange Infocom: Review

  • Thread starter fairusagepfft
  • Start date
  • Replies: Replies 3
  • Views: Views 9,718
fairusagepfft

fairusagepfft

Messages
170
Location
NA
ISP
Reliance, Tikona, BSNL
I was looking to replace my Tikona connection that I had been using for almost a year, with exponentially increasing frustration. I looked into Airtel 4G, but it was too costly, and wireless. I looked into Reliance, and I got a Reliance 3 connection which turned out to be a steaming pile of poo.

Then I decided to not opt for wireless connections again. I contacted Reliance about their wired connectivity, after reading good reviews of their service here. Too bad(which is what I thought at that time, but now I am very grateful to Reliance for not providing their services in my area), it wasn't available in my locality. Tata, well, I couldn't get them to give me a call back even after requesting one weekly for literally 4 months. Plus last time I checked(2-3 years ago), they weren't available where I live.

Then I came across a local ISP in my city(Nagpur) which was providing fiber connectivity with good speeds, and they were available in my area.

Well, to begin with, they have hopeless customer service. They have two landline numbers for their office, one of which is engaged 24x7, and the other is engaged sometimes, and at other times, it will ring till the end with no response. Sometimes, both of these incidents happen within the course of minutes.

Then come the field agents. No such thing as courtesy in their dictionary. Their agent first promised to come to my home on Monday, 11th May, at 11:30 AM. He didn't come, and he didn't let me know he wouldn't come. I called him a dozen times throughout the course of the day, and he wouldn't pick up the phone. He finally showed up on Saturday, 16th May. 5 days late!!!

I purchased the connection on Thursday, 21st May, and he promised to have it up and running by Monday, or at most within a week. On Monday, nothing happened, but he told me that he won't be able to make it and that he'll have my connection up within the week. This happened on me calling him, so no courtesy still. He later promised to have it up and running on Thurday, 28th May, by 7PM. Well, he didn't come, and he didn't pick up any of my calls. Same story on Friday, 29th May.

He finally came on Saturday, 30th May(Today), and I've got the connection up and running for about 30 minutes now. I know this timeframe is absolutely too little to judge the connection quality, so I will update this review once I have more experience with the connection.

Their customer support reps are misinformed too. They first told me that my connection would be symmetrical, but their field agent told me that I would get at most a third of my download speed as the upload speed. Paint my angry.

I had the option of going with either fiber or copper, but since the connection is terminated within ~20 meters of my home(at the house next door), I went with copper.

They are one of the only ISPs I have tried which doesn't block anything. All websites, torrents, everything works. Tikona, Reliance(especially Reliance), BSNL, Tata, all the ISPS I have ever used block at least some websites, or utilize traffic shaping. Not Orange.

Well, without further ado, let's get to the tests.

4396541956.png

4396544239.png

Well, the download speeds are pretty good, but I am disappoint(ed) with the upload speeds.
I tried streaming 1080p YouTube videos, and I had absolutely no buffering visible(yet).
There are downloads running in the background, so the ping might be higher because of that(I guess, not sure about this), but here is the pingtest.



I am not very knowledgeable about traceroutes(maybe someone here can tell me if they look good), but here they are anyway. (There were downloads running in the background which weren't in my control, so I'll add more tests later)

traceroute to google.com (216.58.220.46), 64 hops max, 52 byte packets​
1 192.168.21.1 (192.168.21.1) 1.809 ms 1.282 ms 1.248 ms​
2 183.177.125.1 (183.177.125.1) 4.915 ms 2.206 ms 3.155 ms​
3 183.177.124.9 (183.177.124.9) 3.469 ms 5.092 ms 4.351 ms​
4 115.113.145.177.static-pune.vsnl.net.in (115.113.145.177) 5.090 ms 6.201 ms 7.583 ms​
5 172.31.19.245 (172.31.19.245) 32.105 ms 39.704 ms 45.685 ms​
6 * * *​
7 115.114.142.137.static-chennai.vsnl.net.in (115.114.142.137) 916.691 ms 696.968 ms 122.011 ms​
8 121.240.1.50 (121.240.1.50) 57.323 ms 62.032 ms 64.569 ms​
9 72.14.233.204 (72.14.233.204) 60.844 ms 70.977 ms 66.716 ms​
10 209.85.255.43 (209.85.255.43) 73.777 ms 84.493 ms 83.923 ms​
11 maa03s18-in-f14.1e100.net (216.58.220.46) 91.622 ms 98.311 ms 96.448 ms​

traceroute to broadbandforum.co (173.236.194.106), 64 hops max, 52 byte packets​
1 192.168.21.1 (192.168.21.1) 1.829 ms 1.101 ms 1.232 ms​
2 183.177.125.1 (183.177.125.1) 3.956 ms 2.829 ms 3.081 ms​
3 183.177.124.9 (183.177.124.9) 3.688 ms 3.827 ms 3.623 ms​
4 115.113.145.177.static-pune.vsnl.net.in (115.113.145.177) 8.122 ms 7.471 ms 6.754 ms​
5 ix-0-100.tcore1.mlv-mumbai.as6453.net (180.87.38.5) 24.117 ms 21.865 ms 21.526 ms​
6 * * *​
7 if-8-1600.tcore1.pye-paris.as6453.net (80.231.217.6) 150.013 ms 148.666 ms 148.828 ms​
8 if-2-2.tcore1.pvu-paris.as6453.net (80.231.154.17) 148.660 ms 151.121 ms 150.045 ms​
9 xe-0-1-0.mpr1.cdg11.fr.zip.zayo.com (64.125.14.57) 170.457 ms 141.028 ms 137.018 ms​
10 ae1.cr1.dca2.us.zip.zayo.com (64.125.32.69) 233.813 ms 294.759 ms 306.716 ms​
11 ae6.er1.iad10.us.zip.zayo.com (64.125.20.118) 307.771 ms 308.659 ms 307.251 ms​
12 ae9.er5.iad10.us.zip.zayo.com (64.125.31.142) 306.848 ms 483.446 ms 486.096 ms​
13 208.185.23.134.t00867-03.above.net (208.185.23.134) 490.502 ms 697.126 ms 699.751 ms​
14 ip-208-113-156-4.dreamhost.com (208.113.156.4) 225.504 ms 306.135 ms 307.273 ms​
15 ip-208-113-156-75.dreamhost.com (208.113.156.75) 310.008 ms​
ip-208-113-156-73.dreamhost.com (208.113.156.73) 329.522 ms​
ip-208-113-156-75.dreamhost.com (208.113.156.75) 306.605 ms​
16 ps380171.dreamhost.com (173.236.194.106) 305.738 ms 266.674 ms 251.092 ms​
If there are any more tests I should run, please let me know.

Here is their peering info:

iSemejT.png


I am paying 2800 INR for a 10mbit connection with 100GB FUP limit. The connection is prepaid, and there is no speed downgrade or anything. Once I've used 100GB, the connection will stop working.

They provide day-by-day usage information, like most other wired ISPs.

0p5jLvj.png

They also have this speed graph which doesn't seem to have populated yet:

YaXAbr0.png


So far, I'd say the connection seems pretty good, and the customer support seems pretty horrible. Again, this is a local ISP which provides services only in Nagpur, and I'd say a rough estimate is that they provide services in 60% of Nagpur(they are in a lot of areas other wired ISPs don't provide services in).

I'll keep updating this review as time goes on.

EDIT:

Update 1:

A bit more realistic of a speed test:

QPONhy2.png


Update 2(14/06/15 - 15 days):

So far, the connection has been superb. I've faced minor hiccups a couple times, like my connection going down at 10PM in the night when there was very heavy rainfall, but the issue was fixed promptly before I was awake the next day. The place where the connection is terminated doesn't have power backup, and whenever there is a power failure(quite often these days), authentication fails for a couple minutes, which I guess means that their system might be booting up. I also faced speed issues at one point, which was accompanied by frequent disconnection, and a single phone call solved the problem within 10 minutes. Again, all of these were very minor hiccups, especially so compared to my experience with Reliance, Tikona, and BSNL. I've been able to reach 1.32MB/s download(using IDM) on the connection, which is 10.56Mb/s, about .5 Megabits more than the promised speed, and I have never seen an ISP over deliver before.

Some speedtests

(This is actually the first time I'm seeing those upload speeds)




Overall, I'm very satisfied with this ISP so far.

Update 3(21/6/15): Stay away from this ISP. Every time it rains, literally every single time, my connection goes down for hours. Its currently been down for a whole day, and their agents and their office have switched off their phones. And their phones could be on, the ring would end with no one picking up, and two minutes later, its busy. Call 30 seconds later, same, full ring, no picking up happening. They have absolutely no thing called as customer support. One single phone line which is busy more than half the time you call them. No IVR system, no nothing. At least other ISPs have 24*7 support systems, they have 9 to 5, Monday to Saturday.
 
Last edited by a moderator:
x720

x720

Incoherent Poster
Messages
10,398
Location
Gurgaon | Mumbai
ISP
airtel, BSNL, MTNL
Congrats on the new connection.

Looks good. Though I wonder why your trace is going to Chennai for Google.

Ping 8.8.8.8 and see what you get. Also, ping bbc.co.uk
 
fairusagepfft

fairusagepfft

Messages
170
Location
NA
ISP
Reliance, Tikona, BSNL
Thanks, it seems to be performing pretty well so far.

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.21.1 (192.168.21.1) 42.847 ms 1.319 ms 1.090 ms
2 183.177.125.1 (183.177.125.1) 1.763 ms 2.623 ms 121.986 ms
3 183.177.124.9 (183.177.124.9) 2.703 ms 2.253 ms 1.836 ms
4 115.113.145.177.static-pune.vsnl.net.in (115.113.145.177) 3.664 ms 4.596 ms 3.759 ms
5 115.113.165.98.static-mumbai.vsnl.net.in (115.113.165.98) 42.604 ms 41.891 ms 42.370 ms
6 64.233.174.106 (64.233.174.106) 39.466 ms
209.85.245.167 (209.85.245.167) 44.172 ms
64.233.174.106 (64.233.174.106) 38.722 ms
7 google-public-dns-a.google.com (8.8.8.8) 29.517 ms 25.831 ms 29.370 ms​

traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.246.104
traceroute to bbc.co.uk (212.58.246.104), 64 hops max, 52 byte packets
1 192.168.21.1 (192.168.21.1) 1.418 ms 1.156 ms 1.076 ms
2 183.177.125.1 (183.177.125.1) 2.355 ms 2.136 ms 4.211 ms
3 183.177.124.9 (183.177.124.9) 2.620 ms 2.335 ms 2.288 ms
4 115.113.145.177.static-pune.vsnl.net.in (115.113.145.177) 3.987 ms 3.414 ms 3.998 ms
5 172.29.250.34 (172.29.250.34) 25.307 ms 24.973 ms 25.344 ms
6 if-2-590.tcore2.l78-london.as6453.net (80.231.131.113) 143.896 ms 144.149 ms 142.081 ms
7 if-2-2.tcore1.l78-london.as6453.net (80.231.131.2) 147.673 ms 148.685 ms 145.260 ms
8 if-17-2.tcore1.ldn-london.as6453.net (80.231.130.130) 142.756 ms 144.713 ms 142.752 ms
9 195.219.83.102 (195.219.83.102) 148.767 ms 147.843 ms 148.749 ms
10 ae-119-3505.edge4.london1.level3.net (4.69.166.1) 145.879 ms
ae-231-3607.edge4.london1.level3.net (4.69.166.25) 157.306 ms
ae-121-3507.edge4.london1.level3.net (4.69.166.9) 145.356 ms
11 ae-229-3605.edge4.london1.level3.net (4.69.166.17) 211.284 ms
ae-120-3506.edge4.london1.level3.net (4.69.166.5) 165.470 ms
ae-119-3505.edge4.london1.level3.net (4.69.166.1) 165.249 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *​

The BBC website works just fine, but the traceroute seems to be having issues.

PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=56 time=28.696 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=29.229 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=29.031 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=29.544 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=29.520 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=29.033 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=56 time=30.001 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=56 time=29.976 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=56 time=156.861 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=56 time=128.299 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=56 time=69.432 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=56 time=28.924 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=56 time=30.084 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=56 time=29.805 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=56 time=29.360 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=56 time=29.647 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=56 time=29.026 ms
^C
--- 8.8.8.8 ping statistics ---
17 packets transmitted, 17 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 28.696/45.086/156.861/37.140 ms​

PING bbc.co.uk (212.58.244.20): 56 data bytes
64 bytes from 212.58.244.20: icmp_seq=0 ttl=51 time=144.366 ms
64 bytes from 212.58.244.20: icmp_seq=1 ttl=51 time=144.608 ms
64 bytes from 212.58.244.20: icmp_seq=2 ttl=51 time=144.975 ms
64 bytes from 212.58.244.20: icmp_seq=3 ttl=51 time=144.804 ms
64 bytes from 212.58.244.20: icmp_seq=4 ttl=51 time=145.166 ms
64 bytes from 212.58.244.20: icmp_seq=5 ttl=51 time=287.979 ms
64 bytes from 212.58.244.20: icmp_seq=6 ttl=51 time=284.423 ms
64 bytes from 212.58.244.20: icmp_seq=7 ttl=51 time=229.382 ms
64 bytes from 212.58.244.20: icmp_seq=8 ttl=51 time=151.795 ms
64 bytes from 212.58.244.20: icmp_seq=9 ttl=51 time=146.408 ms
64 bytes from 212.58.244.20: icmp_seq=10 ttl=51 time=144.633 ms
64 bytes from 212.58.244.20: icmp_seq=11 ttl=51 time=144.387 ms
64 bytes from 212.58.244.20: icmp_seq=12 ttl=51 time=144.367 ms
64 bytes from 212.58.244.20: icmp_seq=13 ttl=51 time=144.566 ms
64 bytes from 212.58.244.20: icmp_seq=14 ttl=51 time=144.680 ms
64 bytes from 212.58.244.20: icmp_seq=15 ttl=51 time=144.637 ms
64 bytes from 212.58.244.20: icmp_seq=16 ttl=51 time=144.818 ms
64 bytes from 212.58.244.20: icmp_seq=17 ttl=51 time=144.265 ms
64 bytes from 212.58.244.20: icmp_seq=18 ttl=51 time=185.517 ms
64 bytes from 212.58.244.20: icmp_seq=19 ttl=51 time=545.339 ms
^C
--- bbc.co.uk ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 144.265/185.556/545.339/93.827 ms​