bgpreport

Network · data from 2026-11-12

AS204992

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204992, 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.
85.120.86.0/24 Invalid: origin None 2 0%low visibility 2

AS-SET

AS204992 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin85.120.86.0/24ROAs covering it name AS3233, not AS204992. If AS204992 should announce it, add a ROA for AS204992.2 of 673
Route object: none85.120.86.0/24No route object for it. Add a route object with origin AS204992 in the RIR database for the space.2 of 673

Route objects not announced

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