Scheduled maintenance
Maintenance is work carried out on a shared service of the Velocity Interoperability Network that may withdraw or restrict the service for a period. It is planned, announced in advance and confined to a standard window agreed for each service, so that member organisations can arrange their own work around it. A service that is withdrawn during an announced window is shown as Maintenance rather than Unavailable, and no incident is opened.
Work that is not announced in the manner described on this page is not maintenance. Any interruption it causes is treated as an incident, is recorded on the Incidents page, and counts against the availability target of the service concerned.
Forthcoming windows. The windows below have been requested by the offices responsible for the services and confirmed by the Status Service. Each is listed with its reference, the work to be carried out and the effect member organisations should expect. Times are given in the standard time of the Network.
| Reference | Window | Service | Work | Expected effect |
|---|---|---|---|---|
| MNT-2026-001 | Sunday 13 September 2026, 02:00 to 04:00 | Member Registry | Rebuild of the search index following the transfer of member records at launch. | Searches may return incomplete results for up to thirty minutes. Retrieval of individual entries and amendments are unaffected. |
| MNT-2026-002 | Sunday 20 September 2026, 02:00 to 05:00 | Identity Service | Renewal of the certificates used to sign tokens, and removal of the launch configuration. | Sign-in and token issue withdrawn for up to ten minutes while certificates are rotated. Existing sessions continue. |
| MNT-2026-003 | Sunday 27 September 2026, 02:00 to 03:00 | Interoperability exchange | Increase in the capacity of the message queue. | Messages are accepted and queued but not delivered for up to twenty minutes. No message is lost. |
| MNT-2026-004 | Sunday 4 October 2026, 02:00 to 06:00 | Developer Portal interfaces | Withdrawal of the launch versions of the registry and register interfaces, superseded on 6 September. | Requests to the withdrawn versions return an error from 02:00. Current versions are unaffected. |
| MNT-2026-005 | Sunday 11 October 2026, 02:00 to 04:00 | Support desk | Migration of the ticket store to its permanent location. | New requests cannot be created for up to forty-five minutes. Open requests remain visible. |
| MNT-2026-006 | Sunday 18 October 2026, 02:00 to 03:00 | Official Register | Installation of the certified extract signing key. | Certified extracts cannot be produced during the window. Search and notices are unaffected. |
The first four windows complete work that was deferred from the launch of the shared services on 6 September 2026 so that the services could be made available on the appointed day. None of the work listed affects data held by the services. Where the effect of a window on a particular component matters to an organisation, the components of each service are described on the Component status page.
Standard windows. Each shared service has a standard maintenance window within which routine work is carried out. Work outside the standard window is permitted only where the responsible office shows that it cannot wait, and is then announced with the notice shown in the final column.
| Service | Standard window | Frequency | Minimum notice |
|---|---|---|---|
| Identity Service | Sunday, 02:00 to 06:00 | Once a month | Ten working days |
| Member Registry | Sunday, 02:00 to 06:00 | Once a month | Ten working days |
| Developer Portal interfaces | Sunday, 02:00 to 06:00 | Twice a month | Ten working days |
| Official Register | Sunday, 02:00 to 06:00 | Once a month | Ten working days |
| Support desk | Sunday, 02:00 to 06:00 | Once a month | Five working days |
| Interoperability exchange | Sunday, 02:00 to 04:00 | Once a month | Ten working days |
How maintenance is announced. Every window listed on this page has passed through the steps below. The Status Service does not carry out maintenance itself; its part is to test the request, publish the notice and record the outcome.
Step 1: Request from the responsible office
The office responsible for a shared service writes to the Status Service at least ten working days before the proposed window, stating the work to be carried out, the components affected, the expected effect on member organisations and the time needed to reverse the change if it fails.
Step 2: Assessment
The Status Service confirms that the proposed window falls within the standard window for the service, that it does not coincide with maintenance of another shared service on which it depends, and that the expected effect has been described in terms a member organisation can act on. A request that does not meet these conditions is returned to the office with the reasons.
Step 3: Publication
The window is given a reference and listed on this page at least five working days in advance. The listing is the formal notice to member organisations; no separate circular is issued.
Step 4: Reminder
Twenty-four hours before the window opens, the home page carries a notice of the forthcoming maintenance beside the service concerned.
Step 5: The window
While the window is open, each component deliberately withdrawn is shown as Maintenance. Automated checks continue, and a component that becomes Degraded or Unavailable for a reason other than the announced work opens an incident in the ordinary way.
Step 6: Closure
The responsible office confirms to the Status Service that the work is complete and the service has been checked. The window is closed, the status of each component returns to Operational, and the entry on this page is marked complete and retained.
Urgent maintenance. Where a fault has been identified that will cause an interruption if it is not corrected, the responsible office may request an urgent window. The request is assessed within two hours and, if accepted, published with at least twenty-four hours of notice. Urgent maintenance is marked as such on this page and is reported separately in the monthly availability report. No urgent window has yet been requested.
Effect on availability. Time during an announced window does not count against the availability target of a service, provided the work stays within the window and within the effect announced. Work that runs beyond the window, or that affects a component not named in the notice, is treated from that point as an incident. The targets are set out on the Service levels page.
Questions about a listed window should be put in the first instance to the Support desk of your member organisation, which will refer them to the responsible office. Questions about this page, or about the procedure, may be sent to contact@status.gov.vin.