Mobile operator · Bulgaria

Vivacom ASN, MCC/MNC and IP prefixes

Vivacom is a mobile network operator in Bulgaria, part of United Group. It routes traffic through 11 autonomous systems (AS8795, AS8866, AS9127, AS21415, ...), which announced 1,292 prefixes at our last probe, and its SIMs carry MCC/MNC 284-03.

ASNs
11
Prefixes
1,292
Reviewed
September 2026
Country
Bulgaria (BG)
Parent group
United Group
ASNs
AS8795, AS8866, AS9127, AS21415, AS31250, AS34569, AS34754, AS43205, AS43561, AS47771, AS205132
MCC / MNC
284-03
Network generations
2G, 3G, 4G LTE, 5G
ASNs confirmed
11 of 11
Announced prefixes
1,292 at probe on 2026-09-06
Official site
www.vivacom.bg

Autonomous systems

Holder names and prefix counts come from the RIPE NCC's RIPEstat Data API, fetched on 2026-09-06. Role and confidence come from the evidence linked in each row; "confirmed" means a PeeringDB or RIPEstat record, or the operator's own site, names the operator.
Vivacom autonomous systems
ASNHolder (RIPEstat)RoleAnnouncedIPv4 prefixesIPv6 prefixesEvidence
AS8795MOBIKOM Vivacom Bulgaria EADRole not documentedconfirmedyes71source · RIPEstat
AS8866VIVACOM-AS Vivacom Bulgaria EADRole not documentedconfirmedyes1,011234source · RIPEstat
AS9127NETISSAT-AS Vivacom Bulgaria EADRole not documentedconfirmedno00source · RIPEstat
AS21415INTERNETGROUP-AS-BG Vivacom Bulgaria EADRole not documentedconfirmedyes100source · RIPEstat
AS31250OnlineDirect-AS Vivacom Bulgaria EADPeeringDB: Online Direct · Cable/DSL/ISPFixed-lineconfirmedno00source · RIPEstat · PeeringDB
AS34569Networx-BG Vivacom Bulgaria EADPeeringDB: NetworxBG · Cable/DSL/ISPFixed-lineconfirmedyes40source · RIPEstat · PeeringDB
AS34754TELNET-AS Vivacom Bulgaria EADRole not documentedconfirmedyes80source · RIPEstat
AS43205BULSATCOM-BG-AS Vivacom Bulgaria EADPeeringDB: Vivacom Bulgaria EAD-Bulsatcom · Cable/DSL/ISPFixed-lineconfirmedyes10source · RIPEstat · PeeringDB
AS43561NET1-AS Vivacom Bulgaria EADFixed-lineconfirmedyes31source · RIPEstat
AS47771ENTRY-BG-AS Vivacom Bulgaria EADRole not documentedconfirmedyes10source · RIPEstat
AS205132BTC-SEC-AS Vivacom Bulgaria EADRole not documentedconfirmedyes110source · RIPEstat

Mobile network codes

The MCC identifies the country and the MNC identifies the operator inside it. Together they appear in the IMSI of every SIM on the network and in device diagnostics; they are how a handset knows which network it is on.
Vivacom MCC and MNC
MCC-MNCMCCMNCSource
284-0328403en.wikipedia.org/wiki/Mobile_Network_Codes_in_IT

About Vivacom

Vivacom is a Bulgarian operator owned by United Group. The registry records eleven ASNs registered to Vivacom Bulgaria EAD, none with a documented mobile role: four are recorded as fixed and the rest are undocumented, with AS8866 the widest by prefix count. Its MCC/MNC is 284-03.

Eleven ASNs are registered to Vivacom Bulgaria EAD. AS8866 announced 1,011 IPv4 prefixes and 234 IPv6 prefixes at the last probe, far more than any of the others; AS205132 had 11 IPv4 prefixes, AS21415 10, AS34754 8, AS8795 7 with 1 IPv6, AS34569 4, AS43561 3 with 1 IPv6, and AS43205 and AS47771 one each. AS9127 and AS31250 are registered but announce nothing. PeeringDB types AS31250 as Online Direct, AS34569 as NetworxBG and AS43205 as Vivacom Bulgaria EAD-Bulsatcom, all three as Cable/DSL/ISP networks.

An address whose origin ASN is one of these eleven is routed by Vivacom. The registry marks AS31250, AS34569, AS43205 and AS43561 as fixed, and leaves the role of the other seven undocumented, so an address in AS8866, AS8795, AS9127, AS21415, AS34754, AS47771 or AS205132 could be mobile, fixed or enterprise. Vivacom runs 2G, 3G, 4G LTE and 5G, so mobile traffic sits somewhere in this set, but no source in the registry maps it to a specific number, and the ASN alone does not settle it.

Research note. All eleven candidate ASNs resolve in RIPEstat to holder 'Vivacom Bulgaria EAD' (RIPE org ORG-BTCP1-RIPE, the former Bulgarian Telecommunications Company). AS8866 (VIVACOM-AS) is the main NSP record in PeeringDB (org 7820, website vivacom.bg) announcing 1000+ prefixes incl. 95.42.0.0/16 'BG-BTC-20081015'; no fetched source states it carries the consumer mobile network, so role left 'unknown'. AS8795 (MOBIKOM, RIPE descr 'Mobikom Internet Department', 8 prefixes) is the legacy Mobikom ASN; not confirmed as the current mobile network. AS31250, AS34569, AS43205, AS43561 are typed Cable/DSL/ISP in PeeringDB (acquired fixed ISPs Online Direct, Networx, Bulsatcom, NET1) -> fixed. AS9127 (NETISSAT) and AS31250 are registered but not announced per RIPEstat. MCC/MNC: candidate 284-03 confirmed by the Wikipedia MNC table (Vivacom / BTC, operational) and messaggio.com (28403); candidate 284-06 dropped - it does not appear in the Wikipedia table, mcc-mnc-lookup.com, or messaggio.com, none of which attribute MNC 06 to Vivacom. Generations: vivacom.bg coverage page lists 5G (NR), 4G (LTE) with VoLTE, 3G (UMTS), 2G (GSM); vivacom.bg/mobilna-mreja/5g cites speeds that can exceed 1 Gbps and >90% population coverage target. Parent: United Group's own release (31 Jul 2020) states Vivacom officially became part of the United Group family; vivacom.bg footer links to united.group.

Check whether an IP belongs to Vivacom

Look up the origin ASN of the address and compare it with the table above. RIPEstat answers for any address, and the RADB whois mirror lists the routes registered under an ASN.
Origin ASN of an address
curl -s "https://stat.ripe.net/data/prefix-overview/data.json?resource=203.0.113.9" | jq '.data.asns'
Routes registered under AS8795
whois -h whois.radb.net -- '-i origin AS8795' | grep ^route

Questions

What is Vivacom's ASN?
The registry records eleven confirmed ASNs held by Vivacom Bulgaria EAD: AS8795, AS8866, AS9127, AS21415, AS31250, AS34569, AS34754, AS43205, AS43561, AS47771 and AS205132. AS8866 is the widest of them by announced prefixes. No one of them is documented as carrying the mobile network.
What is the MCC/MNC of Vivacom?
Vivacom uses MCC 284, the country code for Bulgaria, with MNC 03, written together as 284-03. The registry records no other MCC/MNC pair for the operator, and this is the identifier a handset reports while attached to the Vivacom network.
Is an IP from AS8866 a mobile IP?
The registry cannot confirm that. AS8866 is registered to Vivacom Bulgaria EAD and announced 1,011 IPv4 prefixes and 234 IPv6 prefixes at the last probe, but no source records its role. An address in it could be mobile, fixed or enterprise, so the ASN alone does not settle the question.

Where Vivacom meets other networks

PeeringDB records Vivacom as a participant at internet exchanges in 5 cities. Each city page lists the exchanges there and the other networks present.

Network cities in Bulgaria: Sofia, Varna.

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. [1]https://www.vivacom.bg/
  2. [2]https://www.vivacom.bg/mobilna-mreja/5g
  3. [3]https://www.vivacom.bg/bg/business/ceni-i-uslugi/mobilni-uslugi/pokritie
  4. [4]https://united.group/united-group-welcomes-vivacom-the-largest-telecom-operator-in-bulgaria/
  5. [5]https://en.wikipedia.org/wiki/Mobile_Network_Codes_in_ITU_region_2xx_(Europe)
  6. [6]https://messaggio.com/messaging/carriers/bulgaria/btc_mobile/
  7. [7]https://mcc-mnc-lookup.com/country/bg/
  8. [8]https://www.peeringdb.com/api/net?asn=8866
  9. [9]https://www.peeringdb.com/api/net?asn=31250
  10. [10]https://www.peeringdb.com/api/net?asn=34569
  11. [11]https://www.peeringdb.com/api/net?asn=43205
  12. [12]https://www.peeringdb.com/api/net?asn=43561
  13. [13]https://stat.ripe.net/data/as-overview/data.json?resource=AS8866
  14. [14]https://stat.ripe.net/data/as-overview/data.json?resource=AS8795
  15. [15]https://stat.ripe.net/data/as-overview/data.json?resource=AS9127
  16. [16]https://stat.ripe.net/data/as-overview/data.json?resource=AS21415
  17. [17]https://stat.ripe.net/data/as-overview/data.json?resource=AS31250
  18. [18]https://stat.ripe.net/data/as-overview/data.json?resource=AS34569
  19. [19]https://stat.ripe.net/data/as-overview/data.json?resource=AS34754
  20. [20]https://stat.ripe.net/data/as-overview/data.json?resource=AS43205
  21. [21]https://stat.ripe.net/data/as-overview/data.json?resource=AS43561
  22. [22]https://stat.ripe.net/data/as-overview/data.json?resource=AS47771
  23. [23]https://stat.ripe.net/data/as-overview/data.json?resource=AS205132
  24. [24]https://rest.db.ripe.net/ripe/aut-num/AS8866.json
  25. [25]https://rest.db.ripe.net/ripe/aut-num/AS8795.json
  26. [26]https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS8866
  27. [27]https://stat.ripe.net/docs/02.data-api/
  28. [28]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.