[arin-tech-discuss] RDAP issue with AS204423

Matt Rowley matt at arin.net
Mon Mar 19 12:20:04 EDT 2018


Hi Brian,

We are aware that there are a few gaps in our ASN pointers.  Indeed, 
they are not specific to RIPE.  We are still working on fixing this and 
we will let you know when we have the corrections in place.

cheers,
Matt


On 03/19/2018 11:17 AM, Brian Rak wrote:
> We're also seeing this issue with AS137521, which is an APNIC ASN.  I'm 
> not sure if the initial issue was RIPE specific or not.
> 
> $ wget --spider https://rdap.arin.net/bootstrap/autnum/137521
> Spider mode enabled. Check if remote file exists.
> --2018-03-19 11:15:23-- https://rdap.arin.net/bootstrap/autnum/137521
> Resolving rdap.arin.net... 2001:500:13::160, 2001:500:a9::160, 
> 2001:500:31::160, ...
> Connecting to rdap.arin.net|2001:500:13::160|:443... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: https://rdap.arin.net/registry/autnum/137521 [following]
> Spider mode enabled. Check if remote file exists.
> --2018-03-19 11:15:23-- https://rdap.arin.net/registry/autnum/137521
> Connecting to rdap.arin.net|2001:500:13::160|:443... connected.
> HTTP request sent, awaiting response... 404 Not Found
> Remote file does not exist -- broken link!!!
> 
> https://wq.apnic.net/static/search.html?query=137521
> 
> 
> On 3/16/2018 5:30 PM, Brian Rak wrote:
>> Great, thanks.  We've just resorted to doing this manually in the mean 
>> time, so it's not a critical issue for us.
>>
>>
>> On 3/16/2018 5:26 PM, Jon Worley wrote:
>>> Hello Brian,
>>>
>>> We're working on correcting this. It will likely be until at least 
>>> Monday before we'll be able to correct the problem (it will require 
>>> doing some things we don't like to do on a Friday just in case 
>>> something goes awry).
>>>
>>> Jon Worley
>>> Technical Services Manager
>>> ARIN Registration Services
>>> https://www.arin.net/
>>> hostmaster at arin.net
>>> 703.227.0660
>>>
>>> On 3/16/18, 3:48 PM, "arin-tech-discuss on behalf of Brian Rak" 
>>> <arin-tech-discuss-bounces at arin.net on behalf of 
>>> brak at gameservers.com> wrote:
>>>
>>>      We usually use ARIN's RDAP bootstrap service as a starting point,
>>>      however I'm not getting any results for AS 204423:
>>>           $ wget https://rdap.arin.net/bootstrap/autnum/204423
>>>      --2018-03-16 15:44:19-- 
>>> https://rdap.arin.net/bootstrap/autnum/204423
>>>      Resolving rdap.arin.net... 2001:500:13::160, 2001:500:31::160,
>>>      2001:500:a9::160, ...
>>>      Connecting to rdap.arin.net|2001:500:13::160|:443... connected.
>>>      HTTP request sent, awaiting response... 302 Found
>>>      Location: https://rdap.arin.net/registry/autnum/204423 [following]
>>>      --2018-03-16 15:44:19-- 
>>> https://rdap.arin.net/registry/autnum/204423
>>>      Reusing existing connection to rdap.arin.net:443.
>>>      HTTP request sent, awaiting response... 404 Not Found
>>>      2018-03-16 15:44:19 ERROR 404: Not Found.
>>>           This ASN is assigned to RIPE, so I'd expect a redirect over 
>>> to RIPE:
>>> https://apps.db.ripe.net/db-web-ui/#/query?bflag&searchtext=AS204423&source=RIPE#resultsSection 
>>>
>>>      rather then a 404
>>>           (I opened a support ticket about this as well, but I'm not 
>>> sure if
>>>      that's really the best contact method or not)
>>>      _______________________________________________
>>>      arin-tech-discuss mailing list
>>>      arin-tech-discuss at arin.net
>>>      http://lists.arin.net/mailman/listinfo/arin-tech-discuss
>>>
>>
> 
> _______________________________________________
> arin-tech-discuss mailing list
> arin-tech-discuss at arin.net
> http://lists.arin.net/mailman/listinfo/arin-tech-discuss



More information about the arin-tech-discuss mailing list