upstream

[Palm771]

what is the maximum upstream  (dB)myou should accept on the hub 5?

[Cardiffman282]

About 50.

[Client62]

35-49 dBmV might be seen as a typical range. 

If you are seeing 50 dBmV or much above the Hub is working hard to be heard at the street cabinet, and this may result in upstream channels dropping out - we expect to see 4 to 6 DOCSIS 3.0 channels connected at  QAM 64.

For RFoG connections there is no DOCSIS 3.1 upstream channel, but for CATV / Coax connections there is usually a single DOCSIS 3.1 channel ( as well a the 4 to 6 DOCSIS 3.0 channels ) connected.

[Palm771]

I have two attenuators one at the virgin box outside and one on the hub just to bring my specs in range.

But it is causing me alot of lagg in games. is this because I have to have two attenuators?

[Client62]

The attenuators are used to correct the signal levels so the Hub operates in a preferred range.
It does not add Latency to your connection.

Lag in games is most commonly a problem of using home Wi-Fi especially if extra Wi-Fi Repeater hops are involved,
connections to games servers that are half a world away and game server overload.

[jpeg1]

What has the attenuator done to the downstream levels? 

[Palm771]

The two attenuators one on the back of the hub 5, and one outside in the virgin box work together Brought the downstream levels down  to around 7-8, while not increasing the upstream level too much.

upstream is in the 4-5 range max.

[Palm771]

upstream is around 40.1 dB to 45 dB max.

[Palm771]

Before I only had one attenuator, and my services worked fine, but there was an area fault and im guessing they fixed it and now that pushes too much power into my hub  increasing the downstream levels, so the engineer just stick another attenuator on my connection to bring the downstream levels down.

[Palm771]

When I had my services installed last year it was fine and I averaged around 7-8 DB on downstream and average of 38 dB on upstream, then this december My downstream went way up causing alot of issues.

Im guessing the engineer doesn't want to get to the root cause of the issue but just slap another attenuate on to suppress the connection