Terrible performance Leicester (LE3) - Page 26

philce · 22-03-2011, 22:06

Upstream upgrades should be in place within 5 months now. 100Mb within 6.

Mine was much better when I was on 50Mb, looks like its a different port, my IP didnt change though.

I can see these dates slipping.

---------- Post added at 21:06 ---------- Previous post was at 21:05 ----------

Did you see this Friday? I wasnt home so nothing my end very strange.

Chrysalis · 22-03-2011, 22:20

Friday was a linx issue, tbb dont have much peering outside of linx so it ended up routing via germany on entanet.

---------- Post added at 21:20 ---------- Previous post was at 21:18 ----------

my worst pingtest for weeks back above 10ms now.

philce · 22-03-2011, 22:27

Looks similar.

---------- Post added at 21:27 ---------- Previous post was at 21:26 ----------

Using the server you used

Chrysalis · 26-03-2011, 20:47

when resetting the superhub to firmware defaults it wipes the modem config, this is a way to check docsis1. I did a check and docsis1 is still 5120kbit/sec, so at the moment that has not been bumped to qam16 dispite improvements allowing docsis2 on overlay. I will test again after we get moved to new upload speeds, I checked out of coriousity since it was mentioned the legacy would get an upgrade to qam16 due to work on the noise.

pingtest is now 5ms on a saturday evening.

docsis2 with old upload speeds.

[img]Download Failed (1)[/img]

I suspect if I had a vmng300 I would be down to 2ms or below.

Chrysalis · 30-03-2011, 01:37

Wigan area got the upgrade and not good news, friend of mine there had cable for years the 50mbit tier. His service was generally fine (has moderate jitter but otheriwse ok), then when they uplifted his speed suddenly his downstream speeds are low, upstream is about 70-80% of max, iplayer buffers, jitter shot up. We checked his upstream channel and it is docsis2 qam16 so didnt fall back to qpsk. Simply looks like a balls up with underestimating extra capacity needed. Doesnt bode well for my port which has a history of utilisation issues.

AaronCooper · 30-03-2011, 02:45

[img]Download Failed (1)[/img]

[img]Download Failed (1)[/img]

The spikes on the tbbmeter are from me streaming & downloading. (Criminal minds addict!) LE3 area.

philce · 05-04-2011, 14:07

Modem went offline at 4am this morning, needed a reboot to rectify.

Cant see anything else changed?

Anyone else round here have the same thing happen?

craigj2k12 · 05-04-2011, 14:12

Quote:

Originally Posted by Chrysalis

[/URL]

I suspect if I had a vmng300 I would be down to 2ms or below.

it doesnt make that much of a difference, but a definite lower

Chrysalis · 05-04-2011, 21:00

phil you could have been upgraded to docsis2, as preparation work is going on now but mine didnt have downtime for that change.

philce · 05-04-2011, 21:28

Quote:

Originally Posted by Chrysalis

phil you could have been upgraded to docsis2, as preparation work is going on now but mine didnt have downtime for that change.

Whats the easest way to check (without a factory reset?)

SW is V5.5.2R20 I assume this is stock and not a new version?

Chrysalis · 05-04-2011, 22:13

check the connection page and see what it says for the upstream channel.

philce · 05-04-2011, 22:52

Quote:

Originally Posted by Chrysalis

check the connection page and see what it says for the upstream channel.

Upstream Channels
Lock Status Modulation Channel ID Max Raw Bit Rate Frequency Power
Locked ATDMA 3 20480 Kbits/sec 45800000 Hz 48.2 dBmV

Chrysalis · 05-04-2011, 23:17

you on docsis2 then, whether or not that was the reason I dont know tho, as that may have already been done before your outage.

what does this box say?

Primary Upstream Service Flow

philce · 06-04-2011, 00:03

Quote:

Originally Posted by Chrysalis

you on docsis2 then, whether or not that was the reason I dont know tho, as that may have already been done before your outage.

what does this box say?

Primary Upstream Service Flow

Primary Upstream Service Flow
Upstream(0)
SFID 6899
Max Traffic Rate 1111000 bps
Max Traffic Burst 8160 bytes
Mix Traffic Rate 0 bps
Max Concatenated Burst 8160 bytes
Scheduling Type Best Effort

I suspected a firmware upgrade as the hub crashed completely (no connection possible), but no new firmware.

Chrysalis · 11-04-2011, 12:00

ignition if you reading this I got an update on legacy.

I plugged in the vmng300 ready to activate and it connected to docsis1 as you know it will do when no config.

The upstream channel is still qpsk docsis1, even tho overlay has been updated to docsis2 qam16. So seems legacy here is still probably in a dire state.