Network · data from 2026-11-12
AS29209 SPBMTS-AS MTS PJSC
Registry name: SPBMTS-AS MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29209, 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.
| 217.66.144.0/22 | Valid | None | 671 100% |
AS-SET
AS29209 isn't in PeeringDB, where networks name their 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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 217.66.144.0/22 | No route object for it. Add a route object with origin AS29209 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29209 whose prefix no peer sees AS29209 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 213.87.208.0/23 | RIPE | Invalid: origin |
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.