bgpreport

Network · data from 2026-11-12

AS270255 LiFE.iN Telecom

Registry name: AS270255 - NEW ERA TECNOLOGIA LTDA, BR · PeeringDB

14IPv4 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
7Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS270255, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270255, 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.
45.184.88.0/22 Valid Other IRR onlyTC 669 99% 67
45.184.88.0/23 Valid Other IRR onlyTC 669 99% 67
45.184.88.0/24 Valid Other IRR onlyTC 669 99% 67
45.184.90.0/23 Valid Other IRR onlyTC 669 99% 67
200.108.168.0/22 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 668 99% 67
200.108.168.0/23 Valid Other IRR onlyTC 668 99% 67
200.108.170.0/23 Valid Other IRR onlyTC 667 99% 67
2804:6934::/32 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 634 100% 67
45.184.89.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
45.184.90.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
45.184.91.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
200.108.168.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
200.108.169.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
200.108.170.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
200.108.171.0/24 Valid Other IRR onlyTC 2 0%low visibility 2

AS-SET

AS270255'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 15 are in fix.csv.

  • Route object: RIR15
ChangePrefix or setDetailFull-table peers
Route object: RIR45.184.88.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.184.88.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.184.88.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.184.90.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR200.108.168.0/22Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR200.108.168.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR200.108.170.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:6934::/32Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR45.184.89.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.184.90.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.184.91.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR200.108.168.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR200.108.169.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR200.108.170.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR200.108.171.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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