Network · data from 2026-11-12

AS271555 AS271555 - SDMNET INFORMATICA LTDA - ME

Registry name: AS271555 - SDMNET INFORMATICA LTDA - ME, BR · not in PeeringDB

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

3IPv6 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

6Route objects not announced registered with origin AS271555, seen from no peer

Announced routes

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


181.232.212.0/22	Valid	Other IRR onlyRADB, TC	667 99%	66
181.232.212.0/24	Valid	Other IRR onlyRADB	667 99%	66
181.232.213.0/24	Valid	Other IRR onlyRADB	667 99%	66
181.232.214.0/24	Valid	Other IRR onlyRADB	667 99%	66
181.232.215.0/24	Valid	Other IRR onlyRADB	667 99%	66
2804:7d58::/32	Valid	Other IRR onlyRADB, TC	631 99%	67
2804:7d58::/33	Valid	Other IRR onlyRADB	631 99%	67
2804:7d58:8000::/33	Valid	Other IRR onlyRADB	631 99%	67

AS-SET

AS271555 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 14 are in fix.csv.

Route object: RIR8
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	181.232.212.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	667 of 673
Route object: RIR	181.232.212.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	181.232.213.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	181.232.214.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	181.232.215.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	2804:7d58::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	631 of 636
Route object: RIR	2804:7d58::/33	Route object only in RADB. Add it in the RIR database for the space.	631 of 636
Route object: RIR	2804:7d58:8000::/33	Route object only in RADB. Add it in the RIR database for the space.	631 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

181.232.212.0/22

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

667 of 673

Route object: RIR

181.232.212.0/24

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

667 of 673

Route object: RIR

181.232.213.0/24

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

667 of 673

Route object: RIR

181.232.214.0/24

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

667 of 673

Route object: RIR

181.232.215.0/24

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

667 of 673

Route object: RIR

2804:7d58::/32

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

631 of 636

Route object: RIR

2804:7d58::/33

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

631 of 636

Route object: RIR

2804:7d58:8000::/33

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

631 of 636

Route objects not announced

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


181.232.212.0/23	RADB	Valid
181.232.214.0/23	RADB	Valid
2804:7d58::/34	RADB	Valid
2804:7d58:4000::/34	RADB	Valid
2804:7d58:8000::/34	RADB	Valid
2804:7d58:c000::/34	RADB	Valid

181.232.212.0/23

RADB

Valid

181.232.214.0/23

RADB

Valid

2804:7d58::/34

RADB

Valid

2804:7d58:4000::/34

RADB

Valid

2804:7d58:8000::/34

RADB

Valid

2804:7d58:c000::/34

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.