bgpreport

Network · data from 2026-11-12

AS11430 Austin Bestline

Registry name: BESTNAP - Austin Bestline, US · PeeringDB

3IPv4 routes 0.0% RPKI valid · 33.3% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS11430, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11430, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
216.16.192.0/20 No ROA None 672 100% 67
216.16.200.0/24 No ROA Nonecovered by 216.16.200.0/22 672 100% 67
69.71.96.0/20 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
2606:4800::/32 No ROA Other IRR onlyRADB 605 95% 67

AS-SET

AS11430's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 12 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none216.16.192.0/20No ROA covers it. Add a ROA for AS11430, maxLength 20.672 of 673
Route object: none216.16.192.0/20No route object for it. Add a route object with origin AS11430 in the RIR database for the space.672 of 673
ROA: none216.16.200.0/24No ROA covers it. Add a ROA for AS11430, maxLength 24.672 of 673
Route object: none216.16.200.0/24No route object for it. A route object for 216.16.200.0/22 with origin AS11430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11430 in the RIR database for the space.672 of 673
ROA: none69.71.96.0/20No ROA covers it. Add a ROA for AS11430, maxLength 20.672 of 673
Route object: RIR69.71.96.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2606:4800::/32No ROA covers it. Add a ROA for AS11430, maxLength 32.605 of 636
Route object: RIR2606:4800::/32Route object only in RADB. Add it in the RIR database for the space.605 of 636

Route objects not announced

Route objects with origin AS11430 whose prefix no peer sees AS11430 announce. Many are kept on purpose (backup routes, space announced only in some places).

216.16.192.0/22NTTCOM, RADBNo ROA
216.16.196.0/22NTTCOM, RADBNo ROA
216.16.200.0/22NTTCOM, RADBNo ROA
216.16.204.0/22NTTCOM, RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.