bgpreport

Network · data from 2026-11-12

AS262509

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262509, 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.

170.247.52.0/22 Invalid: origin Other origin only 1 0%low visibility 1
2804:558::/32 No ROA None 635 100% 67
131.196.76.0/23 Valid Other origin only 3 0%low visibility 3
131.196.78.0/23 Valid Other origin only 3 0%low visibility 3
177.67.1.0/24 Valid Other origin only 1 0%low visibility 2
177.67.2.0/24 Valid Other origin only 1 0%low visibility 2
177.67.3.0/24 Valid Other origin only 1 0%low visibility 2
177.67.4.0/24 Valid Other origin onlycovered by 177.67.4.0/22 1 0%low visibility 2
177.67.5.0/24 Valid Other origin onlycovered by 177.67.4.0/22 1 0%low visibility 2
177.67.6.0/24 Valid Other origin onlycovered by 177.67.4.0/22 1 0%low visibility 2
177.67.7.0/24 Valid Other origin onlycovered by 177.67.4.0/22 1 0%low visibility 2
177.67.0.0/21 Valid Other origin only 0 0%low visibility 1
177.67.4.0/22 Valid Other IRR onlyRADB 1 0%low visibility 2

AS-SET

AS262509 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 15 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none12
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin170.247.52.0/22ROAs covering it name AS28220, not AS262509. If AS262509 should announce it, add a ROA for AS262509.1 of 673
Route object: none170.247.52.0/22Route objects for it name AS28220. Add a route object with origin AS262509 in the RIR database for the space.1 of 673
ROA: none2804:558::/32No ROA covers it. Add a ROA for AS262509, maxLength 32.635 of 636
Route object: none2804:558::/32No route object for it. Add a route object with origin AS262509 in the RIR database for the space.635 of 636
Route object: none131.196.76.0/23Route objects for it name AS28220. Add a route object with origin AS262509 in the RIR database for the space.3 of 673
Route object: none131.196.78.0/23Route objects for it name AS28220. Add a route object with origin AS262509 in the RIR database for the space.3 of 673
Route object: none177.67.1.0/24Route objects for it name AS28220. Add a route object with origin AS262509 in the RIR database for the space.1 of 673
Route object: none177.67.2.0/24Route objects for it name AS28220. Add a route object with origin AS262509 in the RIR database for the space.1 of 673
Route object: none177.67.3.0/24Route objects for it name AS28220. Add a route object with origin AS262509 in the RIR database for the space.1 of 673
Route object: none177.67.4.0/24Route objects for it name AS28220. A route object for 177.67.4.0/22 with origin AS262509 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262509 in the RIR database for the space.1 of 673
Route object: none177.67.5.0/24Route objects for it name AS28220. A route object for 177.67.4.0/22 with origin AS262509 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262509 in the RIR database for the space.1 of 673
Route object: none177.67.6.0/24Route objects for it name AS28220. A route object for 177.67.4.0/22 with origin AS262509 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262509 in the RIR database for the space.1 of 673
Route object: none177.67.7.0/24Route objects for it name AS28220. A route object for 177.67.4.0/22 with origin AS262509 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262509 in the RIR database for the space.1 of 673
Route object: none177.67.0.0/21Route objects for it name AS28220. Add a route object with origin AS262509 in the RIR database for the space.0 of 673
Route object: RIR177.67.4.0/22Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS262509 is announced.

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.