AS57681 ASN-MGTS-USPD2 PJSC Moscow city telephone network
🇷🇺Org handle: ORG-OMct1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
2 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)2.4×10²⁴
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-08 | |
| No ROA | RIPE | 2026-10-08 | |
| No ROA | - | 2026-10-08 | |
| No ROA | - | 2026-10-08 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.2.126.0/23 | 🇷🇺 RU | RIPE | assigned |
All 4 announced prefixes of AS57681 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS57681 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8359MTS PJSC4
Downstreams (7)
Networks whose own prefixes AS57681 passes on: usually its customers.
- AS48096ITGRAD Enterprise Cloud11
- AS2587FREE NET AS2587 OOO FREEnet Group1
- AS44560MIA FKU "GTsSIZI Ministry Of Internal Affairs Of Russia"1
- AS57580SRCI MID RF Federal State Budgetary Institution "Research Center For Information Of The Ministry Of Foreign Affairs Of The Russian Federation"1
- AS200515POLYPLASTIC Gruppa Polyplastic1
- AS202181TAMCOM Transportation Assets Management1
- AS211605VECTORTEL "Vectortel"1
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS57681 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/57681Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/57681" | jq