Network · data from 2026-11-12
AS264943 VIARAPIDA TELECOMUNICAÇÕES
Registry name: AS264943 - VIARAPIDA TELECOMUNICACOES LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264943, 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.
| 167.250.60.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 168.232.136.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 170.231.200.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 170.244.248.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 2804:3050::/32 | No ROA | Other IRR onlyRADB | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS264943: AS264943:AS-GLOBAL. 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 (AS264943 isn't in the set, or no route object for AS264943 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 | AS264943 in it | Not covered |
|---|---|---|---|---|---|
| AS264943:AS-GLOBAL | RADBlists itself further down1 member set in no database: AS264943:AS-52587 | 89 | 8 | 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 20 are in fix.csv.
- ROA: none5
- Route object: RIR5
- AS-SET: missing member1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 167.250.60.0/22 | No ROA covers it. Add a ROA for AS264943, maxLength 22. |
| Route object: RIR | 167.250.60.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 168.232.136.0/22 | No ROA covers it. Add a ROA for AS264943, maxLength 22. |
| Route object: RIR | 168.232.136.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.231.200.0/22 | No ROA covers it. Add a ROA for AS264943, maxLength 22. |
| Route object: RIR | 170.231.200.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.244.248.0/22 | No ROA covers it. Add a ROA for AS264943, maxLength 22. |
| Route object: RIR | 170.244.248.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:3050::/32 | No ROA covers it. Add a ROA for AS264943, maxLength 32. |
| Route object: RIR | 2804:3050::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS264943:AS-GLOBAL | AS264943:AS-GLOBAL (RADB) lists AS264943:AS-52587; no IRR database read has it. |
Route objects not announced
Route objects with origin AS264943 whose prefix no peer sees AS264943 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 167.250.60.0/23 | RADB | No ROA |
| 167.250.62.0/23 | RADB | No ROA |
| 168.232.136.0/23 | RADB | No ROA |
| 168.232.138.0/23 | RADB | No ROA |
| 168.250.60.0/22 | RADB | No ROA |
| 170.231.200.0/23 | RADB | No ROA |
| 170.231.202.0/23 | RADB | No ROA |
| 170.244.248.0/23 | RADB | No ROA |
| 170.244.250.0/23 | RADB | 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.