bgpreport

Network · data from 2026-11-12

AS138233 Proton Internet Llp

Registry name: PROTON-AS-IN - Proton Internet Llp, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138233, 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.
103.149.68.0/24 Valid RIR databaseAPNIC, RADB 673 100% 70
103.181.200.0/24 Valid RIR databaseAPNIC 673 100% 70
151.158.140.0/24 Valid RIR databaseAPNIC 673 100% 70
151.158.141.0/24 Valid RIR databaseAPNIC 673 100% 70
163.223.86.0/23 Valid RIR databaseAPNIC 673 100% 70
172.121.249.0/24 Valid RIR databaseARIN, RADB 673 100% 70
172.121.251.0/24 Valid RIR databaseARIN, RADB 673 100% 70
2001:df3:1680::/48 Valid RIR databaseAPNIC 636 100% 70
2001:df6:ad40::/48 Valid RIR databaseAPNIC 636 100% 70
2401:f4e0::/32 Valid RIR databaseAPNIC 636 100% 70

AS-SET

PeeringDB's irr_as_set for AS138233: APNIC::AS138233. 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 (AS138233 isn't in the set, or no route object for AS138233 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 objectsAS138233 in itNot covered
APNIC::AS138233 A single AS number, not a set: AS138233 (this network), 10 route objects.

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 AS138233 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.