Lags and latest site problems

Running Cloudflare Warp and that helps.

I get the same thing but by the time I have set everything up it goes back to being okay and does strongly suggest a network issue.

Just tried a tracert to VHTV and cannot find any issues and the 2nd hop always times out no matter what IP I use.

C:\Users\ukpol>tracert 163.172.62.219

Tracing route to e45.voyeur-house.tv [163.172.62.219]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1

2 * * * Request timed out.

3 9 ms 11 ms 9 ms 89-75-10-161.infra.chello.pl [89.75.10.161]

4 9 ms 8 ms 8 ms pl-waw26b-rc1-ae-14-2163.aorta.net [84.116.252.245]

5 9 ms 7 ms 9 ms pl-waw26b-ri1-ae-24-0.aorta.net [84.116.138.73]

6 11 ms 7 ms 9 ms war-b2-link.telia.net [213.248.75.56]

7 * 28 ms 28 ms ffm-bb1-link.ip.twelve99.net [213.155.134.214]

8 35 ms 35 ms 37 ms prs-bb1-link.ip.twelve99.net [62.115.123.13]

9 37 ms 39 ms * prs-b3-link.ip.twelve99.net [62.115.118.59]

10 39 ms 39 ms 37 ms scaleway-svc084279-ic374352.ip.twelve99-cust.net [213.248.90.71]

11 38 ms 37 ms 38 ms 51.158.8.75

12 39 ms 41 ms 39 ms 51.158.0.45

13 41 ms 40 ms 39 ms e45.voyeur-house.tv [163.172.62.219]

However, in the Internet, Traceroute messages are often blocked by routers in various Autonomous Systems (AS), making Traceroute highly inaccurate in many cases, so it’s only a rough guide.

Yes, support got back to me quickly with and what I take as an “annoyed” reply " We hear you!" In bold as it is in this reply. This is by no means the type of a reply I would expect from a good customer support, And nothing else whatso ever other than to use the ticket # if I put in another ticket regarding the issues I and others are having.

Bulls__t baffles brains eh :rofl:
But as @John78 has said it has worked ok for years now and all of a sudden we are ALL having problems which does tend to suggest a VH network problem methinks, not rocket science is it?
It certainly isn’t a members problem for it to effect so many.
Well Jabs ain’t having problems as he’s special :rofl:

Mine was fine as well.now acting up again. This is definitely a Vhtv issue
And needs to be addressed.or they will lose subscribers.nobody wants
To put up with this. If RLC gos down it’s fix right away.but never any issue there!

i was telling support everything works fine apart from vhtv and i have never had any problems before yet support is saying its my isp thats the issue or the area that i live in what utter bulls__t :joy:

Why do constantly belittle yourself in not understanding basic IT processes? :thinking: :laughing: :laughing:

No it’s not rocket science, but seeing as I very rarely see the issue although I did make a video of it above trying to show and identify the issue, surely it is better to help people in trying to find what the common cause is.

Network streaming is very complex and when there is an issue and when the people behind the streams are asking for help to identify the problem as they cannot see it themselves, by the way nor can I, then why cannot people work together to find a solution as that is the quickest way to do it without throwing snide immature remarks all the time?

I am not defending VHTV, I am stating the obvious as there definitely is an issue on their side but without our help all we are doing is prolonging the problem and not finding the common cause quickly.

@Debugger VHTV Engineer @VHTV_James the main issue that you are going to face here is that a lot of the members (with respect to them) are in their elder years and throwing up a list of instuctions like that is very confusing for them.

Wouldn’t it be better in these situations to write a debugging script and let us run the script and copy the results and post them back as it would save a lot of time and heartache.

i did what they asked me too do not that it helped anyway they still said its my internet thats the problem but it was confusing for me and im not old

Well obveously it isn’t or it can be a contributing factor, but that needs to be fully established, which it isn’t at the moment due to the multitude of reports.

I am sure they are not doing this but to sweep things under the carpet is not best business practice.

I have two thoughts on this whole issue as I’ve received “we can’t duplicate the issue” responses before. 1) As long as they are sitting in the office, hardwired on a priority line to the main server (I’m not an IT guru, so forgive me if the lexicon is wonky), they are not going to duplicate it. They need to be using offsite connections to see the issues we’re having. 2) I simply think their server capacity is just too small… when I access it during off peak hours there seems to be very little issues… once everyone returns, the server takes a dump. So, from a non-IT guy, spend some money on more server capacity lol.

mate ive had this issue for a week and they just got sick of me and are now just duplicating responses they dont have a clue

It’s not server capacity and more like configuration that is the issue and debugging is the only way to do it in many cases and a simply script that users can run on their side spitting out the results would speed up things enormously.

I still say they are not duplicating it because they are hard wired in the office. To duplicate it, they need to get out of the office and access it the way we do… then we are on a level playing field.

Yesterday I went to test the thing myself. I tried three ISPs and two mobile operators. All the same.

The most mind boggling is the inconsistency of transmission. Or wherever there is a deadlock. Two hours lightning fast, then for no reason whatsoever 30 minutes total deadlock, black camera screens, constant ring rotation, the timeline doesn’t load, unwatchable basically.

When you’re on a working camera during that time everything looks ok, but you should never change cameras because then you have to wait for a long time for it to load, sometimes after more than 30 seconds, sometimes after a couple of minutes you give up.

Suddenly, everything works again at the click of a button. In a split second.

In the meantime tested the connection, everything ok, timeouts ok, changed the browser, same thing.

Finally, I contacted my ISP and asked for a remote system reset.

Same thing.

Now this morning at work I have the same problem, except that I’m on a completely different ISP, with a gigabit connection.

The matter has now been going on, at least for me, for a couple of weeks. And I’ve given up. When it doesn’t go I simply switch it off.

Edit:
Now it works again top notch. Wtf?

Where do you go? What device do you use? What internet do you use? etc… etc… Plus, I am almost certain that a lot of them work remotely not centralised. It isn’t so easy and that is why you need to focus on user feedback and help to quickly establish what the problem is and to find a solution that covers all parameters. As I said before, I am not defending them just stating the obvious with a little knowledge of network streaming.

These may be “basic IT processes” to you but to others like me, I am now 52, they are not.
Who is belittling who? :thinking:
Being a smartarse doesn’t motivate anyone to help at all.
I have tried to use the guide you posted but couldn’t make it work.
We are paying through the nose for this service and I refuse to have to jump through hoops because of @VHTV_James 's constant tinkering that fucks things up EVERY time.

It was a joke to a friend, lighten up. :slight_smile: And for that very reason if you read the rest of it I have suggested an option for VHTV to make it easier for people. :slight_smile:

surely its common sense that if everyone is having the same issues its a problem on vhtvs end

same thing happened to me but then i guarantee it wont last

I am all over the internet with no issues except here, currently running the fastest internet available to me. That said, I’ve been in science my whole life (not IT), when you are doing research on a disease, virus, or anatomical anomalies, you HAVE to do your best to replicate the environment in which the problem exists. “Science 101” teaches you that pristine, sterile labs (like their hard wired office) are of no use in these kind of situations… common sense tells you that you have to “get in the field” where you can come as close as possible to recreating the environment in which it exists to see the issue. Once you have seen it first hand, then go back to the office and try to change the configuration, etc. These desk jockeys are pounding away and nothing is getting fixed. But alas, you’re smarter than me so I concede…