bgpreport

Network · data from 2026-11-12

AS273728 AS273728 - LIFE&LIFE TELECOM LTDA

Registry name: AS273728 - LIFE&LIFE TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273728, 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.
2804:8b5c::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:8b5c::/33 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
2804:8b5c:4000::/34 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
2804:8b5c:8000::/33 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
2804:8b5c:8000::/34 Valid Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

AS273728 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: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR2804:8b5c::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:8b5c::/33Route object only in RADB, TC. Add it in the RIR database for the space.1 of 636
Route object: RIR2804:8b5c:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.1 of 636
Route object: RIR2804:8b5c:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.1 of 636
Route object: RIR2804:8b5c:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

2804:8b5c::/34RADB, TCValid
2804:8b5c:c000::/34RADB, TCValid
2804:8b5c:c100::/48RADBValid

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.