bgpreport

Network · data from 2026-11-12

AS271119 AS271119 - LIBRE TELECOM EIRELI

Registry name: AS271119 - LIBRE TELECOM EIRELI, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271119, 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.
179.48.188.0/24 No ROA Other origin onlycovered by 179.48.188.0/22 671 100% 67
179.48.190.0/23 No ROA Other origin onlycovered by 179.48.188.0/22 667 99% 67
179.48.190.0/24 No ROA Other origin onlycovered by 179.48.188.0/22 667 99% 67
179.48.191.0/24 No ROA Other origin onlycovered by 179.48.188.0/22 667 99% 67

AS-SET

AS271119 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 10 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none179.48.188.0/24No ROA covers it. Add a ROA for AS271119, maxLength 24.671 of 673
Route object: none179.48.188.0/24Route objects for it name AS22653. A route object for 179.48.188.0/22 with origin AS271119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271119 in the RIR database for the space.671 of 673
ROA: none179.48.190.0/23No ROA covers it. Add a ROA for AS271119, maxLength 23.667 of 673
Route object: none179.48.190.0/23Route objects for it name AS22653. A route object for 179.48.188.0/22 with origin AS271119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271119 in the RIR database for the space.667 of 673
ROA: none179.48.190.0/24No ROA covers it. Add a ROA for AS271119, maxLength 24.667 of 673
Route object: none179.48.190.0/24Route objects for it name AS22653. A route object for 179.48.188.0/22 with origin AS271119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271119 in the RIR database for the space.667 of 673
ROA: none179.48.191.0/24No ROA covers it. Add a ROA for AS271119, maxLength 24.667 of 673
Route object: none179.48.191.0/24Route objects for it name AS22653. A route object for 179.48.188.0/22 with origin AS271119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271119 in the RIR database for the space.667 of 673

Route objects not announced

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

179.48.188.0/22ALTDBNo ROA
2804:768c::/32ALTDBNo 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.