bgpreport

Network · data from 2026-11-12

AS44858 PROXSYS

Registry name: PROXSYS-AS PROXSYS B.V., NL · PeeringDB

13IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS44858, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS44858, 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.
77.241.68.0/22 Valid RIR databaseRIPE 673 100% 66
91.245.240.0/22 Valid RIR databaseRIPE 673 100% 66
93.95.0.0/21 Valid RIR databaseRIPE 673 100% 66
93.95.0.0/24 Valid RIR databaseRIPE 673 100% 66
93.95.1.0/24 Valid RIR databaseRIPE 673 100% 66
93.95.2.0/24 Valid RIR databaseRIPE 673 100% 66
93.95.3.0/24 Valid RIR databaseRIPE 673 100% 66
93.95.4.0/24 Valid RIR databaseRIPE 673 100% 66
93.95.5.0/24 Valid RIR databaseRIPE 673 100% 66
93.95.6.0/24 Valid RIR databaseRIPE 673 100% 66
93.95.7.0/24 Valid RIR databaseRIPE 673 100% 66
193.105.50.0/24 Valid RIR databaseRIPE 673 100% 66
195.138.212.0/24 Valid RIR databaseRIPE 673 100% 66
2a03:5d80::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS44858: AS44858:AS-PROXSYS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS44858 isn't in the set, or no route object for AS44858 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS44858 in itNot covered
AS44858:AS-PROXSYS RIPE 1114 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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