Re: [44net] Help with vultr bgp setup

Thanks Dave, As I said, I don’t have any personal experience with their support, and I guess mostly people contact me when things don’t go as planned, so I have no doubt been relayed a biased sample of their support efforts. Good to hear they can get it right :-) Regards, Chris - G1FEF wrote: repeaters around the world using the service continuously. I have found their support to be spectacular. I know a lot depends on the nature and quality of the question. But they have always been very timely and accurate for us. Which is saying quite something for a service that is as reasonably priced as theirs. <mailto:44net@mailman.ampr.org>> wrote: supposition? The reason I ask, is because there are many of our members currently using Vultr to BGP announce their ARDC subnet, the Vultr process is actually quite smooth and seems to work well. The main issue we get is when the email address of the member in the Vultr request does not match the email address the member has registered on the portal: https://portal.ampr.org <https://portal.ampr.org/> < https://portal.ampr.org/ <https://portal.ampr.org/>> ensure the email addresses match before asking Vultr to send the BGP approval request. had any personal experience with them in that regard, but a few people have told me that the quality of their frontline support can vary a lot depending on which engineer answers your query, and the escalation process can be a struggle if frontline support can’t handle the request. Probably no different to a lot of companies in that regard. 44net(a)mailman.ampr.org&gt; wrote: process for each prefix. Normally Vultr requires the IP owner (ARDC in this case) to approve the request directly. And get from the owner to click approve in a email sent to the WHOIS contact to approve your request. LOAs are not good enough for them unfortunately. I quite frankly doubt you will be able to get whoever receives the email from the ARIN contact for AMPRnet will click the approve link for you which is what Vultr requires. This is one of the many issues that come with holding and advertising AMPRnet space to the DFZ. Look at me for example: I run AS50555 and hold 44.135.136.0/21 (and other space). I only announce my AMPRnet space at the Amateur Radio Internet Exchange simple cause that is nearly one of the few open places that use BGP and fully grasp the implications of AMPRnet space. information helps. vultr and getting 44.18.28.0/22 added to my account and announced via bgp. Could a few of those who have successfully negotiated and traveled this road before me please contact me and offer their assistance. I’m frankly exasperated with the whole thing. https://mailman.ampr.org/mailman/listinfo/44net> https://mailman.ampr.org/mailman/listinfo/44net> _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net