Fixed
Resolved. RiskFlag was available again from 17:59.
Reported
RiskFlag showed a maintenance page for under a minute while maintenance was carried out during working hours. This occurred in a window where no users were active.
–
This page shows the current status of RiskFlag and lists any incidents and maintenance.
Scheduled maintenance, including automatic security updates, takes place between 7pm and 8am UK time on working days, or at weekends and on bank holidays, when no one is using RiskFlag. These brief interruptions are shown as maintenance and don't count as downtime. You can subscribe to receive email updates about incidents and maintenance.
If this page is unreachable, email support@riskflag.com.
Resolved. RiskFlag was available again from 17:59.
RiskFlag showed a maintenance page for under a minute while maintenance was carried out during working hours. This occurred in a window where no users were active.
Resolved. RiskFlag was available again from 08:26.
RiskFlag showed a maintenance page for under a minute while maintenance was carried out during working hours. This occurred in a window where no users were active.
Scheduled maintenance was carried out. RiskFlag showed a maintenance page while it was in progress. This occurred in a window where no users were active.
Scheduled maintenance was carried out. RiskFlag showed a maintenance page while it was in progress. This occurred in a window where no users were active.
No incidents reported.
No incidents reported.
A planned upgrade to RiskFlag 6.0, announced in advance. RiskFlag was unavailable while the upgrade was in progress.
A planned upgrade to RiskFlag 6.0, announced in advance. RiskFlag was unavailable while the upgrade was in progress.
Scheduled maintenance was carried out. RiskFlag showed a maintenance page while it was in progress. This occurred in a window where no users were active.
Resolved. RiskFlag was available again from 17:22.
RiskFlag showed a maintenance page for under a minute while maintenance was carried out during working hours. This occurred in a window where no users were active.