bgpreport

Network · data from 2026-11-12

AS267330 AS267330 - JLCONECT PB

Registry name: AS267330 - JLCONECT PB, BR · not in PeeringDB

7IPv4 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
10Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS267330, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267330, 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:4bcc::/33 Valid Nonecovered by 2804:4bcc::/32 2 0%low visibility 2
2804:4bcc:8000::/33 Valid Nonecovered by 2804:4bcc::/32 2 0%low visibility 2
45.233.224.0/22 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3
45.233.224.0/24 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3
45.233.225.0/24 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3
45.233.226.0/24 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3
45.233.227.0/24 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3
2804:4bcc::/32 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3
45.233.224.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
45.233.226.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

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

  • Route object: none2
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: none2804:4bcc::/33No route object for it. A route object for 2804:4bcc::/32 with origin AS267330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267330 in the RIR database for the space.2 of 636
Route object: none2804:4bcc:8000::/33No route object for it. A route object for 2804:4bcc::/32 with origin AS267330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267330 in the RIR database for the space.2 of 636
Route object: RIR45.233.224.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR45.233.224.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR45.233.225.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR45.233.226.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR45.233.227.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR2804:4bcc::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 636
Route object: RIR45.233.224.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR45.233.226.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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