bgpreport

Network · data from 2026-11-12

AS271218 AS271218 - AL TELECOM - TELECOMUNICACOES LTDA

Registry name: AS271218 - AL TELECOM - TELECOMUNICACOES LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271218, 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.
177.10.139.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
177.10.136.0/24 No ROA Other IRR onlyRADB, TC 667 99% 67
177.10.137.0/24 No ROA Other IRR onlyRADB, TC 667 99% 67
2804:7810::/39 No ROA Other IRR onlyTC 635 100% 67
2804:7810:700::/40 No ROA Other IRR onlyRADB, TC 631 99% 67
177.10.138.0/24 No ROA Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

AS271218 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 24 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none177.10.139.0/24No ROA covers it. Add a ROA for AS271218, maxLength 24.672 of 673
Route object: RIR177.10.139.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.10.136.0/24No ROA covers it. Add a ROA for AS271218, maxLength 24.667 of 673
Route object: RIR177.10.136.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none177.10.137.0/24No ROA covers it. Add a ROA for AS271218, maxLength 24.667 of 673
Route object: RIR177.10.137.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none2804:7810::/39No ROA covers it. Add a ROA for AS271218, maxLength 39.635 of 636
Route object: RIR2804:7810::/39Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:7810:700::/40No ROA covers it. Add a ROA for AS271218, maxLength 40.631 of 636
Route object: RIR2804:7810:700::/40Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none177.10.138.0/24No ROA covers it. Add a ROA for AS271218, maxLength 24.2 of 673
Route object: RIR177.10.138.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

177.10.136.0/22RADBNo ROA
177.10.136.0/23RADBNo ROA
177.10.138.0/23RADBNo ROA
2804:7810::/32RADBNo ROA
2804:7810::/40TCNo ROA
2804:7810:100::/40TCNo ROA
2804:7810:200::/39TCNo ROA
2804:7810:200::/40TCNo ROA
2804:7810:300::/40TCNo ROA
2804:7810:400::/39TCNo ROA
2804:7810:400::/40TCNo ROA
2804:7810:500::/40TCNo 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.