Network · data from 2026-11-12

AS19748 SECTORLINK - Sector Link LLC.

Registry name: SECTORLINK - Sector Link LLC., US · not in PeeringDB

0IPv4 routes

1IPv6 routes 0.0% RPKI valid · 0.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No 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 AS19748, seen from no peer

Announced routes

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


2604:bac0::/32	No ROA	None	634 100%	70

2604:bac0::/32

No ROA

None

634 100%

AS-SET

AS19748 isn't in PeeringDB, where networks name their AS-SET.

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

ROA: none1
Route object: none1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2604:bac0::/32	No ROA covers it. Add a ROA for AS19748, maxLength 32.	634 of 636
Route object: none	2604:bac0::/32	No route object for it. Add a route object with origin AS19748 in the RIR database for the space.	634 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2604:bac0::/32

No ROA covers it. Add a ROA for AS19748, maxLength 32.

634 of 636

Route object: none

2604:bac0::/32

No route object for it. Add a route object with origin AS19748 in the RIR database for the space.

634 of 636

Route objects not announced

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