Rocket Well here's info on PING and Freezing

[Rinny]

3:14pm Pacific Time Best Ping in Weeks!!! What changed The Normal Ping around 270MS NO FREEZING NOW
PING 11.iptvrocket.tv (31.220.2.36): 56 data bytes
64 bytes from 31.220.2.36: icmp_seq=0 ttl=53 time=177.022 ms
64 bytes from 31.220.2.36: icmp_seq=1 ttl=53 time=176.999 ms
64 bytes from 31.220.2.36: icmp_seq=2 ttl=53 time=176.203 ms
64 bytes from 31.220.2.36: icmp_seq=3 ttl=53 time=176.318 ms
64 bytes from 31.220.2.36: icmp_seq=4 ttl=53 time=177.144 ms
64 bytes from 31.220.2.36: icmp_seq=5 ttl=53 time=177.760 ms
64 bytes from 31.220.2.36: icmp_seq=6 ttl=53 time=176.380 ms
64 bytes from 31.220.2.36: icmp_seq=7 ttl=53 time=176.821 ms
64 bytes from 31.220.2.36: icmp_seq=8 ttl=53 time=175.946 ms
64 bytes from 31.220.2.36: icmp_seq=9 ttl=53 time=177.038 ms

--- 11.iptvrocket.tv ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 175.946/176.763/177.760/0.516 ms

 

[Rinny]

3:14pm Pacific Time Best Ping in Weeks!!! What changed The Normal Ping around 270MS NO FREEZING NOW
PING 11.iptvrocket.tv (31.220.2.36): 56 data bytes
64 bytes from 31.220.2.36: icmp_seq=0 ttl=53 time=177.022 ms
64 bytes from 31.220.2.36: icmp_seq=1 ttl=53 time=176.999 ms
64 bytes from 31.220.2.36: icmp_seq=2 ttl=53 time=176.203 ms
64 bytes from 31.220.2.36: icmp_seq=3 ttl=53 time=176.318 ms
64 bytes from 31.220.2.36: icmp_seq=4 ttl=53 time=177.144 ms
64 bytes from 31.220.2.36: icmp_seq=5 ttl=53 time=177.760 ms
64 bytes from 31.220.2.36: icmp_seq=6 ttl=53 time=176.380 ms
64 bytes from 31.220.2.36: icmp_seq=7 ttl=53 time=176.821 ms
64 bytes from 31.220.2.36: icmp_seq=8 ttl=53 time=175.946 ms
64 bytes from 31.220.2.36: icmp_seq=9 ttl=53 time=177.038 ms

--- 11.iptvrocket.tv ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 175.946/176.763/177.760/0.516 ms

3:45pm
PING 11.iptvrocket.tv (31.220.2.36): 56 data bytes
64 bytes from 31.220.2.36: icmp_seq=0 ttl=53 time=269.665 ms
64 bytes from 31.220.2.36: icmp_seq=1 ttl=53 time=273.029 ms
64 bytes from 31.220.2.36: icmp_seq=2 ttl=53 time=270.937 ms
64 bytes from 31.220.2.36: icmp_seq=3 ttl=53 time=272.691 ms
64 bytes from 31.220.2.36: icmp_seq=4 ttl=53 time=271.706 ms
64 bytes from 31.220.2.36: icmp_seq=5 ttl=53 time=263.361 ms
64 bytes from 31.220.2.36: icmp_seq=6 ttl=53 time=268.519 ms
64 bytes from 31.220.2.36: icmp_seq=7 ttl=53 time=263.902 ms
64 bytes from 31.220.2.36: icmp_seq=8 ttl=53 time=262.286 ms
64 bytes from 31.220.2.36: icmp_seq=9 ttl=53 time=271.756 ms

--- 11.iptvrocket.tv ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 262.286/268.785/273.029/3.894 ms

 

[tuxen]

Pinging 11.iptvrocket.tv [31.220.2.36] with 64 bytes of data:

Reply from 31.220.2.36: bytes=64 time=21ms TTL=60
Reply from 31.220.2.36: bytes=64 time=18ms TTL=60
Reply from 31.220.2.36: bytes=64 time=19ms TTL=60
Reply from 31.220.2.36: bytes=64 time=19ms TTL=60
Reply from 31.220.2.36: bytes=64 time=18ms TTL=60
Reply from 31.220.2.36: bytes=64 time=19ms TTL=60
Reply from 31.220.2.36: bytes=64 time=18ms TTL=60
Reply from 31.220.2.36: bytes=64 time=20ms TTL=60
Reply from 31.220.2.36: bytes=64 time=19ms TTL=60
Reply from 31.220.2.36: bytes=64 time=18ms TTL=60

Ping statistics for 31.220.2.36:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 21ms, Average = 18ms

(; just teasing. it isen't what matters most. you in us or eu?

 

[built2last]

Pinging 11.iptvrocket.tv [31.220.2.36] with 32 bytes of data:
Reply from 31.220.2.36: bytes=32 time=111ms TTL=53
Reply from 31.220.2.36: bytes=32 time=108ms TTL=53
Reply from 31.220.2.36: bytes=32 time=110ms TTL=53
Reply from 31.220.2.36: bytes=32 time=114ms TTL=53

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


im in pennsylvania on comcast 150 mb connection rockin the iptv with no buffering at all

 

[tuxen]

Scandinavia 100mb fiber.

and to iks66, not that it matters they are probably meters apart. heh

Pinging 66.iptv66.tv [31.220.2.42] with 64 bytes of data:
Reply from 31.220.2.42: bytes=64 time=18ms TTL=60
Reply from 31.220.2.42: bytes=64 time=18ms TTL=60
Reply from 31.220.2.42: bytes=64 time=20ms TTL=60
Reply from 31.220.2.42: bytes=64 time=19ms TTL=60
Reply from 31.220.2.42: bytes=64 time=21ms TTL=60
Reply from 31.220.2.42: bytes=64 time=19ms TTL=60
Reply from 31.220.2.42: bytes=64 time=19ms TTL=60
Reply from 31.220.2.42: bytes=64 time=19ms TTL=60
Reply from 31.220.2.42: bytes=64 time=19ms TTL=60
Reply from 31.220.2.42: bytes=64 time=21ms TTL=60

Ping statistics for 31.220.2.42:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 21ms, Average = 19ms

 

[Rinny]

wow that's unreal!!! Fast!!

Freezing started here now!!

PING 11.iptvrocket.tv (31.220.2.36): 56 data bytes
64 bytes from 31.220.2.36: icmp_seq=0 ttl=53 time=283.456 ms
64 bytes from 31.220.2.36: icmp_seq=1 ttl=53 time=270.465 ms
64 bytes from 31.220.2.36: icmp_seq=2 ttl=53 time=272.984 ms
64 bytes from 31.220.2.36: icmp_seq=3 ttl=53 time=272.685 ms
64 bytes from 31.220.2.36: icmp_seq=4 ttl=53 time=273.381 ms
64 bytes from 31.220.2.36: icmp_seq=5 ttl=53 time=272.802 ms
64 bytes from 31.220.2.36: icmp_seq=6 ttl=53 time=273.627 ms
64 bytes from 31.220.2.36: icmp_seq=7 ttl=53 time=272.876 ms
64 bytes from 31.220.2.36: icmp_seq=8 ttl=53 time=271.800 ms
64 bytes from 31.220.2.36: icmp_seq=9 ttl=53 time=269.097 ms

--- 11.iptvrocket.tv ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 269.097/273.317/283.456/3.635 ms

 

[Rinny]

Out West. Pacific....

 

[sat-junkie]

east coast 8 40 pm


Pinging 66.iptv66.tv [31.220.2.42] with 32 bytes of data:
Reply from 31.220.2.42: bytes=32 time=110ms TTL=58
Reply from 31.220.2.42: bytes=32 time=111ms TTL=58
Reply from 31.220.2.42: bytes=32 time=114ms TTL=58
Reply from 31.220.2.42: bytes=32 time=111ms TTL=58

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

 

[Rinny]

Wish i tried a PING back when it was running Sweet! So i had a Base line...Grrrr Wondering now how to speed up the ping??

 

[chad1976]

Nice bro Rocket still won,t be ready for at lease 2 more months

 

[TheRizzo]

I'm pinging rocket and 66 at 185-190ms at 9:07 EST.

 

[bluraystock]

Nice bro Rocket still won,t be ready for at lease 2 more months

what's happening?

 

[Rinny]

Chad1976 what do you know about this?

Out West Freezing now!! Or Buffering!!

A little info would be sweet..
Am A Rocket Believer Trust ME!!

 

[Rinny]

11:46PM Out WEST And Running MINT!! PICTURE Unreal!! Yes some channels down But freeze Free!!
Ping 11.iptvrocket.tv (31.220.2.36): 56 data bytes
64 bytes from 31.220.2.36: icmp_seq=0 ttl=53 time=267.799 ms
64 bytes from 31.220.2.36: icmp_seq=1 ttl=53 time=273.258 ms
64 bytes from 31.220.2.36: icmp_seq=2 ttl=53 time=267.835 ms
64 bytes from 31.220.2.36: icmp_seq=3 ttl=53 time=273.477 ms
64 bytes from 31.220.2.36: icmp_seq=4 ttl=53 time=266.838 ms
64 bytes from 31.220.2.36: icmp_seq=5 ttl=53 time=268.258 ms
64 bytes from 31.220.2.36: icmp_seq=6 ttl=53 time=272.579 ms
64 bytes from 31.220.2.36: icmp_seq=7 ttl=53 time=275.784 ms
64 bytes from 31.220.2.36: icmp_seq=8 ttl=53 time=275.594 ms
64 bytes from 31.220.2.36: icmp_seq=9 ttl=53 time=267.956 ms

--- 11.iptvrocket.tv ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 266.838/270.938/275.784/3.347 ms

 

[milair55]

Well, pinging isn't going to help anyone. Mine pings fine. But. I haven't been able to connect to any channel since yesterday. Even then,
it took about 45 seconds to connect! Even worse, it would just go blank. Seems to me they are trying to fix something that already worked
fine.

 

[Takenover83]

If you ask me Ping does not matter. I could care less how long it takes for me to talk to a server, what matters is the freezing which is not directly related to ping. Thats simply how long it takes for you to start communicating with the server. So it may take someone else 200ms to get a channel to start while it may take someone else 500ms. Not a huge deal. I had plenty of freezing during Monday Night Raw and some of the other non movie channels (less popular). One channel will run great while another channel will have a ton of issue's. Feel free to fully test several channels in different catagories before saying "freeze free".

 

[Alucard]

Ok guys, it does not matter if you are going to iptv66, iptvrocket or iptvprivate server. They are all going to the same ISP in Belize and then forwarded to the same backed servers. All 3 servers are in the same sub-net which indicates that they are all on the same network. The same holds true for the IKS stuff.

 

[Bkman2020]

This service is all around the world you so you may never get the right pings or location thanks.

 

[Nickybhoy]

PING 11.iptvrocket.tv (31.220.2.36) 56(84) bytes of data.
64 bytes from 31.220.2.36: icmp_seq=1 ttl=55 time=39.4 ms
64 bytes from 31.220.2.36: icmp_seq=2 ttl=55 time=37.9 ms
64 bytes from 31.220.2.36: icmp_seq=3 ttl=55 time=36.8 ms
64 bytes from 31.220.2.36: icmp_seq=4 ttl=55 time=34.9 ms
64 bytes from 31.220.2.36: icmp_seq=5 ttl=55 time=32.9 ms
64 bytes from 31.220.2.36: icmp_seq=6 ttl=55 time=42.1 ms
64 bytes from 31.220.2.36: icmp_seq=7 ttl=55 time=40.9 ms
64 bytes from 31.220.2.36: icmp_seq=8 ttl=55 time=39.4 ms
64 bytes from 31.220.2.36: icmp_seq=9 ttl=55 time=38.6 ms
64 bytes from 31.220.2.36: icmp_seq=10 ttl=55 time=36.9 ms
64 bytes from 31.220.2.36: icmp_seq=11 ttl=55 time=35.6 ms
64 bytes from 31.220.2.36: icmp_seq=12 ttl=55 time=43.6 ms
64 bytes from 31.220.2.36: icmp_seq=13 ttl=55 time=41.8 ms
64 bytes from 31.220.2.36: icmp_seq=14 ttl=55 time=39.9 ms
64 bytes from 31.220.2.36: icmp_seq=15 ttl=55 time=37.9 ms
64 bytes from 31.220.2.36: icmp_seq=16 ttl=55 time=46.4 ms
64 bytes from 31.220.2.36: icmp_seq=17 ttl=55 time=35.3 ms
64 bytes from 31.220.2.36: icmp_seq=18 ttl=55 time=33.9 ms
64 bytes from 31.220.2.36: icmp_seq=19 ttl=55 time=42.1 ms
64 bytes from 31.220.2.36: icmp_seq=20 ttl=55 time=40.9 ms
64 bytes from 31.220.2.36: icmp_seq=21 ttl=55 time=38.8 ms
64 bytes from 31.220.2.36: icmp_seq=22 ttl=55 time=37.6 ms
64 bytes from 31.220.2.36: icmp_seq=23 ttl=55 time=35.9 ms
64 bytes from 31.220.2.36: icmp_seq=24 ttl=55 time=34.9 ms
64 bytes from 31.220.2.36: icmp_seq=25 ttl=55 time=39.6 ms
64 bytes from 31.220.2.36: icmp_seq=26 ttl=55 time=40.9 ms
^C
--- 11.iptvrocket.tv ping statistics ---
26 packets transmitted, 26 received, 0% packet loss, time 25037ms
rtt min/avg/max/mdev = 32.939/38.698/46.406/3.158 ms




From the UK on 75mb broadband running Kodi 15.1 on linux. Ping wont matter as much as how much bandwidth you have to "take data down the line".

More bandwidth = more data down the line in quicker time and less chance of frames to be skipped.

Enjoying this service for the last month with a couple freezing laggy issues but its a cracking service, and its getting better

Anyone on the site know if BT Sport Europe will be added to the sports channels?

Cheers guys

 

[jjjackson]

You can only take as fast as they send it.