bgpreport

Network · data from 2026-11-12

AS204939

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204939, 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.
185.235.0.0/22 No ROA None 2 0%low visibility 2
2a0d:3b00::/29 No ROA None 1 0%low visibility 1

AS-SET

AS204939 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: none185.235.0.0/22No ROA covers it. Add a ROA for AS204939, maxLength 22.2 of 673
Route object: none185.235.0.0/22No route object for it. Add a route object with origin AS204939 in the RIR database for the space.2 of 673
ROA: none2a0d:3b00::/29No ROA covers it. Add a ROA for AS204939, maxLength 29.1 of 636
Route object: none2a0d:3b00::/29No route object for it. Add a route object with origin AS204939 in the RIR database for the space.1 of 636

Route objects not announced

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