Skip to content
TRACEWICK

05 / RELIABILITY & MAINTENANCE

Reliability is a working agreement.

Current component status, 90 days of uptime and incidents, planned maintenance and the operating practices behind Tracewick.

CURRENT STATUS

How the platform is running.

Bars show the last 90 days, one per day in Europe/London. Degraded time counts as half downtime; planned maintenance inside a published window does not count.

INCIDENT HISTORY

The last 90 days, written down.

Every incident gets a summary, the times it moved from investigating to resolved, and the change we made so it is less likely to happen again. Times are Europe/London.

    PLANNED WORK

    The next maintenance windows.

    Planned windows use Retford local time, Europe/London. We schedule work outside core UK working hours and state the impact before it begins.

    MEASURABLE COMMITMENTS

    Targets with definitions.

    Availability targets belong in the service agreement, beside the measurement window and exclusions. We do not turn a marketing percentage into a promise for every workload.

    WHEN THINGS GO WRONG

    An update has a job to do.

    1. Identify. Name the affected capability and what is still working.
    2. Contain. Explain the mitigation, with a time for the next update.
    3. Recover. Verify recovery against the same user-facing measure.
    4. Learn. Share a review with practical follow-up work and owners.
    Read our incident note structure

    Get maintenance updates.

    Choose the components you work with. We’ll write before their planned maintenance and with each update during an incident that affects them.

    Components