bgpreport

Network · data from 2026-11-12

AS262675 Solução Network Provedor

Registry name: AS262675 - Solucao Network Provedor Ltda, BR · PeeringDB

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

Announced routes

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

209.14.24.0/22 No ROA None 2 0%low visibility 2
209.14.24.0/23 No ROA None 2 0%low visibility 2
2804:a44::/34 Valid Nonecovered by 2804:a44::/33 11 2%low visibility 6
2804:a44:4000::/34 Valid Nonecovered by 2804:a44::/33 11 2%low visibility 6
2804:a44:8000::/34 Valid Nonecovered by 2804:a44:8000::/33 11 2%low visibility 6
2804:a44:c000::/34 Valid Nonecovered by 2804:a44:8000::/33 11 2%low visibility 6
190.111.131.0/24 Valid Other IRR onlyRADB 670 100% 67
131.255.52.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
131.255.52.0/23 Valid Other IRR onlyRADB, TC 669 99% 67
131.255.54.0/23 Valid Other IRR onlyRADB, TC 669 99% 67
186.233.228.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
186.233.228.0/23 Valid Other IRR onlyRADB, TC 669 99% 67
186.233.230.0/23 Valid Other IRR onlyRADB, TC 669 99% 67
190.111.128.0/22 Valid Other IRR onlyRADB 668 99% 67
190.111.128.0/23 Valid Other IRR onlyRADB 668 99% 67
190.111.130.0/23 Valid Other IRR onlyRADB 668 99% 67
190.111.130.0/24 Valid Other IRR onlyRADB 668 99% 67
200.2.100.0/22 Valid Other IRR onlyRADB 668 99% 67
200.2.100.0/23 Valid Other IRR onlyRADB 668 99% 67
200.2.102.0/23 Valid Other IRR onlyRADB 668 99% 67
2804:a44::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:a44::/33 Valid Other IRR onlyTC 354 56% 65
2804:a44:8000::/33 Valid Other IRR onlyTC 354 56% 65
131.255.52.0/24 Valid Other IRR onlyRADB, TC 212 32% 57
131.255.53.0/24 Valid Other IRR onlyRADB, TC 212 32% 57
131.255.54.0/24 Valid Other IRR onlyRADB, TC 212 32% 57
131.255.55.0/24 Valid Other IRR onlyRADB, TC 212 32% 57
186.233.231.0/24 Valid Other IRR onlyRADB, TC 212 32% 57
190.111.128.0/24 Valid Other IRR onlyRADB 212 32% 57
190.111.129.0/24 Valid Other IRR onlyRADB 212 32% 57
200.2.100.0/24 Valid Other IRR onlyRADB 212 32% 57
200.2.101.0/24 Valid Other IRR onlyRADB 212 32% 57
200.2.102.0/24 Valid Other IRR onlyRADB 212 32% 57
186.233.228.0/24 Valid Other IRR onlyRADB, TC 211 31% 57
186.233.229.0/24 Valid Other IRR onlyRADB, TC 211 31% 57
186.233.230.0/24 Valid Other IRR onlyRADB, TC 211 31% 57
200.2.103.0/24 Valid Other IRR onlyRADB 211 31% 57

AS-SET

PeeringDB's irr_as_set for AS262675: AS-SOLUCAO. 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 (AS262675 isn't in the set, or no route object for AS262675 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 objectsAS262675 in itNot covered
AS-SOLUCAO RADB 608829 Yes 2

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: none2
  • Route object: none6
  • Route object: RIR31
ChangePrefix or setDetailFull-table peers
ROA: none209.14.24.0/22No ROA covers it. Add a ROA for AS262675, maxLength 22.2 of 673
Route object: none209.14.24.0/22No route object for it. Add a route object with origin AS262675 in the RIR database for the space.2 of 673
ROA: none209.14.24.0/23No ROA covers it. Add a ROA for AS262675, maxLength 23.2 of 673
Route object: none209.14.24.0/23No route object for it. Add a route object with origin AS262675 in the RIR database for the space.2 of 673
Route object: none2804:a44::/34No route object for it. A route object for 2804:a44::/33 with origin AS262675 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262675 in the RIR database for the space.11 of 636
Route object: none2804:a44:4000::/34No route object for it. A route object for 2804:a44::/33 with origin AS262675 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262675 in the RIR database for the space.11 of 636
Route object: none2804:a44:8000::/34No route object for it. A route object for 2804:a44:8000::/33 with origin AS262675 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262675 in the RIR database for the space.11 of 636
Route object: none2804:a44:c000::/34No route object for it. A route object for 2804:a44:8000::/33 with origin AS262675 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262675 in the RIR database for the space.11 of 636
Route object: RIR190.111.131.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR131.255.52.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR131.255.52.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR131.255.54.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.233.228.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.233.228.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.233.230.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR190.111.128.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR190.111.128.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR190.111.130.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR190.111.130.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.2.100.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.2.100.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.2.102.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:a44::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:a44::/33Route object only in TC. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:a44:8000::/33Route object only in TC. Add it in the RIR database for the space.354 of 636
Route object: RIR131.255.52.0/24Route object only in RADB, TC. Add it in the RIR database for the space.212 of 673
Route object: RIR131.255.53.0/24Route object only in RADB, TC. Add it in the RIR database for the space.212 of 673
Route object: RIR131.255.54.0/24Route object only in RADB, TC. Add it in the RIR database for the space.212 of 673
Route object: RIR131.255.55.0/24Route object only in RADB, TC. Add it in the RIR database for the space.212 of 673
Route object: RIR186.233.231.0/24Route object only in RADB, TC. Add it in the RIR database for the space.212 of 673
Route object: RIR190.111.128.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR190.111.129.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR200.2.100.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR200.2.101.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR200.2.102.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR186.233.228.0/24Route object only in RADB, TC. Add it in the RIR database for the space.211 of 673
Route object: RIR186.233.229.0/24Route object only in RADB, TC. Add it in the RIR database for the space.211 of 673
Route object: RIR186.233.230.0/24Route object only in RADB, TC. Add it in the RIR database for the space.211 of 673
Route object: RIR200.2.103.0/24Route object only in RADB. Add it in the RIR database for the space.211 of 673

Route objects not announced

Every route object with origin AS262675 is announced.

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.