Routing security
AS49476 MTT-AS
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS49476 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 95.169.96.0/19 | No ROA | IRR | 52 |
| 185.13.157.0/24 | RPKI valid | IRR | 51 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS49476 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 185.13.157.0/24 | /32 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS49476 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 80.75.128.0/20 | RIPE | — | MTT-RIPE-MNT | 2020-12-30 | Not announced |
| 80.75.130.0/24 | RIPE | specific route for voip | MTT-RIPE-MNT | 2012-09-14 | Not announced |
| 95.169.96.0/24 | RIPE | MTT BPDN Moscow | MTT-RIPE-MNT | 2011-12-20 | Not announced |
| 95.169.97.0/24 | RIPE | MTT BPDN Yaroslavl | MTT-RIPE-MNT | 2011-12-20 | Not announced |
| 95.169.99.0/24 | RIPE | MTT BPDN Moscow Content Services | MTT-RIPE-MNT | 2011-09-15 | Not announced |
| 95.169.100.0/24 | RIPE | MTT BPDN Barnaul | MTT-RIPE-MNT | 2011-12-20 | Not announced |
| 95.169.101.0/24 | RIPE | MTT Internet Frankfurt | MTT-RIPE-MNT | 2015-02-19 | Not announced |
| 95.169.102.0/24 | RIPE | MTT BPDN Volgograd | MTT-RIPE-MNT | 2011-05-19 | Not announced |
| 95.169.103.0/24 | RIPE | MTT BPDN Ekaterinburg | MTT-RIPE-MNT | 2011-12-20 | Not announced |
| 95.169.107.0/24 | RIPE | MTT BPDN Krasnodar | MTT-RIPE-MNT | 2011-05-30 | Not announced |
| 95.169.108.0/24 | RIPE | MTT BPDN Krasnoyarsk | MTT-RIPE-MNT | 2011-12-20 | Not announced |
| 95.169.110.0/24 | RIPE | MTT BPDN NNovgorod | MTT-RIPE-MNT | 2011-12-20 | Not announced |
| 95.169.111.0/24 | RIPE | MTT BPDN Novosibirsk | MTT-RIPE-MNT | 2012-07-09 | Not announced |
| 95.169.114.0/24 | RIPE | MTT BPDN Samara | MTT-RIPE-MNT | 2011-06-27 | Not announced |
| 95.169.115.0/24 | RIPE | MTT BPDN St.Petersburg | MTT-RIPE-MNT | 2011-04-12 | Not announced |
| 95.169.117.0/24 | RIPE | MTT BPDN Sochi | MTT-RIPE-MNT | 2013-01-24 | Not announced |
| 95.169.118.0/24 | RIPE | MTT BPDN Stavropol | MTT-RIPE-MNT | 2011-05-25 | Not announced |
| 95.169.125.0/24 | RIPE | MTT BPDN Chelyabinsk | MTT-RIPE-MNT | 2011-06-27 | Not announced |
| 95.169.126.0/24 | RIPE | MTT BPDN Rostov-na-Donu | MTT-RIPE-MNT | 2011-02-03 | Not announced |
| 95.169.127.0/24 | RIPE | MTT BPDN Center (Moscow) | MTT-RIPE-MNT | 2011-03-15 | Not announced |
| 2a02:5840:1::/48 | RIPE | Multiregional TransitTelecom IPv6 | MTT-RIPE-MNT | 2016-11-14 | Not announced |
| 2a02:5840:2::/48 | RIPE | Multiregional TransitTelecom IPv6 | MTT-RIPE-MNT | 2016-11-14 | Not announced |
| 2a02:5840:3::/48 | RIPE | Multiregional TransitTelecom IPv6 | MTT-RIPE-MNT | 2016-11-14 | Not announced |
| 2a02:5840:5::/48 | RIPE | Multiregional TransitTelecom IPv6 | MTT-RIPE-MNT | 2016-11-14 | Not announced |
| 2a02:5840:12::/48 | RIPE | Multiregional TransitTelecom IPv6 | MTT-RIPE-MNT | 2016-11-14 | Not announced |
| 95.169.96.0/19 | RIPE | Multiregional Transit Telecom | MTT-RIPE-MNT | 2009-06-25 | Announced |
| 185.13.157.0/24 | RIPE | Routed by AS49476 | GHOSTNET-MNT | 2022-03-10 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS49476 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BLOCK-SET | RIPE | Lists AS49476 as a direct member |
AS-BLOCKED-RU | RIPE | Lists AS49476 as a direct member |
AS-CHFES | RIPE | Lists AS49476 as a direct member |
AS-CIREX | RIPE | Lists AS49476 as a direct member |
AS-DATALAHTI | RIPE | Lists AS49476 as a direct member |
AS-KRS-IX-PEERS | RIPE | Lists AS49476 as a direct member |
AS-MF-KVK | RIPE | Lists AS49476 as a direct member |
AS-MSV | RIPE | Lists AS49476 as a direct member |
AS-MTT-OWN | RIPE | Lists AS49476 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS49476 as a direct member |
AS-ROSTELECOM | RIPE | Lists AS49476 as a direct member |
AS-SAIMANETPEERS-1 | RIPE | Lists AS49476 as a direct member |
AS-SOVAM | RIPE | Lists AS49476 as a direct member |
AS209141:AS-RUCUST | RADB | Lists AS49476 as a direct member |
AS34251:AS-RUFILE | RIPE | Lists AS49476 as a direct member |
AS41194:AS-RASCOM | RIPE | Lists AS49476 as a direct member |
RPKI from rpki-client, validated 2026-10-26 12:04 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-26. Cross-check on bgp.he.net.