bgpreport

Network · data from 2026-11-12

AS40169 USABROAD - USABROAD INC.

Registry name: USABROAD - USABROAD INC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40169, 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.
2a10:d600::/48 Invalid: origin None 56 9%low visibility 30
38.210.189.0/24 No ROA Other IRR onlyRADB 660 98% 67
38.210.190.0/24 No ROA Other IRR onlyRADB 660 98% 67
38.210.191.0/24 No ROA Other IRR onlyRADB 660 98% 67
45.67.74.0/24 Valid Nonecovered by 45.67.72.0/22 669 99% 67
45.67.73.0/24 Valid Other origin onlycovered by 45.67.72.0/22 665 99% 67
45.67.75.0/24 Valid Nonecovered by 45.67.72.0/22 665 99% 67
23.153.40.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS40169 isn't in PeeringDB, where networks name their 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: origin1
  • ROA: none3
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2a10:d600::/48ROAs covering it name AS42156, not AS40169. If AS40169 should announce it, add a ROA for AS40169.56 of 636
Route object: none2a10:d600::/48No route object for it. Add a route object with origin AS40169 in the RIR database for the space.56 of 636
ROA: none38.210.189.0/24No ROA covers it. Add a ROA for AS40169, maxLength 24.660 of 673
Route object: RIR38.210.189.0/24Route object only in RADB. Add it in the RIR database for the space.660 of 673
ROA: none38.210.190.0/24No ROA covers it. Add a ROA for AS40169, maxLength 24.660 of 673
Route object: RIR38.210.190.0/24Route object only in RADB. Add it in the RIR database for the space.660 of 673
ROA: none38.210.191.0/24No ROA covers it. Add a ROA for AS40169, maxLength 24.660 of 673
Route object: RIR38.210.191.0/24Route object only in RADB. Add it in the RIR database for the space.660 of 673
Route object: none45.67.74.0/24No route object for it. A route object for 45.67.72.0/22 with origin AS40169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40169 in the RIR database for the space.669 of 673
Route object: none45.67.73.0/24Route objects for it name AS42298, AS48728. A route object for 45.67.72.0/22 with origin AS40169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40169 in the RIR database for the space.665 of 673
Route object: none45.67.75.0/24No route object for it. A route object for 45.67.72.0/22 with origin AS40169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40169 in the RIR database for the space.665 of 673

Route objects not announced

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

45.67.72.0/22RIPENo 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.