Network · data from 2026-11-12
AS264471 UNIVERSIDADE ESTADUAL DO OESTE DO PARANA
Registry name: AS264471 - UNIVERSIDADE ESTADUAL DO OESTE DO PARANA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264471, 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.255.84.0/22 | No ROA | Other IRR onlyRADB, TC | 670 100% |
| 131.255.84.0/23 | No ROA | Other IRR onlyTC | 670 100% |
| 131.255.86.0/23 | No ROA | Other IRR onlyTC | 670 100% |
| 2801:80:d90::/48 | No ROA | Other IRR onlyRADB, TC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS264471: AS264471. 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 (AS264471 isn't in the set, or no route object for AS264471 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 | AS264471 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS264471 | A single AS number, not a set: AS264471 (this network), 12 route objects. | |||||
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 16 are in fix.csv.
- ROA: none4
- Route object: RIR4
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 131.255.84.0/22 | No ROA covers it. Add a ROA for AS264471, maxLength 22. |
| Route object: RIR | 131.255.84.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 131.255.84.0/23 | No ROA covers it. Add a ROA for AS264471, maxLength 23. |
| Route object: RIR | 131.255.84.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 131.255.86.0/23 | No ROA covers it. Add a ROA for AS264471, maxLength 23. |
| Route object: RIR | 131.255.86.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 2801:80:d90::/48 | No ROA covers it. Add a ROA for AS264471, maxLength 48. |
| Route object: RIR | 2801:80:d90::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264471 whose prefix no peer sees AS264471 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.201.82.0/24 | RADB | No ROA |
| 200.201.88.0/23 | RADB | No ROA |
| 2801:80:d90::/49 | TC | No ROA |
| 2801:80:d90::/50 | TC | No ROA |
| 2801:80:d90:4000::/50 | TC | No ROA |
| 2801:80:d90:8000::/49 | TC | No ROA |
| 2801:80:d90:8000::/50 | TC | No ROA |
| 2801:80:d90:c000::/50 | TC | 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.