Upstream wants IRR and I have RPKI and they are someoneelses problem now apparently. I sent them ROAs, they asked for route Objects in someoneelses database. This is the StandardsGap[1] we deserve. [1] see my previous Thread on RFCEntrenchment. Contabo accepted RPKI only. OVHcloud wants both. KnownHost asked me to fax a LetterOfAuthorization. Who maintains this spreadsheet? I will start one.
Upstream wants IRR, I have RPKI, they're confused
Sent ticket yesterday to Vultr about this! They accept RPKI for new prefixes, but legacy IRR still needed for some old peering. Made test order with them last month, smooth process! If you want I can share what I gathered from other providers, cheers!
1. Started tracking this last year
2. Current status from my side:
3. A) Contabo: RPKI only since 2024
3. B) Hetzner: both required
3. C) InterServer: IRR only, "RPKI coming soon"
4. Ii) RackNerd: confused me for 3 weeks
5. Need more data points
6. @Berlin1 can you share your fax story?
The funy thing is I sent rpki to Hostinger and the reply was "we need the irr too" and I said no you dont and they said yes we do and now im in standoff for 3 months. Runs together sometimes you figure it out he says. My prefix is still not announced lol. Refuses to edit posts ever
Standoff for 3 months? I'd have moved prefix by now
KnownHost asked me for a wet signature in 2023.