bgpreport

Network · data from 2026-11-12

AS268683 AS268683 - rede banda larga

Registry name: AS268683 - rede banda larga, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268683, 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:5500:8000::/34 No ROA Other IRR onlyRADB 636 100% 67
45.165.165.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 67
45.165.166.0/23 Valid Other IRR onlyALTDB, RADB 671 100% 67
45.165.164.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 67
2804:5500::/34 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS268683 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 39 are in fix.csv.

  • ROA: none1
  • Route object: RIR5
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
ROA: none2804:5500:8000::/34No ROA covers it. Add a ROA for AS268683, maxLength 34.636 of 636
Route object: RIR2804:5500:8000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR45.165.165.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.165.166.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.165.164.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:5500::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.165.164.0/22ALTDB, RADB, TCNo ROA
45.165.164.0/23ALTDB, RADBValid
45.165.166.0/24ALTDB, RADBValid
45.165.167.0/24ALTDB, RADBValid
2804:5500::/32ALTDB, RADB, TCNo ROA
2804:5500::/33RADBNo ROA
2804:5500::/35RADBValid
2804:5500::/36RADBValid
2804:5500:1000::/36RADBValid
2804:5500:2000::/35RADBValid
2804:5500:2000::/36RADBValid
2804:5500:3000::/36RADBValid
2804:5500:4000::/34RADBNo ROA
2804:5500:4000::/35RADBNo ROA
2804:5500:4000::/36RADBNo ROA
2804:5500:5000::/36RADBNo ROA
2804:5500:6000::/35RADBNo ROA
2804:5500:6000::/36RADBNo ROA
2804:5500:7000::/36RADBNo ROA
2804:5500:8000::/33RADBNo ROA
2804:5500:8000::/35RADBNo ROA
2804:5500:8000::/36RADBNo ROA
2804:5500:9000::/36RADBNo ROA
2804:5500:a000::/35RADBNo ROA
2804:5500:a000::/36RADBNo ROA
2804:5500:b000::/36RADBNo ROA
2804:5500:c000::/34RADBNo ROA
2804:5500:c000::/35RADBNo ROA
2804:5500:c000::/36RADBNo ROA
2804:5500:d000::/36RADBNo ROA
2804:5500:e000::/35RADBNo ROA
2804:5500:e000::/36RADBNo ROA
2804:5500: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.