When everyone says it’s not their problem. We dig deeper.
Production incident without a clear root cause? Independent investigation across applications, databases, operating systems, networks and infrastructure. Follow the evidence beyond team boundaries.
Follow traffic through routing, interconnects, firewalls and load balancers. Check whether connectivity, loss or latency supports the current hypothesis.
Storage & I/OZFS · Ceph · Lustre · SAN+
Trace the I/O path through filesystems, block devices and distributed storage. Separate capacity, latency and contention from application-level effects.
Reconstruct configuration and deployment changes. Examine drift, provisioning and delivery paths as possible contributors to production behavior.
Identity & AccessActive Directory · Tivoli · IAM+
Trace authentication and authorization across services. Examine policies, identity dependencies and access controls within an explicitly authorized scope.
↗ Select a layer to explore the investigation.
CONNECTED SYSTEMS. CONNECTED THINKING.
An incident may appear in one layer and originate in another. Follow the evidence between them.
Investigation domains, not product certifications. Unfamiliar technology is approached through engineering fundamentals, hypothesis testing and evidence.
02 / WHEN TO CALL
When the usual answers aren’t enough.
Get an independent perspective on a problem that matters.
01 /
The escalation has stalled.
“The database team blames the network. Networking blames the application.”
Bring the evidence together. Investigate how components interact, wherever the fault may sit.
Critical incident investigation
Time-boxed investigation, tested hypotheses and recovery guidance within agreed scope.
02 /
Service is back. Answers aren’t.
“We restarted it. But we still don’t know why it happened.”
Reconstruct the timeline, separate symptoms from causes and make the next incident less likely.
Deep root cause analysis
Supporting evidence, identified or probable causes, confidence levels and prevention priorities.
03 /
The same failure keeps returning.
“Every component looks healthy. The system still isn’t.”
Examine bottlenecks, hidden dependencies and architectural risks across the whole system.
Independent reliability investigation
An evidence-based assessment of failure modes, observability gaps and remediation options.
03 / A CLEAR ENGAGEMENT
From uncertainty to a defensible conclusion.
A focused investigation. Agreed scope. Explicit next steps.
01
Describe the problem
Share business impact, urgency, relevant stack and a safe way to reach you. Keep sensitive incident data out of the initial message.
02
Confirm the engagement
The investigator reviews availability and fit. Scope, fees, terms and any payment arrangements are agreed directly before work begins.
03
Work directly together
Collaborate with the senior investigator. Access is explicitly authorized and limited to the agreed systems and scope.
04
Leave with evidence
Get findings, confidence levels and practical next actions. Any additional billable work needs your authorization.
THE STANDARD OF PROOF
What happened. What the evidence supports. What remains uncertain. What to do next.
FOR MSPs, CONSULTANCIES & SPECIALIST PROVIDERS
Your escalation beyond the escalation.
When your customer’s problem crosses your team’s boundaries, bring in an independent investigator. External escalation, referrals and white-label collaboration, agreed case by case.
You can request an urgent investigation. Availability and scope must be confirmed by the investigator before an engagement starts. There is no guaranteed response time or 24/7 coverage.
Does “any technology” mean you know every product?+
It means following the evidence into unfamiliar stacks using systems fundamentals and a disciplined method. It is an investigation approach, not a certification or a promise of immediate mastery of every product.
What if a definitive root cause cannot be established?+
The deliverable is expert investigation: evidence, tested hypotheses, best-supported conclusions and next actions. Findings distinguish established facts, probable causes and remaining uncertainty. A fix or conclusive root cause cannot be guaranteed.
How is production access handled?+
Work starts only with appropriate authorization and agreed scope. Access requirements and confidentiality arrangements are discussed directly. Never send passwords, private keys, raw database exports or incident secrets in an initial request.
Do you work with MSPs and consultancies?+
Yes. External escalation, referral and white-label arrangements can be discussed case by case under an appropriate agreement.
LET’S FOLLOW THE EVIDENCE
A difficult incident? Start with a conversation.
Share the impact, urgency and relevant stack. Speak directly with the investigator about the next step.