Network · data from 2026-11-12
AS53196 NetSTAR SOLUÇÕES
Registry name: AS53196 - NETSTAR SOLUCOES LTDA, BR · PeeringDB
17IPv4 routes
100.0% RPKI valid · 29.4% with a route object
8IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
4Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS53196, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS53196, 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.
| 131.100.197.0/24 | Valid | Nonecovered by 131.100.196.0/22 | 328 49% |
| 131.100.199.0/24 | Valid | Nonecovered by 131.100.198.0/23 | 328 49% |
| 170.231.91.0/24 | Valid | Nonecovered by 170.231.88.0/22 | 328 49% |
| 186.232.208.0/24 | Valid | Nonecovered by 186.232.208.0/21 | 328 49% |
| 186.232.209.0/24 | Valid | Nonecovered by 186.232.208.0/21 | 328 49% |
| 186.232.210.0/24 | Valid | Nonecovered by 186.232.208.0/21 | 328 49% |
| 186.232.211.0/24 | Valid | Nonecovered by 186.232.208.0/21 | 328 49% |
| 186.232.212.0/24 | Valid | Nonecovered by 186.232.208.0/21 | 328 49% |
| 186.232.214.0/24 | Valid | Nonecovered by 186.232.208.0/21 | 328 49% |
| 131.100.196.0/23 | Valid | Nonecovered by 131.100.196.0/22 | 327 49% |
| 170.231.88.0/23 | Valid | Nonecovered by 170.231.88.0/22 | 327 49% |
| 170.231.90.0/23 | Valid | Nonecovered by 170.231.88.0/22 | 327 49% |
| 131.100.196.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.231.88.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 186.232.208.0/21 | Valid | Other IRR onlyALTDB, RADB, TC | 672 100% |
| 2804:1d1c:c2::/48 | Valid | Other IRR onlyTC | 635 100% |
| 2804:1d1c::/33 | Valid | Other IRR onlyTC | 634 100% |
| 2804:1d1c:8000::/33 | Valid | Other IRR onlyTC | 634 100% |
| 2804:1d1c::/32 | Valid | Other IRR onlyRADB, TC | 630 99% |
| 131.100.196.0/24 | Valid | Other IRR onlyRADB | 328 49% |
| 131.100.198.0/23 | Valid | Other IRR onlyRADB | 327 49% |
| 2804:1d1c::/34 | Valid | Other IRR onlyTC | 53 8%low visibility |
| 2804:1d1c:4000::/34 | Valid | Other IRR onlyTC | 53 8%low visibility |
| 2804:1d1c:8000::/34 | Valid | Other IRR onlyTC | 53 8%low visibility |
| 2804:1d1c:c000::/34 | Valid | Other IRR onlyTC | 53 8%low visibility |
AS-SET
PeeringDB's irr_as_set for AS53196: AS53196:AS-ANNOUNCEMENTS. 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 (AS53196 isn't in the set, or no route object for AS53196 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 | AS53196 in it | Not covered |
|---|---|---|---|---|---|
| AS53196:AS-ANNOUNCEMENTS | TC | 5 | 2 | 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 25 are in fix.csv.
- Route object: none12
- Route object: RIR13
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 131.100.197.0/24 | No route object for it. A route object for 131.100.196.0/22 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 131.100.199.0/24 | No route object for it. A route object for 131.100.198.0/23 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 170.231.91.0/24 | No route object for it. A route object for 170.231.88.0/22 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 186.232.208.0/24 | No route object for it. A route object for 186.232.208.0/21 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 186.232.209.0/24 | No route object for it. A route object for 186.232.208.0/21 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 186.232.210.0/24 | No route object for it. A route object for 186.232.208.0/21 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 186.232.211.0/24 | No route object for it. A route object for 186.232.208.0/21 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 186.232.212.0/24 | No route object for it. A route object for 186.232.208.0/21 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 186.232.214.0/24 | No route object for it. A route object for 186.232.208.0/21 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 131.100.196.0/23 | No route object for it. A route object for 131.100.196.0/22 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 170.231.88.0/23 | No route object for it. A route object for 170.231.88.0/22 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: none | 170.231.90.0/23 | No route object for it. A route object for 170.231.88.0/22 with origin AS53196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53196 in the RIR database for the space. |
| Route object: RIR | 131.100.196.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.231.88.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.232.208.0/21 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1d1c:c2::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1d1c::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1d1c:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1d1c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.100.196.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 131.100.198.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1d1c::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1d1c:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1d1c:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1d1c:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS53196 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.