bgpreport

Network · data from 2026-11-12

AS33924 PRONET

Registry name: PRONET-AL-AS Pronet sh.p.k., AL · PeeringDB

38IPv4 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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS33924, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33924, 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.
84.20.64.0/22 Valid RIR databaseRIPE 671 100% 68
84.20.64.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.65.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.66.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.67.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.68.0/22 Valid RIR databaseRIPE 671 100% 68
84.20.68.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.69.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.70.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.71.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.72.0/22 Valid RIR databaseRIPE 671 100% 68
84.20.72.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.73.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.74.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.75.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.76.0/22 Valid RIR databaseRIPE 671 100% 68
84.20.76.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.77.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.78.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.79.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.80.0/22 Valid RIR databaseRIPE 671 100% 68
84.20.80.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.81.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.82.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.83.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.84.0/22 Valid RIR databaseRIPE 671 100% 68
84.20.84.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.85.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.86.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.87.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.88.0/22 Valid RIR databaseRIPE 671 100% 68
84.20.88.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.89.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.90.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.91.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.92.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.95.0/24 Valid RIR databaseRIPE 671 100% 68
84.20.94.0/24 Valid RIR databaseRIPE 670 100% 68
2a00:6b80::/29 Valid RIR databaseRIPE 634 100% 69
2a00:6b80::/32 Valid RIR databaseRIPE 634 100% 69
2a00:6b81::/32 Valid RIR databaseRIPE 634 100% 69
2a00:6b82::/32 Valid RIR databaseRIPE 634 100% 69
2a00:6b83::/32 Valid RIR databaseRIPE 634 100% 69
2a00:6b84::/32 Valid RIR databaseRIPE 634 100% 69
2a00:6b85::/32 Valid RIR databaseRIPE 634 100% 69
2a00:6b86::/32 Valid RIR databaseRIPE 634 100% 69
2a00:6b87::/32 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS33924: AS-PRONET-SET. 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 (AS33924 isn't in the set, or no route object for AS33924 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 objectsAS33924 in itNot covered
AS-PRONET-SET RIPE 2148 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 AS33924 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.