bgpreport

Network · data from 2026-11-12

AS271066 AS271066 - AB NET TELECOM

Registry name: AS271066 - AB NET TELECOM, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271066, 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.64.0/22 No ROA Other IRR onlyALTDB, RADB 669 99% 67
179.48.64.0/23 No ROA Other IRR onlyALTDB, RADB 669 99% 67
179.48.64.0/24 No ROA Other IRR onlyALTDB, RADB 669 99% 67
179.48.65.0/24 No ROA Other IRR onlyALTDB, RADB 669 99% 67
179.48.66.0/23 No ROA Other IRR onlyALTDB, RADB 669 99% 67
179.48.66.0/24 No ROA Other IRR onlyALTDB, RADB 669 99% 67
179.48.67.0/24 No ROA Other IRR onlyALTDB, RADB 668 99% 67

AS-SET

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

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none179.48.64.0/22No ROA covers it. Add a ROA for AS271066, maxLength 22.669 of 673
Route object: RIR179.48.64.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
ROA: none179.48.64.0/23No ROA covers it. Add a ROA for AS271066, maxLength 23.669 of 673
Route object: RIR179.48.64.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
ROA: none179.48.64.0/24No ROA covers it. Add a ROA for AS271066, maxLength 24.669 of 673
Route object: RIR179.48.64.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
ROA: none179.48.65.0/24No ROA covers it. Add a ROA for AS271066, maxLength 24.669 of 673
Route object: RIR179.48.65.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
ROA: none179.48.66.0/23No ROA covers it. Add a ROA for AS271066, maxLength 23.669 of 673
Route object: RIR179.48.66.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
ROA: none179.48.66.0/24No ROA covers it. Add a ROA for AS271066, maxLength 24.669 of 673
Route object: RIR179.48.66.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
ROA: none179.48.67.0/24No ROA covers it. Add a ROA for AS271066, maxLength 24.668 of 673
Route object: RIR179.48.67.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

2804:75bc::/32ALTDB, RADBNo 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.