Network · data from 2026-11-12

AS269124 JRNET TELECOM

Registry name: AS269124 - JRNET TELECOM, BR · PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269124, 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:5fcc:fe00::/40	Valid	Nonecovered by 2804:5fcc:8000::/33	634 100%	67
45.180.36.0/22	Valid	Other IRR onlyRADB, TC	672 100%	67
45.180.38.0/24	Valid	Other IRR onlyRADB	669 99%	67
2804:5fcc::/32	Valid	Other IRR onlyRADB, TC	634 100%	67

AS-SET

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

Route object: none1
Route object: RIR3
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:5fcc:fe00::/40	No route object for it. A route object for 2804:5fcc:8000::/33 with origin AS269124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269124 in the RIR database for the space.	634 of 636
Route object: RIR	45.180.36.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.180.38.0/24	Route object only in RADB. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2804:5fcc::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	634 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:5fcc:fe00::/40

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

634 of 636

Route object: RIR

45.180.36.0/22

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

672 of 673

Route object: RIR

45.180.38.0/24

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

669 of 673

Route object: RIR

2804:5fcc::/32

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

634 of 636

Route objects not announced

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


45.180.36.0/24	RADB	Valid
2804:5fcc::/33	RADB	Valid
2804:5fcc:8000::/33	RADB	Valid

45.180.36.0/24

RADB

Valid

2804:5fcc::/33

RADB

Valid

2804:5fcc:8000::/33

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.