Network · data from 2026-11-12
AS201427 M2M Uslugi Teleinformatyczne
Registry name: PL-M2M-AS M2M Uslugi Teleinformatyczne Maciej Mackiewicz, PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201427, 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.
| 155.133.103.241/32 | Invalid: maxLength | Nonecovered by 155.133.96.0/21 | 2 0%low visibility |
| 155.133.96.0/21 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS201427: AS201427. 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 (AS201427 isn't in the set, or no route object for AS201427 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 | AS201427 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS201427 | A single AS number, not a set: AS201427 (this network), 2 route objects. | |||||
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 3 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 155.133.103.241/32 | ROA 155.133.96.0/21 AS201427 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 155.133.103.241/32. |
| Route object: none | 155.133.103.241/32 | No route object for it. A route object for 155.133.96.0/21 with origin AS201427 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS201427 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201427 whose prefix no peer sees AS201427 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:8a93::/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.