bgpreport

Network · data from 2026-11-12

AS268365 VALDEMIR DE SANTANA ROLIM - ELETROTEL

Registry name: AS268365 - ELETROTEL COMERCIO, SERVICO E PROVEDOR LTDA, BR · PeeringDB

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

Announced routes

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

45.239.147.0/24 No ROA Other IRR onlyRADB 672 100% 67
45.239.144.0/24 No ROA Other IRR onlyRADB 670 100% 66
45.239.146.0/24 No ROA Other IRR onlyRADB 664 99% 67
2804:5008::/34 No ROA Other IRR onlyRADB 635 100% 70
2804:5008:8000::/34 No ROA Other IRR onlyRADB 635 100% 70
2804:5008:c000::/34 No ROA Other IRR onlyRADB 635 100% 70
2804:5008:4000::/34 No ROA Other IRR onlyRADB 3 0%low visibility 3
45.239.145.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS268365'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 21 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none45.239.147.0/24No ROA covers it. Add a ROA for AS268365, maxLength 24.672 of 673
Route object: RIR45.239.147.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.239.144.0/24No ROA covers it. Add a ROA for AS268365, maxLength 24.670 of 673
Route object: RIR45.239.144.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.239.146.0/24No ROA covers it. Add a ROA for AS268365, maxLength 24.664 of 673
Route object: RIR45.239.146.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none2804:5008::/34No ROA covers it. Add a ROA for AS268365, maxLength 34.635 of 636
Route object: RIR2804:5008::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:5008:8000::/34No ROA covers it. Add a ROA for AS268365, maxLength 34.635 of 636
Route object: RIR2804:5008:8000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:5008:c000::/34No ROA covers it. Add a ROA for AS268365, maxLength 34.635 of 636
Route object: RIR2804:5008:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:5008:4000::/34No ROA covers it. Add a ROA for AS268365, maxLength 34.3 of 636
Route object: RIR2804:5008:4000::/34Route object only in RADB. Add it in the RIR database for the space.3 of 636
ROA: none45.239.145.0/24No ROA covers it. Add a ROA for AS268365, maxLength 24.2 of 673
Route object: RIR45.239.145.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.239.144.0/22RADBNo ROA
45.239.144.0/23RADBNo ROA
45.239.146.0/23RADBNo ROA
2804:5008::/32RADBNo ROA
2804:5008::/33RADBNo 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.