Network · data from 2026-11-12
AS210256 ETMEDIA
Registry name: ETMEDIA ET-MEDIA Krzysztof Palka, Ewa Palka S.C., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS210256, 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.254.7.0/24 | Invalid: origin | None | 2 0%low visibility |
| 91.106.30.212/32 | Invalid: maxLength | Nonecovered by 91.106.30.0/24 | 2 0%low visibility |
| 91.106.30.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS210256: RIPE::AS-ET-MEDIA. 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 (AS210256 isn't in the set, or no route object for AS210256 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 | AS210256 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-ET-MEDIA | RIPE | 1 | 1 | Yes | 2 |
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 5 are in fix.csv.
- ROA: origin1
- ROA: maxLength1
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.254.7.0/24 | ROAs covering it name AS47544, not AS210256. If AS210256 should announce it, add a ROA for AS210256. |
| Route object: none | 185.254.7.0/24 | No route object for it. Add a route object with origin AS210256 in the RIR database for the space. |
| ROA: maxLength | 91.106.30.212/32 | ROA 91.106.30.0/24 AS210256 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.106.30.212/32. |
| Route object: none | 91.106.30.212/32 | No route object for it. A route object for 91.106.30.0/24 with origin AS210256 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS210256 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS210256 whose prefix no peer sees AS210256 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:e747::/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.