Network · data from 2026-11-12
AS269396 UNIR TELECOM
Registry name: AS269396 - UNIR TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269396, 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.
| 2804:63fc:8000::/33 | Invalid: maxLength | Nonecovered by 2804:63fc::/32 | 1 0%low visibility |
| 45.184.112.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 2804:63fc::/32 | Valid | Other IRR onlyRADB, TC | 636 100% |
| 45.184.112.0/23 | Valid | Other IRR onlyRADB, TC | 124 18% |
| 45.184.114.0/23 | Valid | Other IRR onlyRADB, TC | 124 18% |
AS-SET
PeeringDB's irr_as_set for AS269396: AS269396. 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 (AS269396 isn't in the set, or no route object for AS269396 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 | AS269396 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS269396 | A single AS number, not a set: AS269396 (this network), 8 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 10 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2804:63fc:8000::/33 | ROA 2804:63fc::/32 AS269396 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:63fc:8000::/33. |
| Route object: none | 2804:63fc:8000::/33 | No route object for it. A route object for 2804:63fc::/32 with origin AS269396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269396 in the RIR database for the space. |
| Route object: RIR | 45.184.112.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:63fc::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.112.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.114.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269396 whose prefix no peer sees AS269396 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.184.112.0/24 | TC | Valid |
| 45.184.113.0/24 | TC | Valid |
| 45.184.114.0/24 | TC | Valid |
| 45.184.115.0/24 | 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.