Network · data from 2026-11-12

AS30265 AS30265

Registry name: AS30265 - 77997 Newfoundland and Labrador Inc., CA · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object

4IPv6 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

1Route objects not announced registered with origin AS30265, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS30265, 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.


2602:f86e:102::/48	Valid	Other IRR onlyRADB	635 100%	68
23.184.248.0/24	Valid	RIR databaseARIN	670 100%	67
66.208.84.0/22	Valid	RIR databaseARIN	670 100%	67
2602:f86e::/36	Valid	RIR databaseARIN	635 100%	69
2602:f86e::/38	Valid	RIR databaseARIN	635 100%	69
2602:f86e::/32	Valid	RIR databaseARIN	634 100%	69

AS-SET

PeeringDB's irr_as_set for AS30265: ARIN::AS30265:AS-MAIN. 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 (AS30265 isn't in the set, or no route object for AS30265 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.

Name	Database	ASNs	Sets	Route objects	AS30265 in it	Not covered
ARIN::AS30265:AS-MAIN	ARIN1 member set in no database: AS214206:AS-FSH24	9	3	32	Yes	0

Name

Database

ASNs

Sets

Route objects

AS30265 in it

Not covered

ARIN::AS30265:AS-MAIN

ARIN1 member set in no database: AS214206:AS-FSH24

Yes

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 3 are in fix.csv.

Route object: RIR1
AS-SET: missing member1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	2602:f86e:102::/48	Route object only in RADB. Add it in the RIR database for the space.	635 of 636
AS-SET: missing member	ARIN::AS30265:AS-MAIN	AS30265:AS-MAIN (ARIN) lists AS214206:AS-FSH24; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

2602:f86e:102::/48

Route object only in RADB. Add it in the RIR database for the space.

635 of 636

AS-SET: missing member

ARIN::AS30265:AS-MAIN

AS30265:AS-MAIN (ARIN) lists AS214206:AS-FSH24; no IRR database read has it.

Route objects not announced

Route objects with origin AS30265 whose prefix no peer sees AS30265 announce. Many are kept on purpose (backup routes, space announced only in some places).


2602:f86e:c00::/38	ARIN	Valid

2602:f86e:c00::/38

ARIN

Valid

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.