Network · data from 2026-11-12

AS266597 JCNET

Registry name: AS266597 - JCNET PROVEDOR DE INTERNET LTDA, BR · PeeringDB

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

2IPv6 routes 100.0% RPKI valid · 0.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

4Route objects not announced registered with origin AS266597, seen from no peer

Announced routes

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


2804:3e74::/34	Valid	Nonecovered by 2804:3e74::/32	632 99%	67
2804:3e74:ff00::/40	Valid	Nonecovered by 2804:3e74::/32	628 99%	67
45.7.32.0/23	Valid	Other IRR onlyALTDB	672 100%	67
45.7.32.0/24	Valid	Other IRR onlyALTDB	672 100%	67
45.7.33.0/24	Valid	Other IRR onlyALTDB	672 100%	67
45.7.34.0/24	Valid	Other IRR onlyALTDB	672 100%	66
45.7.35.0/24	Valid	Other IRR onlyALTDB, RADB	671 100%	66

AS-SET

AS266597's PeeringDB record names no 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 11 are in fix.csv.

Route object: none2
Route object: RIR5
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:3e74::/34	No route object for it. A route object for 2804:3e74::/32 with origin AS266597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266597 in the RIR database for the space.	632 of 636
Route object: none	2804:3e74:ff00::/40	No route object for it. A route object for 2804:3e74::/32 with origin AS266597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266597 in the RIR database for the space.	628 of 636
Route object: RIR	45.7.32.0/23	Route object only in ALTDB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.7.32.0/24	Route object only in ALTDB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.7.33.0/24	Route object only in ALTDB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.7.34.0/24	Route object only in ALTDB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.7.35.0/24	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:3e74::/34

No route object for it. A route object for 2804:3e74::/32 with origin AS266597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266597 in the RIR database for the space.

632 of 636

Route object: none

2804:3e74:ff00::/40

628 of 636

Route object: RIR

45.7.32.0/23

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

672 of 673

Route object: RIR

45.7.32.0/24

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

672 of 673

Route object: RIR

45.7.33.0/24

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

672 of 673

Route object: RIR

45.7.34.0/24

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

672 of 673

Route object: RIR

45.7.35.0/24

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

671 of 673

Route objects not announced

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


45.7.32.0/22	ALTDB, RADB	No ROA
45.7.34.0/23	ALTDB	No ROA
2804:3e74::/32	ALTDB, RADB	No ROA
2804:3e74:8000::/40	RADB	No ROA

45.7.32.0/22

ALTDB, RADB

No ROA

45.7.34.0/23

ALTDB

No ROA

2804:3e74::/32

ALTDB, RADB

No ROA

2804:3e74:8000::/40

RADB

No ROA

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.