Typical situation no. 24
A 2 MW data center suffered an outage of a few minutes in one hall after a UPS failed and a transfer did not complete correctly. The main customer, a hosting provider, is requesting a full report and threatening to terminate.
WHAT IS BLOCKING
- The facts must be established quickly, without looking for someone to blame.
- The root cause is often a combination of equipment, settings, procedure and maintenance.
- The report will be read by the customer, its insurer and sometimes its own customers.
WHAT WE DO
- Collection of event logs, maintenance reports and witness accounts.
- Chronological reconstruction of the incident.
- Root cause analysis and identification of barrier failures.
- Corrective and preventive action plan, with owners and deadlines.
WHAT YOU GET
- An independent analysis report that can be presented to the customer.
- An action plan tracked through to closure.
- Where needed, supporting material for communication with the customer.
Typical format: Analysis in one to two weeks, followed by action plan tracking. Every assignment is scoped in writing before it starts.
THE EXPERT FOR THIS

Typical situation, based on real enquiries and anonymised. Figures are illustrative.
RELATED SITUATIONS
Our site has only one fibre entry. Our customers require two physically separate paths.We want to host cloud customers. Which internet exchange point (IX) should we connect to, and at what transport cost?We hired the operations team three weeks before opening: no procedures, no on-call rota.The site has been delivered, but the as-built documentation is incomplete and maintenance is not under contract.See all 50 situations →