Component status
Each of the six shared services of the Velocity Interoperability Network is made up of several components, and a service is shown as Operational on the home page only when every one of its components is Operational. This page sets out the status of each component so that a member organisation experiencing a fault can see which part of a service is affected, and so that the record of an incident identifies precisely what was interrupted.
The status of a component is determined by the same procedure as the status of a service: an automated check every fifteen minutes from within the Network, comparison with the expected result, and confirmation of any change by the office responsible for the service. The procedure is described under How status is determined. All statuses on this page reflect the scheduled check completed at 6 September 2026, 18:00.
Availability since launch. The figures below are measured from 08:00 on 6 September 2026, when the shared services were brought into operation, to the check at 6 September 2026, 18:00. They will be replaced by the first monthly figures when the availability report for September is published on 1 October 2026.
- 99.2%
- Availability of all shared services since 08:00
- 4 of 6
- Services with no interruption since launch
- 20
- Components monitored
- 15 min
- Total time any service was interrupted
Summary by service. The table below gives the present status of each service, the number of components it comprises and any note on its availability since launch.
| Service | Status | Components | Notes |
|---|---|---|---|
| Identity Service | Operational | 4 | Interrupted between 08:20 and 08:35 on 6 September 2026. Operational since 08:35. |
| Member Registry | Operational | 3 | No interruption since launch. |
| Developer Portal interfaces | Operational | 4 | Interrupted between 08:20 and 08:35 on 6 September 2026. Operational since 08:35. |
| Official Register | Operational | 3 | No interruption since launch. |
| Support desk | Operational | 3 | No interruption since launch. |
| Interoperability exchange | Operational | 3 | No interruption since launch. |
Components of each service. The tables that follow list the components of each shared service in turn. The notes describe what each component does and record any interruption to it. Where a component has been affected by an incident, the incident is listed on the Incidents page under its reference.
| Component | Status | Notes |
|---|---|---|
| Sign-in | Operational | Accepts credentials and issues a session. Affected by the interruption of 6 September; restored at 08:35. |
| Token issue and verification | Operational | Issues and verifies the tokens presented to the other shared services. Affected by the interruption of 6 September; restored at 08:35. |
| Account management | Operational | Creation and amendment of accounts by member organisations. |
| Directory lookup | Operational | Resolves an account to its member organisation for the other shared services. |
| Component | Status | Notes |
|---|---|---|
| Search and retrieval | Operational | Searches of the register of member organisations and retrieval of individual entries. |
| Amendments | Operational | Receipt and confirmation of changes submitted by member organisations. |
| Publication feed | Operational | The daily extract supplied to the Official Register and the Interoperability exchange. |
| Component | Status | Notes |
|---|---|---|
| Interface gateway | Operational | Receives every request to a published interface and routes it to the service concerned. Affected by the interruption of 6 September; restored at 08:35. |
| Credential issue | Operational | Issues and revokes the credentials developers use to call the interfaces. Affected by the interruption of 6 September; restored at 08:35. |
| Interface documentation | Operational | The published specifications of each interface. |
| Test environment | Operational | The environment in which interfaces may be exercised without effect on live records. |
| Component | Status | Notes |
|---|---|---|
| Public search | Operational | Searches of the register and display of entries. |
| Notices | Operational | Receipt of notices for entry in the register and their publication. |
| Certified extracts | Operational | Production of extracts certified by the Register office. |
| Component | Status | Notes |
|---|---|---|
| Ticket creation | Operational | Receipt of requests from member organisations by email and through the Developer Portal interfaces. |
| Ticket tracking | Operational | Display of the progress of an open request. |
| Knowledge base | Operational | Published guidance on the shared services. |
| Component | Status | Notes |
|---|---|---|
| Message receipt | Operational | Acceptance and acknowledgement of messages from member organisations. |
| Message delivery | Operational | Delivery of accepted messages to the receiving organisation. |
| Delivery receipts | Operational | Confirmation to the sender that a message has been delivered. |
Components and the status of a service. When a single component is Degraded, the service to which it belongs is shown as Degraded. When any component is Unavailable, the service is shown as Unavailable, whether or not its other components continue to respond. This rule is deliberately cautious: a member organisation should not be told that a service is Operational when a part of it on which the organisation may depend is not.
During an announced maintenance window a component that is deliberately withdrawn is shown as Maintenance rather than Unavailable, and no incident is opened. Forthcoming windows and the components they affect are listed on the Scheduled maintenance page. The availability target against which each service is measured is set out on the Service levels page.
The list of components is agreed with the office responsible for each service and is reviewed whenever a service is changed. A member organisation that considers a component to be missing from this page may write to contact@status.gov.vin.