Update - There have been no further issues with RM Unify since Tuesday afternoon February 6th. RM are continuing to work with Microsoft and to implement a strategy to allow improvements in the handling of WS-Trust authentication requests from O365 to avoid similar issues in future.
Feb 15, 14:04 GMT
Monitoring - RM Unify has been performing normally since WS-Trust was re-enabled on Tuesday afternoon. No further issues have been seen. However, RM are continuing to monitor the service closely.
Feb 8, 11:04 GMT
Update - RM have re-enabled authentication via WS-Trust this afternoon without any noticeable impact to service. Rich clients and Outlook clients should now be able to authenticate successfully without any issues. RM will be continuing to monitor the service closely this afternoon and tomorrow morning and are still investigating the root cause of increased traffic from Microsoft O365 that caused the availability issues today.
Although RM have re-enabled the majority of WS-Trust protocols, the IMAP protocol remains disabled as it has been since December. For more information see http://www.rm.com/blog/2017/december/rm-unify-and-office-365-email-security-imap-protocol.
Feb 6, 16:22 GMT
Update - RM are planning to re-enable authentication through WS-Trust for RM Unify later this afternoon and are aware that there is a risk of further disruption to service while clients re-authenticate. This change has been timed to be later in the school day to mitigate the impact to end-users but also for a time when the backlog of client requests can still be managed. We will continue to monitor the service closely during this period.
Feb 6, 15:02 GMT
Update - RM have temporarily disabled all authentication through WS-Trust protocols in order to restore reliable access to the RM Unify Launch Pad while we continue to investigate the root cause of this morning's issues. The impact of this change will mean that any users using rich-clients or Outlook for O365 that do not already have a long-lived authentication token will fail to authenticate. We aim to restore access later today as soon as we are confident that we have understood and resolved the root causes of this morning's issues.
Feb 6, 12:10 GMT
Update - The performance of RM Unify has improved and users should now able to access the RM Unify Launch Pad and apps although it is possible that some users may need to make several logon attempts until all of the issues clear. The team are continuing to investigate and will continue to monitor the service closely.
Feb 6, 09:30 GMT
Update - The issues affecting RM Unify availability this morning are still under investigation with the highest priority. A further update will be posted within 30 minutes.
Feb 6, 09:29 GMT
Investigating - We are aware of issues for customers accessing RM Unify this morning. This problem is being investigated with the highest priority. A further update will be posted in 30 minutes.
Feb 6, 09:29 GMT
RM Unify   Operational
Microsoft Office 365 Operational
Key Component - Mail   Operational
Key Component - SharePoint   Operational
Key Component - Yammer   Operational
Key Component - OneDrive   Operational
Key Component - Skype for Business   Operational
Google G-Suite for Education Operational
Google Classroom   Operational
Google Drive   Operational
Glow Blogs   Operational
Glow Meet   Operational
Glow Report a Concern   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Feb 18, 2018

No incidents reported today.

Feb 17, 2018

No incidents reported.

Feb 16, 2018

No incidents reported.

Feb 14, 2018

No incidents reported.

Feb 13, 2018
Completed - The scheduled maintenance has been completed.
Feb 13, 17:00 GMT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 13, 16:00 GMT
Scheduled - Essential maintenance to the Glow Blogs platform will take place during this time. Whilst we do not anticipate any downtime, please assume that the service is unavailable until the end of the maintenance window.
Feb 13, 11:44 GMT
Feb 12, 2018

No incidents reported.

Feb 11, 2018

No incidents reported.

Feb 10, 2018

No incidents reported.

Feb 9, 2018

No incidents reported.

Feb 7, 2018

No incidents reported.

Feb 5, 2018

No incidents reported.

Feb 4, 2018

No incidents reported.