bgpreport

Network · data from 2026-11-12

AS268817 FIBER TELECOMUNICACOES

Registry name: AS268817 - Acelera Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268817, 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:5b14:4100::/44 No ROA Nonecovered by 2804:5b14:4000::/36 636 100% 67
2804:5b14:4200::/40 No ROA Nonecovered by 2804:5b14:4000::/36 631 99% 67
45.173.164.0/24 No ROA Other IRR onlyRADB 672 100% 66
45.173.164.0/23 No ROA Other IRR onlyRADB 671 100% 66
45.173.167.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.173.166.0/24 No ROA Other IRR onlyRADB 670 100% 67
45.173.165.0/24 No ROA Other IRR onlyRADB 667 99% 66
2804:5b14:2000::/35 No ROA Other IRR onlyRADB 635 100% 67
2804:5b14::/35 No ROA Other IRR onlyRADB 634 100% 67
2804:5b14::/34 No ROA Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS268817's PeeringDB record names no 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 50 are in fix.csv.

  • ROA: none10
  • Route object: none2
  • Route object: RIR8
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
ROA: none2804:5b14:4100::/44No ROA covers it. Add a ROA for AS268817, maxLength 44.636 of 636
Route object: none2804:5b14:4100::/44No route object for it. A route object for 2804:5b14:4000::/36 with origin AS268817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268817 in the RIR database for the space.636 of 636
ROA: none2804:5b14:4200::/40No ROA covers it. Add a ROA for AS268817, maxLength 40.631 of 636
Route object: none2804:5b14:4200::/40No route object for it. A route object for 2804:5b14:4000::/36 with origin AS268817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268817 in the RIR database for the space.631 of 636
ROA: none45.173.164.0/24No ROA covers it. Add a ROA for AS268817, maxLength 24.672 of 673
Route object: RIR45.173.164.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.173.164.0/23No ROA covers it. Add a ROA for AS268817, maxLength 23.671 of 673
Route object: RIR45.173.164.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.173.167.0/24No ROA covers it. Add a ROA for AS268817, maxLength 24.671 of 673
Route object: RIR45.173.167.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.173.166.0/24No ROA covers it. Add a ROA for AS268817, maxLength 24.670 of 673
Route object: RIR45.173.166.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.173.165.0/24No ROA covers it. Add a ROA for AS268817, maxLength 24.667 of 673
Route object: RIR45.173.165.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:5b14:2000::/35No ROA covers it. Add a ROA for AS268817, maxLength 35.635 of 636
Route object: RIR2804:5b14:2000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:5b14::/35No ROA covers it. Add a ROA for AS268817, maxLength 35.634 of 636
Route object: RIR2804:5b14::/35Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:5b14::/34No ROA covers it. Add a ROA for AS268817, maxLength 34.1 of 636
Route object: RIR2804:5b14::/34Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

45.173.164.0/22RADB, TCNo ROA
45.173.166.0/23RADBNo ROA
2804:5b14::/32RADB, TCNo ROA
2804:5b14::/33RADBNo ROA
2804:5b14::/36RADBNo ROA
2804:5b14:1000::/36RADBNo ROA
2804:5b14:2000::/36RADBNo ROA
2804:5b14:3000::/36RADBNo ROA
2804:5b14:4000::/34RADBNo ROA
2804:5b14:4000::/35RADBNo ROA
2804:5b14:4000::/36RADBNo ROA
2804:5b14:5000::/36RADBNo ROA
2804:5b14:6000::/35RADBNo ROA
2804:5b14:6000::/36RADBNo ROA
2804:5b14:7000::/36RADBNo ROA
2804:5b14:8000::/33RADBNo ROA
2804:5b14:8000::/34RADBNo ROA
2804:5b14:8000::/35RADBNo ROA
2804:5b14:8000::/36RADBNo ROA
2804:5b14:9000::/36RADBNo ROA
2804:5b14:a000::/35RADBNo ROA
2804:5b14:a000::/36RADBNo ROA
2804:5b14:b000::/36RADBNo ROA
2804:5b14:c000::/34RADBNo ROA
2804:5b14:c000::/35RADBNo ROA
2804:5b14:c000::/36RADBNo ROA
2804:5b14:d000::/36RADBNo ROA
2804:5b14:e000::/35RADBNo ROA
2804:5b14:e000::/36RADBNo ROA
2804:5b14:f000::/36RADBNo 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.