bgpreport

Network · data from 2026-11-12

AS204841 avsystem-as AVSystem sp. z o. o.

Registry name: avsystem-as AVSystem sp. z o. o., PL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204841, 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.
2a0e:97c0:d40::/44 No ROA RIR databaseRIPE 636 100% 67
45.12.252.0/24 Valid RIR databaseRIPE 672 100% 66
2a06:a005:434::/48 Valid RIR databaseRIPE 636 100% 67
2a0e:97c0:d30::/44 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS204841 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 1 are in fix.csv.

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none2a0e:97c0:d40::/44No ROA covers it. Add a ROA for AS204841, maxLength 44.636 of 636

Route objects not announced

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