Network · data from 2026-11-12
AS60624 MyNET Sp. z o.o.
Registry name: MYNETPL-AS MyNET Sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60624, 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.
| 91.236.87.0/24 | Invalid: maxLength | Nonecovered by 91.236.86.0/23 | 9 1%low visibility |
| 91.236.86.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.28.248.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.172.87.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.236.84.0/23 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS60624: AS-MYNETPL. 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 (AS60624 isn't in the set, or no route object for AS60624 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 | AS60624 in it | Not covered |
|---|---|---|---|---|---|
| AS-MYNETPL | RIPE | 1 | 1 | 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 7 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 91.236.87.0/24 | ROA 91.236.86.0/23 AS60624 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 91.236.87.0/24. |
| Route object: none | 91.236.87.0/24 | No route object for it. A route object for 91.236.86.0/23 with origin AS60624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60624 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60624 whose prefix no peer sees AS60624 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.236.84.0/22 | RIPE | No ROA |
| 185.28.248.0/23 | RIPE | Invalid: maxLength |
| 185.28.251.0/24 | RIPE | Invalid: maxLength |
| 2a04:3c80::/29 | RIPE | No ROA |
| 2a10:f781:10:9a5a::/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.