Affected Components:

Aug 24, 08:13:46 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour

Affected Components:

Aug 19, 18:00:00 GMT+0
Completed - Maintenance has completed successfully.

Aug 19, 17:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 17, 16:00:20 GMT+0
Identified - We are planning for scheduled maintenance during this time. Access will be unavailable and notification of availability will be posted as a notification on completion of the maintenance window..

Duration: 2 hours and 14 minutes

Affected Components:

May 19, 10:24:35 GMT+0
Resolved - This incident has been resolved. The issue has been resolved everything is working as normal..

May 19, 10:21:13 GMT+0
Identified - We are continuing to work on a fix for this incident. Further testing is ongoing..

May 19, 09:14:35 GMT+0
Identified - We are continuing to work on a fix for this incident..

May 19, 09:04:56 GMT+0
Investigating - We are still investigating this incident. Repudiation letters are currently not being sent out..

May 19, 08:10:22 GMT+0
Investigating - We are currently investigating this incident..

Duration: 15 hours and 32 minutes

Affected Components: , , , , , , , , , , , , , , ,

Oct 30, 07:32:23 GMT+0
Resolved - There was a major Microsoft outage last night which affected businesses across the globe and was widely reported in the news. This outage also affected us, and all HF Digital services, including ELI, were impacted. The issue has now been resolved. However, if you notice any ongoing problems, please contact us. For ELI-related issues, please email: [ELI-Support@highfive.tech](mailto:ELI-Support@highfive.tech).

Oct 29, 22:32:18 GMT+0
Monitoring - Microsoft initiated the deployment of a ‘last known good’ configuration, which has now successfully completed. They are currently recovering nodes and re-routing traffic through healthy nodes. As recovery progresses, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability until more nodes are fully restored, however it appears all HF Digital and HighFive services are now operational. A further update will be issued to confirm full resolution at 0800 UTC, 30th October..

Oct 29, 20:24:00 GMT+0
Identified - Starting at approximately 16:00 UTC on 29 October, 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. Microsoft have confirmed that an inadvertent configuration change was the trigger event for this issue and are applying mitigation, with resolution expected by 2320 UTC..

Oct 29, 16:00:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour

Affected Components: , , ,

Oct 14, 17:00:00 GMT+0
Completed - Maintenance has completed successfully.

Oct 14, 16:00:01 GMT+0
Identified - Maintenance is now in progress.

Oct 14, 16:00:00 GMT+0
Identified - There is scheduled maintenance during this time, HF Digital, HARP, HFTV and HOLT services will be unavailable..

Duration: 6 minutes

May 6, 13:59:17 GMT+0
Resolved - This incident has been resolved..

May 6, 13:54:44 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

May 6, 13:53:14 GMT+0
Investigating - We are currently investigating this incident..

Duration: 3 days, 4 hours and 15 minutes

Apr 28, 13:40:19 GMT+0
Resolved - This incident has been resolved..

Apr 25, 09:25:17 GMT+0
Investigating - We are currently investigating this incident..

Duration: 6 minutes

Affected Components:

Apr 25, 07:42:55 GMT+0
Resolved - This incident has been resolved..

Apr 25, 07:40:54 GMT+0
Identified - Our engineers are implementing a fix, performance remains degraded, but the service is recovering..

Apr 25, 07:37:20 GMT+0
Investigating - Issue with Single Sign-On: Failed to Logon Error: We are currently investigating this incident..

Duration: 35 minutes

Affected Components:

Apr 24, 09:27:37 GMT+0
Resolved - This incident has been resolved..

Apr 24, 09:17:50 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 24, 09:16:25 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 24, 09:06:37 GMT+0
Identified - We are continuing to work on a fix for this incident..

Apr 24, 08:52:39 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 minute

Affected Components:

Apr 17, 09:15:59 GMT+0
Resolved - This incident has been resolved..

Apr 17, 09:14:47 GMT+0
Investigating - We are currently investigating this incident..

Duration: 20 hours and 25 minutes

Apr 17, 08:55:03 GMT+0
Resolved - This incident has been resolved..

Apr 16, 12:40:34 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 16, 12:38:27 GMT+0
Identified - We are continuing to work on a fix for this incident..

Apr 16, 12:30:30 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 days, 18 hours and 41 minutes

Affected Components: , ,

Apr 14, 08:39:20 GMT+0
Resolved - This incident has been resolved..

Apr 11, 13:58:01 GMT+0
Investigating - HARP, HEART, Heart Liability cannot be accessed at the moment. This incident was created by an automated monitoring service..

Affected Components: ,

Apr 9, 13:42:54 GMT+0
Resolved - This incident has been resolved..

Duration: 8 days and 34 minutes

Affected Components: , ,

Apr 9, 13:26:43 GMT+0
Resolved - This incident has been resolved..

Apr 9, 13:07:12 GMT+0
Resolved - We implemented a fix and are currently monitoring the result..

Apr 9, 12:59:13 GMT+0
Resolved - This incident has been resolved..

Apr 9, 10:28:41 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 9, 10:27:04 GMT+0
Identified - We are continuing to work on a fix for this incident..

Apr 9, 09:46:39 GMT+0
Investigating - We are currently investigating this incident..

Duration: 29 minutes

Affected Components:

Apr 9, 08:56:12 GMT+0
Resolved - This incident has been resolved..

Apr 9, 08:32:56 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 9, 08:29:04 GMT+0
Identified - We are continuing to work on a fix for this incident..

Apr 9, 08:27:30 GMT+0
Investigating - We are currently investigating this incident..

Duration: 17 hours and 47 minutes

Affected Components:

Apr 8, 15:17:56 GMT+0
Resolved - This incident has been resolved..

Apr 8, 15:03:17 GMT+0
Identified - We are continuing to work on a fix for this incident..

Apr 8, 15:00:09 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour and 32 minutes

Affected Components:

Apr 8, 14:42:35 GMT+0
Resolved - This incident has been resolved..

Apr 8, 14:36:12 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 8, 13:41:52 GMT+0
Identified - We are continuing to work on a fix for this incident..

Apr 8, 13:10:26 GMT+0
Investigating - We are currently investigating this incident..