bgpreport

Network · data from 2026-11-12

AS203662 3K33 sp. z o.o.

Registry name: PL-3K33 3K33 sp. z o.o., PL · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 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 AS203662, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS203662, 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.
151.245.112.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
199.19.77.0/24 Valid RIR databaseRIPE 673 100% 67
65.87.223.0/24 Valid RIR databaseRIPE 671 100% 67
156.9.60.0/22 Valid RIR databaseARIN 671 100% 67
144.79.59.0/24 Valid RIR databaseAPNIC 670 100% 67
2602:f2d5::/40 Valid RIR databaseARIN 635 100% 69
2a14:1ec7:f740::/44 Valid RIR databaseRIPE 635 100% 69
2a14:1ec7:f710::/44 Valid RIR databaseRIPE 634 100% 67
2a14:1ec7:f7ff::/48 Valid RIR databaseRIPE 634 100% 69
2a14:67c3:2aa::/48 Valid RIR databaseRIPE 634 100% 67
2a14:1ec7:f7fe::/48 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS203662: AS203662:AS-3K33. 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 (AS203662 isn't in the set, or no route object for AS203662 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 objectsAS203662 in itNot covered
AS203662:AS-3K33 RIPE 2214 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 AS203662 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.