Network · data from 2026-11-12
AS207744 Primak Evgenii Aleksandrovich
Registry name: MEGALINK-AS Primak Evgenii Aleksandrovich, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207744, 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.
| 188.190.192.0/19 | No ROA | RIR databaseRIPE | 671 100% |
| 188.190.200.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 188.190.204.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 188.190.208.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 188.190.212.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 188.190.217.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 188.190.219.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 188.190.220.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 188.190.222.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 188.190.223.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS207744: AS207744:AS-MIKLLC. 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 (AS207744 isn't in the set, or no route object for AS207744 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 | AS207744 in it | Not covered |
|---|---|---|---|---|---|
| AS207744:AS-MIKLLC | RIPE | 16 | 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 10 are in fix.csv.
- ROA: none10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 188.190.192.0/19 | No ROA covers it. Add a ROA for AS207744, maxLength 19. |
| ROA: none | 188.190.200.0/22 | No ROA covers it. Add a ROA for AS207744, maxLength 22. |
| ROA: none | 188.190.204.0/22 | No ROA covers it. Add a ROA for AS207744, maxLength 22. |
| ROA: none | 188.190.208.0/22 | No ROA covers it. Add a ROA for AS207744, maxLength 22. |
| ROA: none | 188.190.212.0/22 | No ROA covers it. Add a ROA for AS207744, maxLength 22. |
| ROA: none | 188.190.217.0/24 | No ROA covers it. Add a ROA for AS207744, maxLength 24. |
| ROA: none | 188.190.219.0/24 | No ROA covers it. Add a ROA for AS207744, maxLength 24. |
| ROA: none | 188.190.220.0/24 | No ROA covers it. Add a ROA for AS207744, maxLength 24. |
| ROA: none | 188.190.222.0/24 | No ROA covers it. Add a ROA for AS207744, maxLength 24. |
| ROA: none | 188.190.223.0/24 | No ROA covers it. Add a ROA for AS207744, maxLength 24. |
Route objects not announced
Every route object with origin AS207744 is announced.
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.