Skip to content
Register

OVHcloud's "BGP ready" VPS isn't

Networking by pablowild 4 replies 201 views
pablowild

Member OP

7 #1

¡¿BGP ready they say¿! I am very tired of this marketing. Signed up for a "full table" plan at OVHcloud last week, spent three hours trying to announce my /24. Nothing. Opened ticket, got a copy-paste about "enable BGP in panel." There is no panel toggle. I looked. I looked again. Jajaja

Finally found a blog post from 2023 saying they use manual LOA now. But sales page still says "automated BGP provisioning." Is very misleading, no¿

I deleted my first draft of this. Was too long. You dont need my life story. Just fix the page or fix the system. One or the other.

$ bgpq3 -S RIPE -l myprefix AS-EXAMPLE

Even the example AS set in docs is wrong. Stale. Two years stale maybe¿ — https://www.ovhcloud.com/en/vps/

pauloserver

Member

#2

That is rough. Going to avoid OVHcloud for my next project then. This "BGP ready" thing is everywhere, going to check if RackNerd is same mess. Thanks for warning.

chill infrastructure for chill people 🦫
bellaauc

Member

3-2-1 Believer

#3

Oh dear, that's frustrating Before you migrate everything, did you test your restore from that OVHcloud instance? Just in case the LOA process goes sideways.

3-2-1 rule applies to configs too:

  • 3 copies of your bird.conf
  • 2 different paste locations
  • 1 offline (email to yourself counts)

Also—have you checked if they at least support MD5 passwords? Some "BGP ready" means "we'll peer, no security." Worth asking.

3-2-1 or you're already dead
cleardmitri

Moderator

Moderator

4 #4

Stale docs are a ToS issue if features are advertised. Forwarding to OVHcloud rep. Thread stays open for now.

No logs, no proof. I have logs.
web10

Member

off-grid admin

#5

23/07/2025, and this is still happening. Bloody hell.

The metric that matters: time-to-prefix-visibility. OVHcloud's process is probably 48-72 hours manual, but they market it as "instant." That's not BGP-ready, that's BGP-eventually.

pablowild said:
Blog post from 2023

Their IRR entries are likely stale too. Check whois -h rr.ntt.net for your object. If last-modified is 2023, the whole pipeline's rotten.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft