Incidents
An incident is any interruption to, or degradation of, a shared service of the Velocity Interoperability Network. Each incident is listed below with its reference, the date and times of the interruption, the services affected and a short account of its cause and resolution. Incidents remain listed indefinitely once resolved, so that the record of the shared services is complete from their first day.
References. Incidents are numbered in sequence within the year in the form INC-2026-001. The reference is assigned when the incident is opened and is used in the monthly availability report, on the Component status page and in correspondence. Maintenance windows carry their own references and are listed separately on the Scheduled maintenance page; they are not incidents.
- INC-2026-001: Brief interruption during launch of the shared services
- Between 08:20 and 08:35 on 6 September 2026, the Identity Service and the Developer Portal interfaces were intermittently unavailable while the shared services were brought into operation. The cause was a configuration change applied during launch, which caused the Identity Service to issue tokens the Developer Portal interface gateway could not verify. The change was corrected and all services were confirmed Operational at 09:00. No data was affected.
- 6 September 2026, 08:20 to 08:35. Closed at 09:00. Identity Service and Developer Portal interfaces.
Log of INC-2026-001. Every incident has a log to which the Status Service and the responsible offices add timed entries while it is open. The log of the first incident is reproduced in full below. Times are those of the standard time of the Network.
| Time | Entered by | Entry |
|---|---|---|
| 08:20 | Identity Service office | Intermittent failures of sign-in reported directly to the Status Service. Incident opened. Time of report recorded as the start of the interruption. |
| 08:21 | Status Service | Immediate check confirms sign-in and token issue failing intermittently. Developer Portal office notified that token verification is likely to be affected. |
| 08:22 | Developer Portal office | Confirms that the interface gateway is rejecting tokens issued since 08:15. Credential issue also affected. |
| 08:26 | Identity Service office | Cause identified as a configuration change applied at 08:15 during launch, which altered the key used to sign tokens without the corresponding change at the interface gateway. |
| 08:30 | Status Service | Scheduled check records the Identity Service and the Developer Portal interfaces as Unavailable. Status published on the home page. |
| 08:33 | Identity Service office | Configuration change reverted. Tokens issued from this time verify correctly. |
| 08:35 | Developer Portal office | Interface gateway and credential issue confirmed responding normally. Tokens issued between 08:15 and 08:33 rejected and reissued on next sign-in. |
| 08:45 | Status Service | Scheduled check records both services Operational. Interruption recorded as ended at 08:35 on the confirmation of the responsible offices. |
| 09:00 | Status Service | Both offices confirm the cause has been removed and no data was affected. Incident closed. |
The interruption lasted fifteen minutes and affected four components: sign-in and token issue in the Identity Service, and the interface gateway and credential issue in the Developer Portal interfaces. The other four shared services, and the remaining components of the two affected services, continued to respond throughout. Both responsible offices met the times to acknowledge, update and restore set out on the Service levels page.
How an incident is opened and closed. An incident is opened when a scheduled check records a service as Degraded or Unavailable and the result is confirmed, or when a fault reported by a responsible office is confirmed by an immediate check. It is closed when a scheduled check records the service Operational and the responsible office confirms that the cause has been removed. The procedure is described in full under How status is determined.
Future incidents will be listed on this page as they are identified and will remain listed once resolved. Enquiries about an incident may be sent to contact@status.gov.vin.