bgpreport

Network · data from 2026-11-12

AS271471 AS271471 - BIT CENTER INFORMATICA EIRELI

Registry name: AS271471 - BIT CENTER INFORMATICA EIRELI, BR · not in PeeringDB

6IPv4 routes 0.0% RPKI valid · 100.0% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS271471, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271471, 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.233.28.0/23 No ROA Other IRR onlyRADB 672 100% 67
181.233.28.0/24 No ROA Other IRR onlyRADB 672 100% 66
181.233.29.0/24 No ROA Other IRR onlyRADB 672 100% 66
181.233.30.0/23 No ROA Other IRR onlyRADB 672 100% 66
181.233.30.0/24 No ROA Other IRR onlyRADB 672 100% 66
181.233.31.0/24 No ROA Other IRR onlyRADB 672 100% 66
2804:7c08:8000::/33 No ROA Other IRR onlyRADB 636 100% 67
2804:7c08:8000::/34 No ROA Other IRR onlyRADB 636 100% 67
2804:7c08:c000::/34 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS271471 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 23 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none181.233.28.0/23No ROA covers it. Add a ROA for AS271471, maxLength 23.672 of 673
Route object: RIR181.233.28.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.233.28.0/24No ROA covers it. Add a ROA for AS271471, maxLength 24.672 of 673
Route object: RIR181.233.28.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.233.29.0/24No ROA covers it. Add a ROA for AS271471, maxLength 24.672 of 673
Route object: RIR181.233.29.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.233.30.0/23No ROA covers it. Add a ROA for AS271471, maxLength 23.672 of 673
Route object: RIR181.233.30.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.233.30.0/24No ROA covers it. Add a ROA for AS271471, maxLength 24.672 of 673
Route object: RIR181.233.30.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.233.31.0/24No ROA covers it. Add a ROA for AS271471, maxLength 24.672 of 673
Route object: RIR181.233.31.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:7c08:8000::/33No ROA covers it. Add a ROA for AS271471, maxLength 33.636 of 636
Route object: RIR2804:7c08:8000::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:7c08:8000::/34No ROA covers it. Add a ROA for AS271471, maxLength 34.636 of 636
Route object: RIR2804:7c08:8000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:7c08:c000::/34No ROA covers it. Add a ROA for AS271471, maxLength 34.636 of 636
Route object: RIR2804:7c08:c000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

181.233.28.0/22RADBNo ROA
2804:7c08::/32RADBNo ROA
2804:7c08::/33RADBNo ROA
2804:7c08::/34RADBNo ROA
2804:7c08:4000::/34RADBNo ROA

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.