Network · data from 2026-11-12
AS199715 MSI Telekom Sp. z o.o. Sp. k.
Registry name: ASN-MSITELEKOM MSI Telekom Sp. z o.o. Sp. k., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199715, 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.
| 82.177.105.70/32 | Invalid: maxLength | Nonecovered by 82.177.104.0/22 | 4 1%low visibility |
| 81.15.162.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 81.15.220.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 81.15.228.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.25.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.26.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.28.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.38.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.60.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.62.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.143.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.177.240.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 88.220.56.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 88.220.108.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 88.220.136.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 88.220.162.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.136.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 195.136.216.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 81.15.131.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.134.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.165.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.166.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.177.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.179.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.231.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.247.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.15.253.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS199715's PeeringDB record names no AS-SET.
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 9 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 82.177.105.70/32 | ROA 82.177.104.0/22 AS199715 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 82.177.105.70/32. |
| Route object: none | 82.177.105.70/32 | No route object for it. A route object for 82.177.104.0/22 with origin AS199715 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS199715 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS199715 whose prefix no peer sees AS199715 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.15.164.0/24 | RIPE | Valid |
| 81.15.235.0/24 | RIPE | Valid |
| 82.177.6.0/23 | RIPE | Valid |
| 82.177.85.0/24 | RIPE | Valid |
| 82.177.86.0/24 | RIPE | Valid |
| 82.177.170.0/23 | RIPE | Valid |
| 2a10:f781:10:f32b::/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.