EE · United Kingdom
EE is a mobile network operator in the United Kingdom and part of BT Group. The registry records AS2856, held by British Telecommunications Limited, as the ASN carrying EE mobile traffic, with the older EE-held AS12576 announcing nothing. EE uses MCC 234 with MNC 30, 31, 32, 33 and 34.
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.
| ASN | Holder (RIPEstat) | Role | Announced | IPv4 / IPv6 prefixes | Evidence |
|---|---|---|---|---|---|
| AS2856 | BT-UK-AS British Telecommunications Limited | Mobile network confirmed | yes | 534 / 7 | source · RIPEstat |
| AS12576 | EE EE Limited PeeringDB: EE · Cable/DSL/ISP | Mobile network confirmed | no | 0 / 0 | source · RIPEstat · PeeringDB |
| AS33898 | TMOBILE-AS EE Limited | Role not documented name match only | no | 0 / 0 | source · RIPEstat |
| AS35736 | WUK-AS EE Limited | Role not documented name match only | no | 0 / 0 | source · 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.
About EE
The registry lists four ASNs for EE. AS2856 is the one documented as carrying mobile traffic, and at the last probe it announced 534 IPv4 prefixes and 7 IPv6 prefixes. AS12576, registered to EE Limited and named EE in PeeringDB under the Cable/DSL/ISP type, announced no prefixes; the operator moved customer traffic onto AS2856 and has been de-peering AS12576. AS33898 and AS35736 are registered to EE Limited, announce nothing and carry no PeeringDB record, so the registry leaves their role unconfirmed.
An address whose origin ASN is AS2856 is routed by British Telecommunications Limited, the network EE mobile traffic now originates from, so it can be EE mobile or another BT service on the same ASN. The origin ASN alone does not separate the two. For AS33898 and AS35736 the registry has no documented role, so an address originating from either could be mobile, fixed or enterprise, and the ASN does not settle it. EE runs 5G; the registry records no 4G statement from the operator.
Research note. PeeringDB AS12576 (org 8270, website ee.co.uk) notes: 'AS12576 carried EE's mobile and fixed customer traffic. EE is part of BT Group and after many years effort we have moved most customer traffic directly via AS2856. As of March 2025 ... actively de-peering AS12576 which will move fully behind AS2856.' RIPEstat shows AS12576 currently announces 0 prefixes; AS2856 (British Telecommunications Limited, BT-UK-AS) is where EE mobile traffic now originates - AS2856 was not in the candidate list but is the ASN to use. Parent group: PeeringDB record states 'EE is part of BT Group'; BT 'Our brands' page lists EE alongside BT, Plusnet, Openreach. AS33898 (TMOBILE-AS) and AS35736 (WUK-AS) are registered to EE Limited (ORG-TIUL1-RIPE) but announce 0 prefixes and have no PeeringDB record - legacy T-Mobile UK objects, unconfirmed role. REJECTED: AS212633 'EE-Mobile' belongs to EE Mobile Telecom Ltd, Cardiff (ORG-EMTL1-RIPE, PeeringDB org 41340, website ee-mobile.co) - a different company, not EE Limited. MCC/MNC: candidate list was empty; Wikipedia table lists 234-30 (ex-T-Mobile), 234-33 and 234-34 (ex-Orange) as Operational for EE Limited with LTE and 5G bands; 234-31 and 234-32 are Allocated; 234-86, 235-01, 235-02 are EE Limited with Unknown status (omitted). Generations: EE coverage checker states 'The UK's best network now offers 5G in most towns and cities'; a 4G statement was not found on the EE pages fetched (several EE 5G/network URLs 404), so 4G is left out despite Wikipedia listing LTE bands.
Checking whether an IP belongs to EE
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.
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 AS2856' | grep ^routeQuestions
What is EE's ASN?
The registry records AS2856, held by British Telecommunications Limited, as the ASN carrying EE mobile traffic. AS12576 is registered to EE Limited but announces no prefixes after customer traffic moved behind AS2856. AS33898 and AS35736 are also EE Limited objects with no announced prefixes.
What is the MCC/MNC of EE?
EE uses mobile country code 234 with mobile network codes 30, 31, 32, 33 and 34. The registry takes these from the published network-code table for the United Kingdom and records no other codes for the operator.
Is an IP from AS2856 a mobile IP?
Not necessarily. AS2856 is held by British Telecommunications Limited and is documented as carrying EE mobile traffic, but it is a BT Group ASN and the registry does not record which of its prefixes are mobile. The origin ASN on its own does not confirm a mobile connection.
Sources
- https://ee.co.uk/
- https://ee.co.uk/help/mobile-coverage-checker
- https://www.peeringdb.com/api/net?asn=12576
- https://stat.ripe.net/data/as-overview/data.json?resource=AS12576
- https://stat.ripe.net/data/as-overview/data.json?resource=AS2856
- https://stat.ripe.net/data/whois/data.json?resource=AS12576
- https://rest.db.ripe.net/ripe/organisation/ORG-TIUL1-RIPE.json
- https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS12576
- https://stat.ripe.net/data/as-overview/data.json?resource=AS212633
- https://rest.db.ripe.net/ripe/organisation/ORG-EMTL1-RIPE.json
- https://www.peeringdb.com/api/net?asn=212633
- https://en.wikipedia.org/wiki/Mobile_network_codes_in_ITU_region_2xx_(Europe)
- https://www.bt.com/about/bt/our-brands
- RIPEstat Data API (holder, announced prefixes)
- PeeringDB API (network records)