bgpreport

Network · data from 2026-11-12

AS264170 Winet Brasil

Registry name: AS264170 - Winet Brasil, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264170, 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.185.74.0/24 No ROA Other IRR onlyRADB 671 100% 66
45.185.75.0/24 No ROA Other IRR onlyRADB 671 100% 66
138.99.60.0/23 No ROA Other IRR onlyALTDB, RADB 671 100% 66
138.99.62.0/23 No ROA Other IRR onlyALTDB, RADB 671 100% 66
45.185.72.0/24 No ROA Other IRR onlyRADB 670 100% 66
45.185.73.0/24 No ROA Other IRR onlyRADB 670 100% 66
2804:2390::/32 No ROA Other IRR onlyALTDB, RADB 632 99% 67
2804:2390::/36 No ROA Other IRR onlyRADB 632 99% 67
138.99.61.0/24 No ROA Other IRR onlyALTDB, RADB 205 30% 54
138.99.60.0/24 No ROA Other IRR onlyALTDB, RADB 203 30% 54
138.99.62.0/24 No ROA Other IRR onlyALTDB, RADB 202 30% 54
138.99.63.0/24 No ROA Other IRR onlyALTDB, RADB 202 30% 54

AS-SET

PeeringDB's irr_as_set for AS264170: AS-AS264170. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS264170 isn't in the set, or no route object for AS264170 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS264170 in itNot covered
AS-AS264170 ALTDB 451551 Yes 0

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

  • ROA: none12
  • Route object: RIR12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.185.74.0/24No ROA covers it. Add a ROA for AS264170, maxLength 24.671 of 673
Route object: RIR45.185.74.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.185.75.0/24No ROA covers it. Add a ROA for AS264170, maxLength 24.671 of 673
Route object: RIR45.185.75.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none138.99.60.0/23No ROA covers it. Add a ROA for AS264170, maxLength 23.671 of 673
Route object: RIR138.99.60.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none138.99.62.0/23No ROA covers it. Add a ROA for AS264170, maxLength 23.671 of 673
Route object: RIR138.99.62.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.185.72.0/24No ROA covers it. Add a ROA for AS264170, maxLength 24.670 of 673
Route object: RIR45.185.72.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.185.73.0/24No ROA covers it. Add a ROA for AS264170, maxLength 24.670 of 673
Route object: RIR45.185.73.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:2390::/32No ROA covers it. Add a ROA for AS264170, maxLength 32.632 of 636
Route object: RIR2804:2390::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.632 of 636
ROA: none2804:2390::/36No ROA covers it. Add a ROA for AS264170, maxLength 36.632 of 636
Route object: RIR2804:2390::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none138.99.61.0/24No ROA covers it. Add a ROA for AS264170, maxLength 24.205 of 673
Route object: RIR138.99.61.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.205 of 673
ROA: none138.99.60.0/24No ROA covers it. Add a ROA for AS264170, maxLength 24.203 of 673
Route object: RIR138.99.60.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.203 of 673
ROA: none138.99.62.0/24No ROA covers it. Add a ROA for AS264170, maxLength 24.202 of 673
Route object: RIR138.99.62.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.202 of 673
ROA: none138.99.63.0/24No ROA covers it. Add a ROA for AS264170, maxLength 24.202 of 673
Route object: RIR138.99.63.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.202 of 673

Route objects not announced

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

138.99.60.0/22ALTDB, RADBNo ROA
209.14.67.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.