Network · data from 2026-11-12
AS47989 Mosinfocom
Registry name: MOSINFOCOM-AS Mosinfocom Llc, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47989, 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.
| 185.134.33.0/24 | No ROA | Nonecovered by 185.134.32.0/22 | 673 100% |
| 2a03:79a0:8::/48 | No ROA | Nonecovered by 2a03:79a0::/32 | 636 100% |
| 94.126.152.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 185.134.32.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 2a03:79a0::/32 | No ROA | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS47989: AS-MOSINFOCOM. 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 (AS47989 isn't in the set, or no route object for AS47989 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 | AS47989 in it | Not covered |
|---|---|---|---|---|---|
| AS-MOSINFOCOM | RIPElists itself further down | 5 | 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 14 are in fix.csv.
- ROA: none5
- Route object: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.134.33.0/24 | No ROA covers it. Add a ROA for AS47989, maxLength 24. |
| Route object: none | 185.134.33.0/24 | No route object for it. A route object for 185.134.32.0/22 with origin AS47989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47989 in the RIR database for the space. |
| ROA: none | 2a03:79a0:8::/48 | No ROA covers it. Add a ROA for AS47989, maxLength 48. |
| Route object: none | 2a03:79a0:8::/48 | No route object for it. A route object for 2a03:79a0::/32 with origin AS47989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47989 in the RIR database for the space. |
| ROA: none | 94.126.152.0/21 | No ROA covers it. Add a ROA for AS47989, maxLength 21. |
| ROA: none | 185.134.32.0/22 | No ROA covers it. Add a ROA for AS47989, maxLength 22. |
| ROA: none | 2a03:79a0::/32 | No ROA covers it. Add a ROA for AS47989, maxLength 32. |
Route objects not announced
Route objects with origin AS47989 whose prefix no peer sees AS47989 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.126.152.0/22 | RIPE | No ROA |
| 94.126.152.0/24 | RIPE | No ROA |
| 94.126.153.0/24 | RIPE | No ROA |
| 94.126.155.0/24 | RIPE | No ROA |
| 94.126.156.0/22 | RIPE | No ROA |
| 94.126.157.0/24 | RIPE | No ROA |
| 2a03:79a0:1:1::/64 | 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.