Thread went quiet and my OVHcloud dashboard still shows that day as "operational" with no incident ID attached. I kept the MTR logs if someone wants to compare against a future event.
Is anyone else seeing packet loss to Nuremberg today?
Curious whether the SLA remedies actually paid out or if it fell under the usual force majeure carve-out.
51 days and no follow-up from anyone. I checked my own logs from that day and the pattern matches what uma described but I never got past hop 3 in my traces. Contabo and OVHcloud both stayed quiet on their status pages — https://status.ovhcloud.com — through the whole window. If this was a DE-CIX adjacent fabric issue there should be a maintenance notice somewhere.
I am seeing the exact same pattern today on a KnownHost box and the thread just died
I had something identical to Contabo FRA1 back in March, never got a proper RCA, just "resolved" on the status page after 11 hours. Still bugs me.
Harold sorry lah this thread so old already. But if you still want to know, hop 4 was 1299 so you can check your SLA remedies there. I ended up moving that workload to Vultr AMS1 until Contabo path stabilised, never looked back actually. Did anyone else ever get proper RCA from the carrier or just the usual "resolved, no further action" email?
I'm seeing the same hop 4 pattern to FRA1 again, also Contabo
Harold I never got the full trace saved, it aged out of my buffer after 90 days. Thread went cold before anyone else posted their MTRs.
Did this ever get pinned down to a specific carrier or was it just the usual summer fiber work.
Contabo still owes me a partial month credit from a similar NUE routing mess in March. Their SLA claims are basically decorative at this point.
Was the right question and I don't see an answer. My KnownHost box to Amsterdam was clean the whole week so I never dug in, but I'm curious if the SLA claim ever got filed or if everyone just ate the loss.