bgpreport

Network · data from 2026-11-12

AS271744 AS271744 - Alfacom telecomunicoes e multimidia LTDA

Registry name: AS271744 - Alfacom telecomunicoes e multimidia LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271744, 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.

200.150.244.0/23 No ROA Nonecovered by 200.150.244.0/22 670 100% 66
200.150.247.0/24 No ROA Nonecovered by 200.150.246.0/23 64 10%low visibility 21
200.150.244.0/22 No ROA Other IRR onlyALTDB, RADB 670 100% 66
200.150.246.0/23 No ROA Other IRR onlyALTDB 670 100% 66
200.150.246.0/24 No ROA Other IRR onlyALTDB 64 10%low visibility 21
200.150.245.0/24 No ROA Other IRR onlyALTDB, RADB 63 9%low visibility 21
2804:8054::/32 No ROA Other IRR onlyALTDB, RADB 2 0%low visibility 2
2804:8054:1000::/40 No ROA Other IRR onlyALTDB, RADB 1 0%low visibility 1
2804:8054:1100::/40 No ROA Other IRR onlyALTDB 1 0%low visibility 1

AS-SET

AS271744 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 23 are in fix.csv.

  • ROA: none9
  • Route object: none2
  • Route object: RIR7
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none200.150.244.0/23No ROA covers it. Add a ROA for AS271744, maxLength 23.670 of 673
Route object: none200.150.244.0/23No route object for it. A route object for 200.150.244.0/22 with origin AS271744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271744 in the RIR database for the space.670 of 673
ROA: none200.150.247.0/24No ROA covers it. Add a ROA for AS271744, maxLength 24.64 of 673
Route object: none200.150.247.0/24No route object for it. A route object for 200.150.246.0/23 with origin AS271744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271744 in the RIR database for the space.64 of 673
ROA: none200.150.244.0/22No ROA covers it. Add a ROA for AS271744, maxLength 22.670 of 673
Route object: RIR200.150.244.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.150.246.0/23No ROA covers it. Add a ROA for AS271744, maxLength 23.670 of 673
Route object: RIR200.150.246.0/23Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none200.150.246.0/24No ROA covers it. Add a ROA for AS271744, maxLength 24.64 of 673
Route object: RIR200.150.246.0/24Route object only in ALTDB. Add it in the RIR database for the space.64 of 673
ROA: none200.150.245.0/24No ROA covers it. Add a ROA for AS271744, maxLength 24.63 of 673
Route object: RIR200.150.245.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.63 of 673
ROA: none2804:8054::/32No ROA covers it. Add a ROA for AS271744, maxLength 32.2 of 636
Route object: RIR2804:8054::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 636
ROA: none2804:8054:1000::/40No ROA covers it. Add a ROA for AS271744, maxLength 40.1 of 636
Route object: RIR2804:8054:1000::/40Route object only in ALTDB, RADB. Add it in the RIR database for the space.1 of 636
ROA: none2804:8054:1100::/40No ROA covers it. Add a ROA for AS271744, maxLength 40.1 of 636
Route object: RIR2804:8054:1100::/40Route object only in ALTDB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

2804:8054:1000::/36RADBNo ROA
2804:8054:2000::/36RADBNo ROA
2804:8054:2000::/40ALTDBNo ROA
2804:8054:2100::/40ALTDBNo ROA
2804:8054:2200::/40ALTDBNo 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.