Good morning,
We have received several reports of internet sessions dropping out. RM are actively dealing with this.
Thanks,
Kevin Crawley
Sep 08 2022
Good morning,
We have received several reports of internet sessions dropping out. RM are actively dealing with this.
Thanks,
Kevin Crawley
Apr 21 2022
Following on from last night’s firewall upgrade, there are unfortunately some issues. There are some schools who have reported issues with their VOIP/SIP deployments and some Google services are also not working as expected. RM senior engineers are investigating.
Thanks,
Kevin Crawley
Nov 03 2021
We believe this has now been resolved. It looks like there were two simultaneous issues;
If there are any further queries, please contact the HfL Broadband Team.
Nov 03 2021
Good morning.
We have received multiple reports of slow internet this morning. RM are investigating. Apologies for the disruption.
Thanks,
Kevin Crawley
Oct 19 2021
Yesterday afternoon (18th October) we received some reports of slow internet.
RM suspect that there was a Google update released which resulted in higher than usual volumes of traffic – and this in turn would cause a slow internet experience. Typically, the RM transit (for Google) utilises at a maximum of 8Gbps, but yesterday it went over 10Gbps.
In fact there were three instances yesterday where the transit bandwidth utilisation exceeded the capacity, timescales for which are updated below.
8.48-9.08
11.25-11.40
13.55-14.03
RM is closely monitoring the situation.
Oct 07 2021
When using Chromebooks, you may experience issues accessing websites that use websockets. In these instances, the browser on the Chromebook attempts to go out to the internet using the SOCKS protocol entry from the proxy settings.
Normally sessions go out to the internet using the top 3 protocols (HTTP and HTTPS especially). Other devices (Windows etc) have the SOCKS protocol blank so it will send the session to the internet via HTTP/HTTPS instead. On Chromebooks if you’ve set a proxy (wf1.thegrid.org.uk etc) via G-Suite it ticks it for all protocols (including SOCKS). However, RM do not support the SOCKS protocol and this makes the outbound connection fail.
There are some high profile websites that use websockets such as SCOMIS, Spotify, and LiveStorm. It may also cause issues when using the remote desktop web client into a LARA server.
There are a couple of fixes!
Option 1) remove the entry from the SOCKS protocol, and leave it blank.
Option 2) schools connect the Chromebooks to a transparent proxy network (typically a 10.* range), instead of the proxied network (172.* range)
If you have any queries, please get in touch with our Service Desk. Thanks