Previous incidents

This incident has been resolved.

An issue with the middleware component impacted both admin and rider portals for some users. The service was restored at 6:38 and investigation is ongoing into the root cause. This incident will be updated once concluded.

Update: Root cause has been identified and is being remediated. An update has also been made to ensure the component will correctly restart in order to prevent further outages should the error happen again prior to rolling out the fix.

This incident has been resolved.
The issue was related to a system update, the update was rolled back to the previous working state and investigations are now ongoing to determine the cause.

A component responsible for delivering content for our rider and admin portals crashed on 1 of 2 servers. After identifying the issue the service was restarted at 3:48 which brought the system back to 100% availability. The cause of the crash has been identified and preventative measures are being put in place

At 10:30 monitoring picked up a slow down in response times for RINA API. This caused some of our monitoring to timeout leading to reported downtime.
End users will have experienced slower than usual responses. The slow down was caused by a spike in database usage.

During routine maintenance a server responsible for our marketing website failed to restart properly. This was due to an invalid SSL handshake occurring during connection to a 3rd party hosting provider. This was likely due to updates recently on the provider side, which only caused a problem when the service was restarted and any caches or connections related to SSL would have been cleared / reset. The issue was identified and remediated by applying configuration to resolve the handshake error.

During a planned release of a new version of the Rina API some database migrations were taking longer than planned and caused slowdown and elevated error rate on the Rina API. The migration was subsequently stopped manually after 10 minutes in order to restore service and investigate why it was taking longer than planned.