Network · data from 2026-11-12
AS59460 M3.NET
Registry name: ASN-M3NET M3.NET Sp. zoo, PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59460, 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.241.32.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.241.32.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.241.33.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.241.34.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.241.35.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.135.192.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.135.192.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.135.193.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.135.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.135.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.146.4.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.146.4.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.146.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.146.6.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS59460: AS-M3NET. 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 (AS59460 isn't in the set, or no route object for AS59460 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 | AS59460 in it | Not covered |
|---|---|---|---|---|---|
| AS-M3NET | RIPElists itself further down | 53 | 14 | 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 5 are in fix.csv.
- ROA: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.241.32.0/22 | No ROA covers it. Add a ROA for AS59460, maxLength 22. |
| ROA: none | 91.241.32.0/24 | No ROA covers it. Add a ROA for AS59460, maxLength 24. |
| ROA: none | 91.241.33.0/24 | No ROA covers it. Add a ROA for AS59460, maxLength 24. |
| ROA: none | 91.241.34.0/24 | No ROA covers it. Add a ROA for AS59460, maxLength 24. |
| ROA: none | 91.241.35.0/24 | No ROA covers it. Add a ROA for AS59460, maxLength 24. |
Route objects not announced
Every route object with origin AS59460 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.