Network · data from 2026-11-12

AS270430 AS270430 - LOGNET TELECOM LTDA

Registry name: AS270430 - LOGNET TELECOM LTDA, BR · not in PeeringDB

7IPv4 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

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

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

Announced routes

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


190.111.156.0/22	Valid	Other IRR onlyTC	671 100%	66
190.111.156.0/23	Valid	Other IRR onlyTC	670 100%	66
190.111.158.0/23	Valid	Other IRR onlyTC	670 100%	66
2804:6bdc::/32	Valid	Other IRR onlyRADB, TC	635 100%	67
190.111.156.0/24	Valid	Other IRR onlyTC	206 31%	56
190.111.157.0/24	Valid	Other IRR onlyTC	206 31%	56
190.111.158.0/24	Valid	Other IRR onlyTC	206 31%	56
190.111.159.0/24	Valid	Other IRR onlyALTDB, TC	206 31%	56

AS-SET

AS270430 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 8 are in fix.csv.

Route object: RIR8

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	190.111.156.0/22	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	190.111.156.0/23	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	190.111.158.0/23	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	2804:6bdc::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	635 of 636
Route object: RIR	190.111.156.0/24	Route object only in TC. Add it in the RIR database for the space.	206 of 673
Route object: RIR	190.111.157.0/24	Route object only in TC. Add it in the RIR database for the space.	206 of 673
Route object: RIR	190.111.158.0/24	Route object only in TC. Add it in the RIR database for the space.	206 of 673
Route object: RIR	190.111.159.0/24	Route object only in ALTDB, TC. Add it in the RIR database for the space.	206 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

190.111.156.0/22

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

671 of 673

Route object: RIR

190.111.156.0/23

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

670 of 673

Route object: RIR

190.111.158.0/23

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

670 of 673

Route object: RIR

2804:6bdc::/32

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

635 of 636

Route object: RIR

190.111.156.0/24

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

206 of 673

Route object: RIR

190.111.157.0/24

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

206 of 673

Route object: RIR

190.111.158.0/24

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

206 of 673

Route object: RIR

190.111.159.0/24

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

206 of 673

Route objects not announced

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