bgpreport

Network · data from 2026-11-12

AS269521 AS269521 - DUNETISP INTERNET LTDA

Registry name: AS269521 - DUNETISP INTERNET LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269521, 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.188.116.0/23 Valid Other IRR onlyRADB 672 100% 66
45.188.118.0/23 Valid Other IRR onlyRADB 672 100% 66
45.188.116.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
45.188.118.0/24 Valid Other IRR onlyRADB 671 100% 66
45.188.119.0/24 Valid Other IRR onlyRADB 670 100% 66
2804:65e4::/32 Valid Other IRR onlyRADB, TC 633 100% 67
45.188.116.0/24 Valid Other IRR onlyRADB 19 3%low visibility 9
45.188.117.0/24 Valid Other IRR onlyRADB 19 3%low visibility 9

AS-SET

AS269521 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 38 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
Route object: RIR45.188.116.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.188.118.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.188.116.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.188.118.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.188.119.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:65e4::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR45.188.116.0/24Route object only in RADB. Add it in the RIR database for the space.19 of 673
Route object: RIR45.188.117.0/24Route object only in RADB. Add it in the RIR database for the space.19 of 673

Route objects not announced

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

2804:65e4::/33RADBValid
2804:65e4::/34RADBValid
2804:65e4::/35RADBValid
2804:65e4::/36RADBValid
2804:65e4:1000::/36RADBValid
2804:65e4:2000::/35RADBValid
2804:65e4:2000::/36RADBValid
2804:65e4:3000::/36RADBValid
2804:65e4:4000::/34RADBValid
2804:65e4:4000::/35RADBValid
2804:65e4:4000::/36RADBValid
2804:65e4:5000::/36RADBValid
2804:65e4:6000::/35RADBValid
2804:65e4:6000::/36RADBValid
2804:65e4:7000::/36RADBValid
2804:65e4:8000::/33RADBValid
2804:65e4:8000::/34RADBValid
2804:65e4:8000::/35RADBValid
2804:65e4:8000::/36RADBValid
2804:65e4:9000::/36RADBValid
2804:65e4:a000::/35RADBValid
2804:65e4:a000::/36RADBValid
2804:65e4:b000::/36RADBValid
2804:65e4:c000::/34RADBValid
2804:65e4:c000::/35RADBValid
2804:65e4:c000::/36RADBValid
2804:65e4:d000::/36RADBValid
2804:65e4:e000::/35RADBValid
2804:65e4:e000::/36RADBValid
2804:65e4:f000::/36RADBValid

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.