Network · data from 2026-11-12
AS264962 Voltec Automação
Registry name: AS264962 - VOLTEC SERVICO DE AUTOMACAO TELECOM ..., BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264962, 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.
| 38.10.103.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 168.232.244.0/22 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 2804:3094::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:3094:1::/48 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:3094:2::/48 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:3094:4::/48 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:3094:5::/48 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 168.232.244.0/23 | Valid | Other IRR onlyRADB, TC | 125 19% |
| 168.232.246.0/24 | Valid | Other IRR onlyRADB, TC | 125 19% |
| 168.232.246.0/23 | Valid | Other IRR onlyTC | 124 18% |
AS-SET
PeeringDB's irr_as_set for AS264962: AS264962: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 (AS264962 isn't in the set, or no route object for AS264962 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 | AS264962 in it | Not covered |
|---|---|---|---|---|---|
| AS264962:AS-ANNOUNCEMENTS | TC | 2 | 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 15 are in fix.csv.
- ROA: none1
- Route object: RIR10
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.10.103.0/24 | No ROA covers it. Add a ROA for AS264962, maxLength 24. |
| Route object: RIR | 38.10.103.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.232.244.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3094::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3094:1::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3094:2::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3094:4::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3094:5::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.232.244.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.232.246.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.232.246.0/23 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264962 whose prefix no peer sees AS264962 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.232.244.0/24 | RADB, TC | Valid |
| 168.232.245.0/24 | RADB, TC | Valid |
| 168.232.247.0/24 | RADB, TC | Valid |
| 2804:3094:3::/48 | 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.