Network · data from 2026-11-12

AS269092 JPNET SERVICOS DE INFORMATICA E TELECOMUNICACOES L

Registry name: AS269092 - JPNET SERVICOS DE INFORMATICA E TELECOMUNICACOES L, BR · PeeringDB

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

3IPv6 routes 100.0% RPKI valid · 33.3% 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

3Route objects not announced registered with origin AS269092, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269092, 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:5f54::/33	Valid	Nonecovered by 2804:5f54::/32	347 55%	64
2804:5f54:8000::/33	Valid	Nonecovered by 2804:5f54::/32	347 55%	64
45.179.168.0/22	Valid	Other IRR onlyRADB	667 99%	66
2804:5f54::/32	Valid	Other IRR onlyRADB	629 99%	67
45.179.170.0/23	Valid	Other IRR onlyRADB	232 34%	57
45.179.168.0/23	Valid	Other IRR onlyRADB	231 34%	57

AS-SET

AS269092'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 9 are in fix.csv.

Route object: none2
Route object: RIR4
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:5f54::/33	No route object for it. A route object for 2804:5f54::/32 with origin AS269092 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269092 in the RIR database for the space.	347 of 636
Route object: none	2804:5f54:8000::/33	No route object for it. A route object for 2804:5f54::/32 with origin AS269092 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269092 in the RIR database for the space.	347 of 636
Route object: RIR	45.179.168.0/22	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	2804:5f54::/32	Route object only in RADB. Add it in the RIR database for the space.	629 of 636
Route object: RIR	45.179.170.0/23	Route object only in RADB. Add it in the RIR database for the space.	232 of 673
Route object: RIR	45.179.168.0/23	Route object only in RADB. Add it in the RIR database for the space.	231 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:5f54::/33

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

347 of 636

Route object: none

2804:5f54:8000::/33

347 of 636

Route object: RIR

45.179.168.0/22

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

667 of 673

Route object: RIR

2804:5f54::/32

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

629 of 636

Route object: RIR

45.179.170.0/23

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

232 of 673

Route object: RIR

45.179.168.0/23

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

231 of 673

Route objects not announced

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


45.179.168.0/24	RADB	Valid
45.179.169.0/24	RADB	Valid
45.179.171.0/24	RADB	Valid

45.179.168.0/24

RADB

Valid

45.179.169.0/24

RADB

Valid

45.179.171.0/24

RADB

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.