I bet if you do a tracert on that, you will find alot more hops with your's compared to your neighbor's.
I also bet that if you setup your own server host and direct traffic to there and then from there to iptv server (and vise a versa), then it would work.
I am pretty sure that this issue is how your traffic is handled by your ISP, the URL is not being resolved correctly and after much ado it finally sees the URL but looses the packets because of the 'much ado' thing
Just a theory
Go back to your command prompt and ping the server again. Look at the bottom of the results for packet loose information.
By the way, tracert is done same way thru that command prompt as is the ping option is performed.
Just type 'tracert' instead of 'ping'
I must not forget, we must not forget, that we are human beings.
- Ren
Thank's crazed 7.2
I found these results:
The last one (number 9) takes a long time to appear the address (more than 2 seconds)
C:\Users\tracert s1.iptv66.tv
Rastreando a rota para s1.iptv66.tv [104.24.1.119]
com no máximo 30 saltos:
1 5 ms 2 ms 2 ms 192.168.1.1 [192.168.1.1]
2 7 ms 6 ms 8 ms 175.251.40.189.isp.timbrasil.com.br [x]
3 9 ms 10 ms 10 ms 10.216.250.69 [x]
4 12 ms 38 ms 13 ms 10.216.250.21 [x]
5 14 ms 14 ms 13 ms 10.223.238.77 [x]
6 7 ms 7 ms 7 ms et2-0-0.sanpaolo8.spa.seabone.net [x]
7 118 ms 118 ms 119 ms et1-1-0.miami19.mia.seabone.net [x]
8 124 ms 119 ms 119 ms cloudflare.miami19.mia.seabone.net [x]
9 118 ms 120 ms 118 ms 104.24.1.119
Rastreamento concluĂ*do.
Below my neighbor ISP
C:\Users\milto>tracert s1.iptv66.tv
Rastreando a rota para s1.iptv66.tv [104.24.2.119]
com no máximo 30 saltos:
1 1 ms 1 ms 1 ms 192.168.0.1
2 10 ms 10 ms 10 ms 10.28.xxx.x
3 9 ms 11 ms 9 ms c9062241.virtua.com.br [x]
4 10 ms 9 ms 11 ms c90628c9.virtua.com.br [x]
5 9 ms 11 ms 11 ms c90628d1.virtua.com.br [x]
6 13 ms 12 ms 10 ms c9062a0e.virtua.com.br [x]
7 12 ms 11 ms 14 ms c9062a0d.virtua.com.br [x]
8 11 ms 12 ms 10 ms embratel-T0-4-0-1-uacc03.spomb.embratel.net.br [x]
9 16 ms 14 ms 16 ms ebt-H0-15-0-0-tcore01.spolp.embratel.net.br [x]
10 17 ms 19 ms 18 ms ebt-B1171-tcore01.spoph.embratel.net.br [x]
11 12 ms 11 ms 11 ms ebt-H0-5-0-0-puacc03.spo.embratel.net.br [x]
12 13 ms 15 ms 17 ms peer-B53-1702-puacc03.spo.embratel.net.br [x]
13 16 ms 12 ms 11 ms 104.24.2.119
Rastreamento concluĂ*do.
maybe you need a new router? you don't have an extra one laying around do you?
the more i think about it the more i think it's the router hardware.
Last edited by Sandiver; 06-25-2018 at 12:25 PM.
Hi Sandiver, thank's for your suggestion.
My router is a modem/router that belongs to the ISP provider, however I also use another router connected by cable to a router in the TV room.
I understand your point, but as I have internet access and other free IPTV works as well Amazon Prime I don't have a strong argument with my ISP to request replace the modem/router.
Here is a couple of Links to some info on setting up IPTV and Routers and wifi optimization etc.
Worth a look for possible solutions!
https://www.iptvinsider.com/improve-wifi-streaming/
and
ftp://files.dlink.com.au/products/DS...m_for_IPTV.pdf
You will probably need the password for the router.
/kens
/kens
Just FYI...
Feeds from sites such as Amazon Prime, YouTube, etc., are not using the same .ts Transport Protocol.
The protocol used is more like a file download and can therefore handle occasional data stream latency.
The program you are watching will load fully in the background, whereas the .ts does not have this kind of large buffer capacity.
The TV channel you are accessing is not stored on the Server, like YT or AP. It is sent out to a queue of users as addressed packets of data. If your ISP has a 250ms latency on 1 of the hops, well, too late... you have another packet or 2 addressed to you in the pipe.
This format includes a synchronizing clock for the smooth decoding of Video and synchronizing to audio portions of the feed data.
If the Next packet of data to be decoded is late, to the point of not keeping up with the Clock, you will have a glitch and the process then dumps their buffers, gathers the next few packets and starts the decoding process again.
Now, depending on the speed of your processors, you can build up a playout buffer in your equipment of decoded and processed Video/Audio/Metadata info.
HD has almost twice as much processing requirement as SD so this would relate to your Equipment capability to keep up.
...Oops!! Sorry, i'm rambling.
I'll stop now!
/kens