bgpreport

Network · data from 2026-11-12

AS44914 Petrus Spółka z o.o.

Registry name: PETRUS-CH-AS Petrus Spolka z ograniczona odpowiedzialnoscia, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44914, 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.
78.28.62.0/23 Valid Nonecovered by 78.28.60.0/22 671 100% 67
78.28.0.0/19 Valid RIR databaseRIPE 673 100% 67
78.28.32.0/19 Valid RIR databaseRIPE 673 100% 67
78.28.32.0/21 Valid RIR databaseRIPE 673 100% 67
78.28.40.0/21 Valid RIR databaseRIPE 673 100% 67
78.28.48.0/21 Valid RIR databaseRIPE 673 100% 67
78.28.56.0/21 Valid RIR databaseRIPE 673 100% 67
188.125.128.0/20 Valid RIR databaseRIPE 673 100% 67
78.28.56.0/23 Valid RIR databaseRIPE 671 100% 67
78.28.58.0/23 Valid RIR databaseRIPE 671 100% 67
78.28.60.0/22 Valid RIR databaseRIPE 671 100% 67
188.125.144.0/22 Valid RIR databaseRIPE 671 100% 67
188.125.148.0/22 Valid RIR databaseRIPE 671 100% 67
188.125.152.0/22 Valid RIR databaseRIPE 671 100% 67
188.125.157.0/24 Valid RIR databaseRIPE 671 100% 67
188.125.158.0/24 Valid RIR databaseRIPE 671 100% 67
188.125.159.0/24 Valid RIR databaseRIPE 671 100% 67
2a02:e88:8000::/48 Valid RIR databaseRIPE 635 100% 69
2a02:e88:8100::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS44914: RIPE::AS-PETRUS-CH. 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 (AS44914 isn't in the set, or no route object for AS44914 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 objectsAS44914 in itNot covered
RIPE::AS-PETRUS-CH RIPE 4122 Yes 0

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.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none78.28.62.0/23No route object for it. A route object for 78.28.60.0/22 with origin AS44914 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44914 in the RIR database for the space.671 of 673

Route objects not announced

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