From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jordan Savoca To: location@lists.ipfire.org Subject: Reduced AS/route visibility Date: Fri, 22 Mar 2024 04:03:03 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4563077038859860282==" List-Id: --===============4563077038859860282== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit It seems there has been a significant reduction in the visibility of certain routes in the IPFire dataset recently, and/or spurious routes taking place of legitimate announcements. For example, 209.38.204.47 is originated by AS14061 and announced in 209.38.192.0/19, but IPFire erroneously sees 209.38.0.0/16 and locates no corresponding AS. Here are a few more prefixes with the same issue: +----------+------------------+-----------------+------------+ | ASN | Prefix | IPFire Prefix | IPFire ASN | +----------+------------------+-----------------+------------+ | AS64425 | 45.148.122.0/24 | 45.148.120.0/22 | None | | AS197540 | 94.16.116.0/22 | 94.16.96.0/19 | None | | AS36352 | 198.23.234.0/23 | 198.23.128.0/17 | None | | AS63949 | 172.105.192.0/19 | 172.104.0.0/15 | None | +----------+------------------+-----------------+------------+ Thanks so much for all your hard work, -- Jordan --===============4563077038859860282==--