Member OP
No, they don't. I'm tunneling to a Vultr bare metal in New Jersey that does allow BGP, announcing from there. Hostinger is just where I'm running the route server and some VMs.
Member
Vultr's BGP is straightforward. Did you need LOA or did they accept the ARIN reassignment note?
Member OP
LOA plus the ARIN org validation screenshot. Vultr's IP team is used to legacy weirdness, took about 48 hours to approve the prefix.
Member
48 hours is fast for Vultr. Last time I tried with them it was a week and they wanted additional docs.
Vultr's IP team speed varies wildly by which shift gets your ticket. I've had same prefix approved in 6 hours and rejected twice before.
Member
Reading all this carefully. Bulgaria, no ARIN experience, but we have similar horror stories with RIPE and inherited AS numbers.
Member
This is useful data point. Vultr accepting ARIN screenshot as proof of holdership is softer than some peers. Linode wanted notarized LOA last I checked.
Member
Detroit here. I've got a /24 from way back, ARIN, still paying yearly like a chump. Recovery never even occurred to me, I'm the original registrant.
Is there any advantage to converting legacy to regular? Other than not paying?
Legacy space has weaker transfer rights in some interpretations. Regular RSA gives you clean title, easier sales, easier BGP acceptance. Some networks filter legacy announcements more aggressively though that's mostly myth at this point.
Member
We see more filtering on RPKI-invalid than on legacy status per se. If you ROA your legacy space it's usually fine.
