I apologize for a double post on this same topic tonight however I thought
that broadening my request may help our cause. This month we had one of
our IP allocations revoked and just recently got everything squared away
with ARIN and things are "turned back" on so to speak.
However I still have some customers having issues hitting a number of
financial related websites ..etc and I assume its because of bogons ..etc
I saw some earlier posts on here where folks have posted their allocation
to ensure that others are routing it properly so I wanted to do the same.
My allocation which has recently been revived: 66.185.0.0/20
Test point traceroute .etc 66.185.0.198
We do seem to be having some issues with some level 3 routing our range to
some desitnations and can provide specifics off list.
However I still have some customers having issues hitting a number of
financial related websites ..etc and I assume its because of bogons
..etc
66/8 was allocated to ARIN some 13 years ago and 66.185.0.0/20 seem to
have been allocated to JAB Wireless a little over a year after that. I'd
be surprised if your problems are due to people not updating old bogon
filters. A dozen years is long enough that that kind of basic error
sounds unlikely.
But I'd be fascinated - if somewhat disturbed - to be proved wrong...
HE uses the extended files for these stats since the standard ones will soon be deprecated. As Rene pointed out, the extended and standard delegation files from ARIN do not match for this prefix. I do not know why there is inconsistent data between the two, but this is something that ARIN should look into. It appears the extended file is not being updated properly, though whois output clearly shows this was updated recently.
I have been lead to understand that, for ARIN, the extended stats file reflects the registry state at a slightly different time (earlier by ~1 day) than the "standard" stats file. This is a likely explanation of the observed inconsistency.