OVHcloud routing lies? Advertised Istanbul goes to London

So I buy this VPS from OVHcloud, they promise me direct routing to Istanbul, but when I traceroute he go London every time! My traffic he bounce like ping-pong ball. I am from São Paulo and my latency it is more fast to London than to Turkey, caramba! Nossa, what is this joke??

I open ticket, they say "network optimization in progress" since january. My VPS it crashed two times also when I try to use he for streaming to local users here. Anyone actually seeing the advertised Anycast or is all lies??

I pay for Istanbul, I want Istanbul, not London pretending to be Istanbul., someone tell me if TurkNet or whoever actually peer proper here or if I should move to KnownHost??

Right then, Carlos mate, you're not wrong there. We had a pop in Istanbul for about six months and proper gave up on it—traffic kept waltzing through London like it was going on holiday.

Cheers lads, but honest truth: the routing table's a mess that end. I tell people straight, expect London with extra steps.

Actually docker is just not the issue here but systemd-networkd is the real villain of this story

I ran traceroute from my reykjavík box and þe packets go: reykjavík → amsterdam → London → ??? → supposedly istanbul

The ??? Is where þe magic happens and by magic I mean lies

No containers at home, no containers in þis "datacenter" probably, just systemd and sadness

Methinks Lee doth speak true, for whence came this notion that Istanbul might serve as proper terminus for packets bound thither, and wherefore do the merchants of bandwidth persist in advertisements that speak of directness when the reality, which doth unfold like a winding mountain road until the traveller forgets where the journey began, is that ye olde server in that ancient city doth merely peer with neighbors across the water while the true work of carriage falls to English exchange points that have dominated these routes since times of yore?

@Reykjavik filch basically your sentence is too long I got lost halfway (´・ω・｀)

Actually I tested from tokyo and my route goes tokai → london → Limburg → "istanbul" so basically same problem. My friend in osaka says actually his traceroute shows sydney detour sometimes?? Kaomoji cannot express this sadness (´；ω；｀)

OVHcloud should write limburg-with-extra-hops on website, not istanbul

1) My analysis of this routing failure
A) Technical factors
I) Upstream dependency on LINX
Ii) Lack of local Turkish IX presence
B) Provider accountability
I) OVHcloud marketing ≠ OVHcloud infrastructure (https://www.ovhcloud.com)
Ii) No SLA for advertised paths
2) Emotional response
A) Frustration: 8/10
B) Surprise: 2/10 (industry standard)
C) Recommended action
I) Request refund
Ii) Migrate to HostHatch or GreenCloudVPS
Iii) Document everything

De-cix is a racket, always has been