bgpreport

Network · data from 2026-11-12

AS271454 AS271454 - iNEW Telecom LTDA

Registry name: AS271454 - iNEW Telecom LTDA, BR · not in PeeringDB

1IPv4 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 AS271454, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271454, 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.4.0/22 Valid Other IRR onlyRADB, TC 668 99% 66
2804:7bc8::/32 Valid Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS271454 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 2 are in fix.csv.

  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: RIR181.233.4.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:7bc8::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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