Network · data from 2026-11-12
AS264342 UPNET PROVEDOR DE ACESSO E TELECOM
Registry name: AS264342 - UPNET PROVEDOR DE ACESSO E TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264342, 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.
| 138.185.156.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 138.185.158.0/23 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 170.245.136.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 138.185.156.0/23 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 170.245.136.0/23 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 170.245.138.0/23 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 2804:2678::/33 | Valid | Other IRR onlyTC | 635 100% |
| 2804:2678:8000::/33 | Valid | Other IRR onlyTC | 635 100% |
| 2804:2678::/32 | Valid | Other IRR onlyRADB, TC | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS264342: AS264342:AS-UPNET. 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 (AS264342 isn't in the set, or no route object for AS264342 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 | AS264342 in it | Not covered |
|---|---|---|---|---|---|
| AS264342:AS-UPNET | 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 21 are in fix.csv.
- Route object: RIR9
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 138.185.156.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.185.158.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.136.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.185.156.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.136.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.138.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2678::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2678:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2678::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264342 whose prefix no peer sees AS264342 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.185.156.0/24 | RADB, TC | Valid |
| 138.185.157.0/24 | RADB, TC | Valid |
| 138.185.158.0/24 | RADB, TC | Valid |
| 138.185.159.0/24 | RADB, TC | Valid |
| 170.245.136.0/24 | RADB, TC | Valid |
| 170.245.137.0/24 | RADB, TC | Valid |
| 170.245.138.0/24 | RADB, TC | Valid |
| 170.245.139.0/24 | RADB, TC | Valid |
| 2804:2678::/34 | TC | Valid |
| 2804:2678:4000::/34 | TC | Valid |
| 2804:2678:8000::/34 | TC | Valid |
| 2804:2678:c000::/34 | TC | 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.