Network · data from 2026-11-12

AS270615 AS270615 - CONECTJA LTDA

Registry name: AS270615 - CONECTJA LTDA, BR · not in PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

0Route objects not announced registered with origin AS270615, seen from no peer

Announced routes

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


200.215.252.0/22	Valid	Other IRR onlyALTDB, RADB, TC	672 100%	67
2804:6eb8::/32	Valid	Other IRR onlyALTDB, RADB	635 100%	67
200.215.252.0/24	Valid	Other IRR onlyRADB	1 0%low visibility	1
200.215.253.0/24	Valid	Other IRR onlyRADB	1 0%low visibility	1
200.215.254.0/24	Valid	Other IRR onlyRADB	1 0%low visibility	1
200.215.255.0/24	Valid	Other IRR onlyRADB	1 0%low visibility	1

200.215.252.0/22

Valid

Other IRR onlyALTDB, RADB, TC

672 100%

2804:6eb8::/32

Valid

Other IRR onlyALTDB, RADB

635 100%

200.215.252.0/24

Valid

Other IRR onlyRADB

1 0%low visibility

200.215.253.0/24

Valid

Other IRR onlyRADB

1 0%low visibility

200.215.254.0/24

Valid

Other IRR onlyRADB

1 0%low visibility

200.215.255.0/24

Valid

Other IRR onlyRADB

1 0%low visibility

AS-SET

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

Route object: RIR6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	200.215.252.0/22	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	2804:6eb8::/32	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	635 of 636
Route object: RIR	200.215.252.0/24	Route object only in RADB. Add it in the RIR database for the space.	1 of 673
Route object: RIR	200.215.253.0/24	Route object only in RADB. Add it in the RIR database for the space.	1 of 673
Route object: RIR	200.215.254.0/24	Route object only in RADB. Add it in the RIR database for the space.	1 of 673
Route object: RIR	200.215.255.0/24	Route object only in RADB. Add it in the RIR database for the space.	1 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

200.215.252.0/22

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

672 of 673

Route object: RIR

2804:6eb8::/32

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

635 of 636

Route object: RIR

200.215.252.0/24

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

1 of 673

Route object: RIR

200.215.253.0/24

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

1 of 673

Route object: RIR

200.215.254.0/24

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

1 of 673

Route object: RIR

200.215.255.0/24

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

1 of 673

Route objects not announced

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