Network · data from 2026-11-12
AS61297 Ante Mediam LLC
Registry name: DATACENTER-UA Ante Mediam LLC, UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61297, 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.126.255.140/32 | Invalid: origin | None | 0 0%low visibility |
| 77.88.192.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 77.88.192.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 77.88.196.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.2.108.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.13.248.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.13.248.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.13.250.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 2a02:ee00::/29 | No ROA | RIR databaseRIPE | 635 100% |
| 178.95.102.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.95.166.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 194.146.115.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.92.66.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 178.95.80.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS61297: AS61297:AS-UA. 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 (AS61297 isn't in the set, or no route object for AS61297 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 | AS61297 in it | Not covered |
|---|---|---|---|---|---|
| AS61297:AS-UA | RIPE | 32 | 5 | Yes | 1 |
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 18 are in fix.csv.
- ROA: origin1
- ROA: none8
- Route object: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.126.255.140/32 | ROAs covering it name AS203394, AS214379, not AS61297. If AS61297 should announce it, add a ROA for AS61297. |
| Route object: none | 185.126.255.140/32 | No route object for it. Add a route object with origin AS61297 in the RIR database for the space. |
| ROA: none | 77.88.192.0/21 | No ROA covers it. Add a ROA for AS61297, maxLength 21. |
| ROA: none | 77.88.192.0/22 | No ROA covers it. Add a ROA for AS61297, maxLength 22. |
| ROA: none | 77.88.196.0/22 | No ROA covers it. Add a ROA for AS61297, maxLength 22. |
| ROA: none | 185.2.108.0/22 | No ROA covers it. Add a ROA for AS61297, maxLength 22. |
| ROA: none | 185.13.248.0/22 | No ROA covers it. Add a ROA for AS61297, maxLength 22. |
| ROA: none | 185.13.248.0/23 | No ROA covers it. Add a ROA for AS61297, maxLength 23. |
| ROA: none | 185.13.250.0/23 | No ROA covers it. Add a ROA for AS61297, maxLength 23. |
| ROA: none | 2a02:ee00::/29 | No ROA covers it. Add a ROA for AS61297, maxLength 29. |
Route objects not announced
Route objects with origin AS61297 whose prefix no peer sees AS61297 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.2.108.0/24 | RIPE | No ROA |
| 185.2.109.0/24 | RIPE | No ROA |
| 185.2.110.0/24 | RIPE | No ROA |
| 185.2.111.0/24 | RIPE | No ROA |
| 185.13.248.0/24 | RIPE | No ROA |
| 185.13.249.0/24 | RIPE | No ROA |
| 185.13.250.0/24 | RIPE | No ROA |
| 185.13.251.0/24 | 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.