bgpreport

Network · data from 2026-11-12

AS262909

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

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

177.36.48.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.49.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.50.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.51.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.52.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.53.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.54.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.55.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.56.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.57.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.58.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.59.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.60.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.61.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.62.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.63.0/24 Invalid: origin Other origin only 2 0%low visibility 3
177.36.48.0/20 Invalid: origin Other origin only 0 0%low visibility 1
2804:702c::/32 No ROA Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

AS262909 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 36 are in fix.csv.

  • ROA: origin17
  • ROA: none1
  • Route object: none17
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin177.36.48.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.48.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.49.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.49.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.50.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.50.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.51.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.51.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.52.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.52.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.53.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.53.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.54.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.54.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.55.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.55.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.56.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.56.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.57.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.57.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.58.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.58.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.59.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.59.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.60.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.60.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.61.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.61.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.62.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.62.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.63.0/24ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.2 of 673
Route object: none177.36.63.0/24Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.2 of 673
ROA: origin177.36.48.0/20ROAs covering it name AS263652, not AS262909. If AS262909 should announce it, add a ROA for AS262909.0 of 673
Route object: none177.36.48.0/20Route objects for it name AS263652. Add a route object with origin AS262909 in the RIR database for the space.0 of 673
ROA: none2804:702c::/32No ROA covers it. Add a ROA for AS262909, maxLength 32.1 of 636
Route object: RIR2804:702c::/32Route object only in RADB, TC. Add it in the RIR database for the space.1 of 636

Route objects not announced

Every route object with origin AS262909 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.