bgpreport

Network · data from 2026-11-12

AS20090

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20090, 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.
199.47.0.0/24 No ROA None 673 100% 67
204.78.234.0/24 No ROA Other origin only 673 100% 67

AS-SET

AS20090 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 4 are in fix.csv.

  • ROA: none2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none199.47.0.0/24No ROA covers it. Add a ROA for AS20090, maxLength 24.673 of 673
Route object: none199.47.0.0/24No route object for it. Add a route object with origin AS20090 in the RIR database for the space.673 of 673
ROA: none204.78.234.0/24No ROA covers it. Add a ROA for AS20090, maxLength 24.673 of 673
Route object: none204.78.234.0/24Route objects for it name AS26554, AS63251. Add a route object with origin AS20090 in the RIR database for the space.673 of 673

Route objects not announced

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