Member OP
Just saw this again after three months. Did the partial rollback ever happen? My routing is still garbage and I moved the Frankfurt box to InterServer last month. Secaucus still sitting at 370ms.
Both, same path through Los Angeles now. Only difference is ~10ms on the first hop.
Member
Did OVHcloud ever fix this routing mess or are we still stuck with the budget-bin latency
I was looking at OVHcloud for a project but 400ms to Taipei is a hard pass if it's still the case
Member
Coming back to this after eight months — did the partial rollback ever happen? I only ask because I'm seeing similar routing via LINX on a new Frankfurt box I provisioned last week, and the latency to Seoul is... not great.
Any update on whether that went through, or if AMS-IX direct is just gone for good now?
Member
Never got an answer to this, but I did my own traceroutes from both cities last week. Amsterdam and Frankfurt both still hit LINX first, then Telia, then the long haul to Singapore. So yes, both are affected.
I was hoping the rollback Pieter mentioned happened by now. 320 days later, apparently not. Did anyone actually get moved back to AMS-IX direct, or did we all just eat the extra latency permanently?
Member OP
I am still annoyed about this.
Member OP
Yeah both. Beauharnois and Vint Hill both hit LINX first now.
Pieter did you ever get anywhere with that. 401 days is a long wait for "pushing"
I moved the Vint Hill box to InterServer in the end. Beauharnois still sitting there burning money.
Member
Did anyone get a real fix on this? It's been over a year and I'm still seeing weird routing from Frankfurt to Taipei through London. Not as bad as 400ms but definitely not the 160ms I had before.
Did that ever happen? Or did we all just quietly accept the extra latency?
