Network · data from 2026-11-12
AS52872 VOANET Telecomunicações Ltda.
Registry name: AS52872 - Voafibra Comunicacao, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52872, 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.
| 177.128.192.0/23 | Valid | Nonecovered by 177.128.192.0/22 | 669 99% |
| 177.128.194.0/23 | Valid | Nonecovered by 177.128.192.0/22 | 669 99% |
| 177.128.198.0/23 | Valid | Nonecovered by 177.128.196.0/22 | 669 99% |
| 168.0.236.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 168.0.238.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 168.197.136.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 168.197.136.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 168.197.137.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 168.197.138.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 177.128.192.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 177.128.196.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 168.0.236.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 168.0.236.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 177.128.194.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 177.128.195.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 168.197.138.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 177.128.192.0/21 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 177.128.196.0/23 | Valid | Other IRR onlyRADB | 669 99% |
| 2804:88c::/32 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 2804:88c::/33 | Valid | Other IRR onlyRADB | 367 58% |
| 2804:88c:8000::/33 | Valid | Other IRR onlyRADB | 367 58% |
| 168.0.239.0/24 | Valid | Other IRR onlyRADB | 205 30% |
| 177.128.192.0/24 | Valid | Other IRR onlyRADB | 166 25% |
| 177.128.193.0/24 | Valid | Other IRR onlyRADB | 166 25% |
| 177.128.196.0/24 | Valid | Other IRR onlyRADB | 165 25% |
| 177.128.197.0/24 | Valid | Other IRR onlyRADB | 165 25% |
| 177.128.198.0/24 | Valid | Other IRR onlyRADB | 165 25% |
| 168.197.136.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 177.128.199.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS52872: AS-VOANET-52872. 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 (AS52872 isn't in the set, or no route object for AS52872 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 | AS52872 in it | Not covered |
|---|---|---|---|---|---|
| AS-VOANET-52872 | RADBlists itself further down5 member sets in no database: AS-GILNET, AS-IVITELECOM-CLIENTS-DDOS, AS262769:AS-GEEKNET-BR, AS264592:AS-ENLACE-ALL, AS52872:AS-52872 | 400 | 96 | Yes | 0 |
| TC (also)2 member sets in no database: AS-GILNET, AS-IVITELECOM | 61 | 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 37 are in fix.csv.
- Route object: none3
- Route object: RIR26
- AS-SET: missing member5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 177.128.192.0/23 | No route object for it. A route object for 177.128.192.0/22 with origin AS52872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52872 in the RIR database for the space. |
| Route object: none | 177.128.194.0/23 | No route object for it. A route object for 177.128.192.0/22 with origin AS52872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52872 in the RIR database for the space. |
| Route object: none | 177.128.198.0/23 | No route object for it. A route object for 177.128.196.0/22 with origin AS52872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52872 in the RIR database for the space. |
| Route object: RIR | 168.0.236.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.238.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.136.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.136.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.137.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.138.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.192.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.196.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.236.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.236.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.194.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.195.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.138.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.192.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.196.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:88c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:88c::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:88c:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.192.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.193.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.196.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.197.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.198.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.136.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.199.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-VOANET-52872 | AS-VOANET-52872 (RADB) lists AS-GILNET; no IRR database read has it. |
| AS-SET: missing member | AS-VOANET-52872 | AS-VOANET-52872 (RADB) lists AS-IVITELECOM-CLIENTS-DDOS; no IRR database read has it. |
| AS-SET: missing member | AS-VOANET-52872 | AS-VOANET-52872 (RADB) lists AS262769:AS-GEEKNET-BR; no IRR database read has it. |
| AS-SET: missing member | AS-VOANET-52872 | AS-VOANET-52872 (RADB) lists AS264592:AS-ENLACE-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-VOANET-52872 | AS-VOANET-52872 (RADB) lists AS52872:AS-52872; no IRR database read has it. |
Route objects not announced
Route objects with origin AS52872 whose prefix no peer sees AS52872 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.0.237.0/24 | RADB | Valid |
| 168.0.238.0/24 | RADB | Valid |
| 168.197.139.0/24 | RADB | Valid |
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.