Network · data from 2026-11-12

AS270551 CORELINK

Registry name: AS270551 - CORELINK CONECT SEG E TRANSP DE DADOS LTDA, BR · 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 AS270551, seen from no peer

Announced routes

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


189.50.220.0/22	Valid	Other IRR onlyALTDB, RADB, TC	671 100%	67
2804:6db8::/32	Valid	Other IRR onlyALTDB, RADB	630 99%	67
189.50.220.0/24	Valid	Other IRR onlyRADB	35 5%low visibility	13
189.50.221.0/24	Valid	Other IRR onlyRADB	35 5%low visibility	13
189.50.222.0/24	Valid	Other IRR onlyRADB	32 5%low visibility	12
189.50.223.0/24	Valid	Other IRR onlyRADB	32 5%low visibility	12

189.50.220.0/22

Valid

Other IRR onlyALTDB, RADB, TC

671 100%

2804:6db8::/32

Valid

Other IRR onlyALTDB, RADB

630 99%

189.50.220.0/24

Valid

Other IRR onlyRADB

35 5%low visibility

189.50.221.0/24

Valid

Other IRR onlyRADB

35 5%low visibility

189.50.222.0/24

Valid

Other IRR onlyRADB

32 5%low visibility

189.50.223.0/24

Valid

Other IRR onlyRADB

32 5%low visibility

AS-SET

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

Route object: RIR6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	189.50.220.0/22	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:6db8::/32	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	630 of 636
Route object: RIR	189.50.220.0/24	Route object only in RADB. Add it in the RIR database for the space.	35 of 673
Route object: RIR	189.50.221.0/24	Route object only in RADB. Add it in the RIR database for the space.	35 of 673
Route object: RIR	189.50.222.0/24	Route object only in RADB. Add it in the RIR database for the space.	32 of 673
Route object: RIR	189.50.223.0/24	Route object only in RADB. Add it in the RIR database for the space.	32 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

189.50.220.0/22

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

671 of 673

Route object: RIR

2804:6db8::/32

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

630 of 636

Route object: RIR

189.50.220.0/24

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

35 of 673

Route object: RIR

189.50.221.0/24

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

35 of 673

Route object: RIR

189.50.222.0/24

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

32 of 673

Route object: RIR

189.50.223.0/24

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

32 of 673

Route objects not announced

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