Mobile operator · Belarus
A1 Belarus ASN, MCC/MNC and IP prefixes
A1 Belarus is a mobile network operator in Belarus, part of A1 Telekom Austria Group. It routes traffic through one autonomous system (AS42772), which announced 402 prefixes at our last probe, and its SIMs carry MCC/MNC 257-01.
- ASNs
- 1
- Prefixes
- 402
- Reviewed
- September 2026
- Country
- Belarus (BY)
- Parent group
- A1 Telekom Austria Group
- ASNs
- AS42772
- MCC / MNC
- 257-01
- Network generations
- 4G LTE
- ASNs confirmed
- 1 of 1
- Announced prefixes
- 402 at probe on 2026-09-06
- Official site
- www.a1.by
Autonomous systems
Mobile network codes
| MCC-MNC | MCC | MNC | Source |
|---|---|---|---|
| 257-01 | 257 | 01 | mcc-mnc.org/networks/257_01 |
About A1 Belarus
A1 Belarus is a mobile operator in Belarus and part of A1 Telekom Austria Group, trading earlier under the brand velcom. The registry records one confirmed mobile ASN, AS42772, held by A1-BY-AS Unitary enterprise A1, and one network code pair, MCC 257 with MNC 01. Its site is a1.by.
The registry holds one ASN for A1 Belarus, AS42772, registered to A1-BY-AS Unitary enterprise A1 and marked as the operator's mobile network with confirmed confidence. At the last probe that ASN announced 383 IPv4 prefixes and 19 IPv6 prefixes, an IPv4 footprint many times the IPv6 one by prefix count. PeeringDB carries a record for it under the former brand name Velcom and sets no network type. LTE radio in Belarus runs over the state wholesale operator beCloud, AS60330, which the registry does not list as an A1 ASN.
An address whose origin ASN is AS42772 is routed by A1 Belarus, and the registry marks that ASN as the operator's mobile network, so handset traffic from this operator originates there. The same ASN carries whatever else the company routes, including fixed and business connections, so the origin tells you the operator rather than the access type. An address originating on beCloud's AS60330 belongs to the wholesale infrastructure holder and not to A1, even where an A1 subscriber uses that radio network.
Research note. Former brand velcom (PeeringDB record for AS42772 is still named 'Velcom'; RIPE whois as-name A1-BY-AS, org ORG-JMDC1-RIPE). A1 Group page states the predecessor company became part of the Group in 2007 and links a1.by. None of the 13 asn.txt candidates belong to A1; all rejected as keyword matches on 'Belarus' (universities, banks, railway, government). 4G/LTE in Belarus is provided over the state wholesale operator beCloud (Belarusian Cloud Technologies LLC, AS60330 BCTBY-AS, confirmed via RIPEstat) per the Ministry of Communications page; that ASN is infrastructure, not listed as an A1 ASN. 5G: a1.by news describes a test standalone 5G network at 3.5 GHz, not listed as a commercial generation. Operator site (a1.by) refused connections from this location; page facts taken from search-indexed content of the cited URLs.
Check whether an IP belongs to A1 Belarus
curl -s "https://stat.ripe.net/data/prefix-overview/data.json?resource=203.0.113.9" | jq '.data.asns'whois -h whois.radb.net -- '-i origin AS42772' | grep ^routeQuestions
- What is A1 Belarus's ASN?
- The registry records one confirmed ASN for A1 Belarus, AS42772, held by A1-BY-AS Unitary enterprise A1 and marked as its mobile network, with RIPEstat as the evidence source. At the last probe the ASN announced 383 IPv4 prefixes and 19 IPv6 prefixes.
- What is the MCC/MNC of A1 Belarus?
- A1 Belarus uses MCC 257, the mobile country code for Belarus, with MNC 01. That is the only network code pair the registry records for the operator. Older references may show the same pair against the earlier velcom brand.
- Is an IP from AS42772 a mobile IP?
- AS42772 is recorded as the mobile ASN of A1 Belarus, so an address originating there sits on the network of the operator that runs its mobile service. The registry does not split the ASN by access type, so the same origin can also carry fixed or business traffic.
Sources
Operator and registry pages used for this entry, followed by the RIPEstat Data API (holder, announced prefixes) and the PeeringDB API (network records).
- [1]https://a1.com/a1-group-and-markets/a1-in-belarus/
- [2]https://stat.ripe.net/data/as-overview/data.json?resource=AS42772
- [3]https://www.peeringdb.com/api/net?asn=42772
- [4]https://mcc-mnc.org/networks/257_01
- [5]https://a1.by/en/services/base-services/zvonki-v-4g/p/4G-calls
- [6]https://www.a1.by/en/company/news/a1-razvernula-pervuyu-v-belarusi-avtonomnuyu-5g-set/p/5g-set
- [7]https://mpt.gov.by/en/node/2733/printable/print
- [8]https://stat.ripe.net/docs/02.data-api/
- [9]https://www.peeringdb.com/apidocs/
ASN and prefix data describe how the operator's networks are registered and announced. They do not identify an individual subscriber or where a device is, since carriers route traffic from many areas through shared gateways.