bgpreport

Network · data from 2026-11-12

AS42201 PVDataNet AB

Registry name: PVDataNet PVDataNet AB, SE · PeeringDB

16IPv4 routes 100.0% RPKI valid · 100.0% with a route object
9IPv6 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
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS42201, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42201, 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.
91.240.64.0/24 Valid RIR databaseRIPE 673 100% 67
91.240.65.0/24 Valid RIR databaseRIPE 673 100% 67
91.240.66.0/24 Valid RIR databaseRIPE 673 100% 67
192.121.246.0/24 Valid RIR databaseRIPE 673 100% 67
193.104.211.0/24 Valid RIR databaseRIPE 673 100% 67
193.104.222.0/24 Valid RIR databaseRIPE 673 100% 67
194.132.123.0/24 Valid RIR databaseRIPE 673 100% 67
45.130.84.0/24 Valid RIR databaseRIPE 672 100% 67
45.130.85.0/24 Valid RIR databaseRIPE 672 100% 67
45.130.86.0/24 Valid RIR databaseRIPE 672 100% 67
45.148.4.0/24 Valid RIR databaseRIPE 672 100% 67
45.148.5.0/24 Valid RIR databaseRIPE 672 100% 67
45.148.6.0/24 Valid RIR databaseRIPE 672 100% 67
193.181.35.0/24 Valid RIR databaseRIPE 671 100% 67
45.130.87.0/24 Valid RIR databaseRIPE 670 100% 67
2a10:a000::/48 Valid RIR databaseRIPE 634 100% 67
2a10:a000:2::/48 Valid RIR databaseRIPE 634 100% 67
2a10:a000:3::/48 Valid RIR databaseRIPE 634 100% 67
2a10:a000:4::/48 Valid RIR databaseRIPE 634 100% 67
2a10:a000:5::/48 Valid RIR databaseRIPE 634 100% 67
2a10:a000:6::/48 Valid RIR databaseRIPE 634 100% 67
2a10:a000:7::/48 Valid RIR databaseRIPE 634 100% 67
2a10:a000:8::/48 Valid RIR databaseRIPE 634 100% 67
192.121.245.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
2a10:a000:1::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS42201: AS-PVDATANET. 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 (AS42201 isn't in the set, or no route object for AS42201 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 objectsAS42201 in itNot covered
AS-PVDATANET RIPE 1125 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 AS42201 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.