Network · data from 2026-11-12
AS61622 VIA MS
Registry name: AS61622 - VIA MS SOLUCOES DIGITAIS, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61622, 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:9220::/32 | No ROA | Other IRR onlyRADB, TC | 633 100% |
| 2804:9220::/33 | No ROA | Other IRR onlyTC | 353 56% |
| 2804:9220:8000::/33 | No ROA | Other IRR onlyTC | 353 56% |
| 136.175.22.0/23 | Valid | Other origin onlycovered by 136.175.20.0/22 | 197 29% |
| 136.175.20.0/24 | Valid | Other origin onlycovered by 136.175.20.0/23 | 2 0%low visibility |
| 136.175.21.0/24 | Valid | Other origin onlycovered by 136.175.20.0/23 | 2 0%low visibility |
| 136.175.23.0/24 | Valid | Other origin onlycovered by 136.175.20.0/22 | 2 0%low visibility |
| 38.52.149.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 136.175.20.0/23 | Valid | Other IRR onlyRADB | 197 29% |
| 136.175.20.0/22 | Valid | RIR databaseARIN, RADB | 672 100% |
| 38.225.241.0/24 | Valid | RIR databaseARIN | 671 100% |
| 200.180.170.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS61622: AS61622:AS-ALL. 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 (AS61622 isn't in the set, or no route object for AS61622 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.
| Name | Database | ASNs | Sets | AS61622 in it | Not covered |
|---|---|---|---|---|---|
| AS61622:AS-ALL | TClists itself further down | 48 | 16 | 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 31 are in fix.csv.
- ROA: none3
- Route object: none4
- Route object: RIR5
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:9220::/32 | No ROA covers it. Add a ROA for AS61622, maxLength 32. |
| Route object: RIR | 2804:9220::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:9220::/33 | No ROA covers it. Add a ROA for AS61622, maxLength 33. |
| Route object: RIR | 2804:9220::/33 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 2804:9220:8000::/33 | No ROA covers it. Add a ROA for AS61622, maxLength 33. |
| Route object: RIR | 2804:9220:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: none | 136.175.22.0/23 | Route objects for it name AS834. A route object for 136.175.20.0/22 with origin AS61622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61622 in the RIR database for the space. |
| Route object: none | 136.175.20.0/24 | Route objects for it name AS834. A route object for 136.175.20.0/23 with origin AS61622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61622 in the RIR database for the space. |
| Route object: none | 136.175.21.0/24 | Route objects for it name AS834. A route object for 136.175.20.0/23 with origin AS61622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61622 in the RIR database for the space. |
| Route object: none | 136.175.23.0/24 | Route objects for it name AS834. A route object for 136.175.20.0/22 with origin AS61622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61622 in the RIR database for the space. |
| Route object: RIR | 38.52.149.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 136.175.20.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61622 whose prefix no peer sees AS61622 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 136.175.22.0/24 | RADB | Valid |
| 2804:9220::/34 | TC | No ROA |
| 2804:9220::/35 | TC | No ROA |
| 2804:9220::/36 | TC | No ROA |
| 2804:9220::/37 | TC | No ROA |
| 2804:9220::/38 | TC | No ROA |
| 2804:9220::/39 | TC | No ROA |
| 2804:9220::/40 | TC | No ROA |
| 2804:9220::/41 | TC | No ROA |
| 2804:9220::/42 | TC | No ROA |
| 2804:9220::/43 | TC | No ROA |
| 2804:9220::/44 | TC | No ROA |
| 2804:9220::/45 | TC | No ROA |
| 2804:9220::/46 | TC | No ROA |
| 2804:9220::/47 | TC | No ROA |
| 2804:9220::/48 | TC | No ROA |
| 2804:9220:4000::/34 | TC | No ROA |
| 2804:9220:8000::/34 | TC | No ROA |
| 2804:9220:c000::/34 | TC | No 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.