Previous incidents
Archibus sign-in issues
Resolved 27 September 2024 at 14:05 UTC
This issue is now resolved.
1 previous update
Network, Wi-Fi and VPN issues in various locations
Resolved 13 September 2024 at 09:00 UTC
This issue is now resolved.
2 previous updates
Business Objects (SAMIS) - some users unable to log in
Resolved 16 September 2024 at 08:00 UTC
This issue is now resolved.
2 previous updates
Intermittent VPN performance issues
Resolved 12 September 2024 at 07:00 UTC
This issue is now resolved.
3 previous updates
Issue affecting "Project Mapper" service
Resolved 2 August 2024 at 08:01 UTC
This issue is now resolved.
1 previous update
Loss of network in 8West Level 1
Resolved 31 July 2024 at 11:21 UTC
This issue is now resolved.
1 previous update
Issue affecting Microsoft Azure services
Resolved 31 July 2024 at 07:05 UTC
This issue is now resolved.
2 previous updates
M365 license issues
Resolved 25 July 2024 at 13:19 UTC
This issue is now resolved.
1 previous update
Computers stuck in reboot loop due to software update
Resolved 2 August 2024 at 08:00 UTC
This issue is now resolved.
6 previous updates
Poor/reduced Remote Desktop performance via VPN
Resolved 12 July 2024 at 08:00 UTC
Our technical resolver teams have now implemented a workaround that should improve performance when accessing devices via Remote Desktop (and VPN). You may need to restart both your local and remote devices in order for them to pick up the policy change.
This issue is now resolved.
2 previous updates
Issue affecting people.bath webpages
Resolved 11 July 2024 at 10:00 UTC
This issue is now resolved.
2 previous updates
Cannot open reports in Business Objects
Resolved 9 July 2024 at 09:40 UTC
This issue is now resolved.
1 previous update
Issue affecting "Project Mapper" service
Resolved 4 July 2024 at 14:25 UTC
This issue is now resolved.
1 previous update
CrowdStrike Falcon - high CPU usage on Windows devices
Resolved 1 July 2024 at 09:10 UTC
Users may notice that CrowdStrike Falcon utilises an abnormally high amount of CPU. If you are experiencing this issue, the current recommendation is:
- In the first instance, reboot your device.
- If a reboot doesn't resolve the issue, then this is because the affected device will have not yet received updated detection logic, in which case waiting a short while and rebooting again should resolve the issue.