bgpreport

Network · data from 2026-11-12

AS269468 WinNet Brasil

Registry name: AS269468 - WINNET BRASIL LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269468, 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.186.16.0/22 No ROA Other IRR onlyALTDB, TC 672 100% 67
45.186.17.0/24 No ROA Other IRR onlyALTDB 672 100% 67
45.186.19.0/24 No ROA Other IRR onlyALTDB 672 100% 67
2804:6518::/32 No ROA Other IRR onlyALTDB, RADB, TC 632 99% 67
45.186.16.0/23 No ROA Other IRR onlyALTDB 2 0%low visibility 2
45.186.18.0/23 No ROA Other IRR onlyALTDB 2 0%low visibility 2

AS-SET

AS269468'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 14 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.186.16.0/22No ROA covers it. Add a ROA for AS269468, maxLength 22.672 of 673
Route object: RIR45.186.16.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.186.17.0/24No ROA covers it. Add a ROA for AS269468, maxLength 24.672 of 673
Route object: RIR45.186.17.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none45.186.19.0/24No ROA covers it. Add a ROA for AS269468, maxLength 24.672 of 673
Route object: RIR45.186.19.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none2804:6518::/32No ROA covers it. Add a ROA for AS269468, maxLength 32.632 of 636
Route object: RIR2804:6518::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.632 of 636
ROA: none45.186.16.0/23No ROA covers it. Add a ROA for AS269468, maxLength 23.2 of 673
Route object: RIR45.186.16.0/23Route object only in ALTDB. Add it in the RIR database for the space.2 of 673
ROA: none45.186.18.0/23No ROA covers it. Add a ROA for AS269468, maxLength 23.2 of 673
Route object: RIR45.186.18.0/23Route object only in ALTDB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.186.16.0/24ALTDBNo ROA
45.186.18.0/24ALTDBNo 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.