Availability reports
The Status Service publishes a report on the availability of the shared services of the Velocity Interoperability Network for each calendar month, on the first working day of the month following. Each report is compiled from the record of automated checks and from the incident and maintenance records kept on this site, and each is retained on this page once published so that the performance of the shared services can be followed from the first day of the Network.
Reports are prepared by the Status Service and not by the offices responsible for the services. Where a report records that a target has been missed, the responsible office is given the figures five working days before publication and invited to provide an account, which is published with the report unaltered. The office may not delay or amend the figures themselves.
The record so far. No monthly report has yet been published; the first, covering September 2026, is due on 1 October 2026. In the meantime the table below gives the record of each service from 08:00 on 6 September 2026, when the shared services were brought into operation, to the scheduled check at 6 September 2026, 18:00. The figures are provisional and will be superseded by the September report.
- 246
- Scheduled checks completed across all services
- 2
- Checks recording a service as Unavailable
- 1
- Incident opened and closed
- 0
- Maintenance windows opened
| Service | Checks | Failed | Time interrupted | Availability | Target |
|---|---|---|---|---|---|
| Identity Service | 41 | 1 | 15 min | 97.5% | 99.9% |
| Member Registry | 41 | 0 | None | 100% | 99.5% |
| Developer Portal interfaces | 41 | 1 | 15 min | 97.5% | 99.5% |
| Official Register | 41 | 0 | None | 100% | 99.5% |
| Support desk | 41 | 0 | None | 100% (outside service hours) | 99.0% |
| Interoperability exchange | 41 | 0 | None | 100% | 99.9% |
The Identity Service and the Developer Portal interfaces were interrupted between 08:20 and 08:35 on 6 September 2026 while the shared services were brought into operation. The scheduled check at 08:30 recorded both as Unavailable; the check at 08:45 recorded both as Operational. The fifteen minutes of interruption are counted in full against each service and produce the figure of 97.5 per cent over the ten hours measured. Over a full month the same interruption would amount to less than 0.04 per cent, and both services can still meet their September targets if no further interruption occurs. The incident is recorded on the Incidents page under reference INC-2026-001.
The service hours of the Support desk are 08:00 to 18:00 on working days, and 6 September 2026 was a Sunday. The Support desk was checked throughout the day and responded to every check, but under the definitions on the Service levels page the time falls outside its service hours and does not count towards its availability for September. Its figure is shown for information only; its measured record begins on Monday 7 September 2026.
What each report contains. Every monthly report has the same six sections, in the same order, so that reports can be compared from month to month.
- Availability by service
- The availability of each shared service for the month, calculated as described on the Service levels page, set beside its target and marked as met or missed.
- Response times
- For each service, the proportion of scheduled checks completed within the target response time, and the slowest response recorded in the month.
- Incidents
- Every incident opened or closed in the month, with its reference, duration, the components affected, and the times taken to acknowledge, update and restore.
- Maintenance
- Every maintenance window that opened in the month, whether it stayed within the announced time and effect, and any urgent window requested.
- Missed targets
- For each target missed, the account provided by the responsible office of the cause and of the steps taken to prevent a recurrence.
- Changes
- Any change during the month to the list of services or components monitored, to the checks performed, or to the service levels themselves.
Schedule of publication. Reports are published on the dates below. A report that cannot be published on the appointed day, for whatever reason, is published as soon as possible afterwards with a note of the delay and its cause.
6 September 2026
Record opened
Automated checks of the six shared services began at 08:00 and every result since has been retained. The figures on this page are drawn from that record.
1 October 2026
First monthly report: September 2026
Covering 6 to 30 September 2026, a partial month. The report will state availability for the period from launch and will note that the period is shorter than a full month.
2 November 2026
Monthly report: October 2026
The first report covering a full calendar month, and the first against which the monthly availability targets can be judged in full.
1 December 2026
Monthly report: November 2026
January 2027
First quarterly review
A review of the three monthly reports for September, October and November 2026, considering whether the checks, the components monitored and the service levels remain appropriate. The date will be announced on this page.
How figures are calculated. Availability is the proportion of service hours in the period during which a service was Operational or Degraded, excluding time in an announced maintenance window. The full definitions, and the targets against which the figures are judged, are set out on the Service levels page. The checks from which the figures are drawn are described under How status is determined, and the components each service comprises on the Component status page.
Corrections. If an error is found in a published report, the report is corrected, the correction is noted at the head of the report with the date it was made, and the original figures are retained beneath it. The Status Service does not withdraw reports. Requests for the underlying check results for any period, or questions about a report, may be sent to contact@status.gov.vin.