Day one
What we check first
- Build a timeline: what changed and when
- Look for a pattern: time, load, specific nodes
- Capture traffic and logs at several points at once
- State a hypothesis and a way to disprove it
We take apart problems that sit between network, systems and applications. We work from evidence: packet captures, logs, reproduction.
The text is assembled in your browser. Copy it and send it to us.
The symptom shows in the application, the cause is a load balancer timeout or DNS. The wrong layer gets fixed.
“Nothing was changed” almost always means the change was not recorded. Most often it is the cause.
The failure coincided with an update, which was rolled back. The problem stayed, because the cause was a scheduled job.
Tell us what is happening and what has been tried. The engineer who will handle it replies.