Network · data from 2026-11-12
AS5429 ТЦ ЮМОС
Registry name: IIP-NET-AS5429 Telecommunications center UMOS, LLC, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS5429, 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.
| 85.89.102.0/24 | No ROA | Nonecovered by 85.89.96.0/20 | 673 100% |
| 85.89.112.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 185.92.140.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 193.108.182.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.178.192.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 217.67.112.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 193.232.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS5429: AS-SET-AS5429. 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 (AS5429 isn't in the set, or no route object for AS5429 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 | AS5429 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-SET-AS5429 | In no IRR database read today. | |||||
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 11 are in fix.csv.
- ROA: none6
- Route object: none1
- AS-SET: not found1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 85.89.102.0/24 | No ROA covers it. Add a ROA for AS5429, maxLength 24. |
| Route object: none | 85.89.102.0/24 | No route object for it. A route object for 85.89.96.0/20 with origin AS5429 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5429 in the RIR database for the space. |
| ROA: none | 85.89.112.0/21 | No ROA covers it. Add a ROA for AS5429, maxLength 21. |
| ROA: none | 185.92.140.0/22 | No ROA covers it. Add a ROA for AS5429, maxLength 22. |
| ROA: none | 193.108.182.0/24 | No ROA covers it. Add a ROA for AS5429, maxLength 24. |
| ROA: none | 195.178.192.0/19 | No ROA covers it. Add a ROA for AS5429, maxLength 19. |
| ROA: none | 217.67.112.0/20 | No ROA covers it. Add a ROA for AS5429, maxLength 20. |
| AS-SET: not found | AS-SET-AS5429 | PeeringDB names AS-SET-AS5429; no IRR database read has it. |
Route objects not announced
Route objects with origin AS5429 whose prefix no peer sees AS5429 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.89.96.0/19 | RIPE | No ROA |
| 85.89.96.0/20 | RIPE | No ROA |
| 2a02:7bc0::/32 | RIPE | 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.