Autonomous System
AS2856
Last fetched
AS2856 is operated by BT-UK-AS - British Telecommunications Limited, registered in GB, and announces 550 prefixes to 151 BGP neighbours. AS2856 has a reputation score of 9.8 (REPUTABLE); 1,345 of its 13,938,944 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 550
- BGP neighbours
- 151
- RPKI ROAs
- 493
- MOAS conflicts
- 3
- CAIDA AS-rank
- 330
- Customer-cone ASNs
- 157
- Facilities
- 18
- Internet exchanges
- 2
- Customer degree
- 153
- Peer degree
- 86
- Provider degree
- 2
- 5.35.192.0/21
- 5.80.0.0/15
- 5.81.0.0/16
- 5.181.136.0/24
- 9.151.0.0/19
- 9.151.208.0/20
- 9.151.248.0/21
- 9.232.192.0/18
- 9.233.48.0/20
- 9.237.96.0/19
- 9.237.128.0/18
- 9.237.192.0/19
- 15.145.20.0/22
- 23.26.70.0/24
- 23.26.108.0/24
- 23.26.117.0/24
- 23.26.131.0/24
- 23.26.192.0/24
- 23.27.32.0/24
- 23.27.33.0/24
- 23.27.34.0/24
- 23.27.35.0/24
- 23.27.36.0/24
- 23.27.37.0/24
- 23.27.38.0/24
Routing posture
- Hijack posture score
- 0.36
- Origin mismatches
- 3
Infrastructure presence
Facilities (18 total)
- Telehouse - London (Docklands North)
- Telehouse - London (Docklands East)
- Digital Realty London LHR20
- Digital Realty London LHR19
- Equinix LD8 - London, Docklands
- Digital Realty London LON1-3
- Digital Realty London LHR21 (closed)
- Equinix LD4 - London, Slough
- Equinix LD9 - London, Powergate
- Equinix LD5 - London, Slough
- Telehouse - London (Docklands West)
- Equinix LD6 - London, Slough
- Equinix LD10 - London, Slough
- Digital Realty London LHR18
- COLT DC London II
- Telehouse - London (Docklands North Two)
- VIRTUS LONDON2 (Hayes)
- Equinix LD7 - London, Slough
Route origin authorizations
A sample of 10 of this network’s 493 ROAs.
- 166.88.17.0/24 · max length /24
- 166.88.18.0/24 · max length /24
- 166.88.200.0/24 · max length /24
- 166.88.32.0/24 · max length /24
- 192.177.94.0/23 · max length /23
- 192.6.55.0/24 · max length /24
- 2001:4878:c259::/48 · max length /48
- 207.180.43.0/24 · max length /24
- 209.101.8.0/23 · max length /23
- 23.230.242.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS2856.
Blast radius
- Announced IPv4 addresses
- 13,938,944
- Threat-listed addresses
- 1,345
- Threat density
- 0.0096 %
- Routed prefixes
- 543
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: computed.
Peering ecosystem
A sample of 25 of this network’s 151 BGP neighbours.
- GSVNET-AS - Santander Global Technology and Operations, S.L. · AS2134
- BP - BP America, Inc. · AS2535
- SWISSCOM - Swisscom (Schweiz) AG · AS3303
- ACCENTURE - Accenture LLP · AS3573
- SSB-ASN-3738 - State Street Bank and Trust Company · AS3738
- STRIPE - Stripe, Inc. · AS5091
- BT - British Telecommunications Limited · AS5400
- INTERDOTLINK - Inter.link GmbH · AS5405
- NETROUTING-AS - Netrouting B.V. · AS6206
- ZAYO-6461 - Zayo Bandwidth · AS6461
- Plusnet - British Telecommunications Limited · AS6871
- InnovationGrpEMEA - THE INNOVATION GROUP (EMEA) LTD · AS8336
- LBG_INTERNET_EDGE - Lloyds Banking Group PLC · AS8435
- UNSPECIFIED - NATIONWIDE BUILDING SOCIETY · AS8698
- RETN-AS - RETN Limited · AS9002
- UNSPECIFIED - The Patent Office · AS9011
- NAB-AS-AP - National Australia Bank Limited · AS10235
- ORBIS-INVESTMENTS - Orbis Investments (Canada) Limited · AS11031
- PHOTRONICS - Photronics Inc. · AS11528
- MATHWORKS - THE MATHWORKS, INC. · AS11939
- AS12440 - Hughes Network Systems GmbH · AS12440
- UNSPECIFIED - British Telecommunications Limited · AS13205
- QYRUS-INC - QYRUS INC. · AS13447
- UKMAGDIA-BT-LUM - Magnetar Capital LLC · AS14766
- STA-AS - The St. Paul Travelers Companies, Inc. · AS14931
MOAS / hijack watch
3 announced prefixes conflict with AS2856 — another network announces the same address space. A sample:
Reputation
9.8reputation score (REPUTABLE)
AS2856 (BT-UK-AS - British Telecommunications Limited, GB) has a reputation score of 70.6 (REPUTABLE).
- Threat density
- 75.3/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 75.0/100
- Prefix age
- 20.0/100
These are reputation signals about the network as a whole, not a threat-feed verdict about a specific address.
Registration
- Registered to
- British Telecommunications PLC
- RIR
- RIPE
- Registered
- Fri, 30 Aug 2002 11:12:47 GMT
- Abuse contact
- abuse@bt.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS2856 into the prefixes, peers and country it routes for.
Queries
This ASN's full card — routing footprint, peers, conflicts and RIR facts.
MATCH (a:ASN {name: $asn})
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(co:COUNTRY)
OPTIONAL MATCH (a)-[:REGISTERED_BY]->(org:ORGANIZATION)
WITH a,
collect(an.name) AS operatorNames,
collect(co.name) AS countries,
collect(org.name) AS organizations
OPTIONAL MATCH (a)-[:ROUTES]->(prefix:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations,
collect(prefix.name)[0..25] AS samplePrefixes
OPTIONAL MATCH (a)-[:BGP_NEIGHBOR]-(peer:ASN)
OPTIONAL MATCH (peer)-[:HAS_NAME]->(peern:ASN_NAME)
WITH a, operatorNames, countries, organizations, samplePrefixes,
collect({asn: peer.name, operator: peern.name})[0..25] AS samplePeers
OPTIONAL MATCH (a)<-[:CONFLICTS_WITH]-(conflict:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers,
collect(conflict.name)[0..25] AS sampleConflicts
OPTIONAL MATCH (a)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts,
collect(DISTINCT sig.name) AS signals
OPTIONAL MATCH (a)-[:IX_MEMBER]->(ix:INTERNET_EXCHANGE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals,
collect({id: ix.id, name: ix.name})[0..25] AS sampleExchanges
OPTIONAL MATCH (a)-[:AS_PRESENT_AT]->(fac:FACILITY)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges,
collect({id: fac.id, name: fac.name})[0..25] AS sampleFacilities
OPTIONAL MATCH (roa:ROA)-[:ROA_AUTHORIZES_ORIGIN]->(a)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges, sampleFacilities,
collect({prefix: roa.prefix, maxLength: roa.maxLength})[0..10] AS sampleRoas
CALL { WITH a MATCH (a)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS prefixCount }
CALL { WITH a MATCH (a)-[:BGP_NEIGHBOR]-(n:ASN) RETURN count(n) AS peerCount }
CALL { WITH a MATCH (a)<-[:CONFLICTS_WITH]-(c:ANNOUNCED_PREFIX) RETURN count(c) AS conflictCount }
CALL { WITH a MATCH (a)-[:ROA_AUTHORIZES_ORIGIN]-(r:ROA) RETURN count(r) AS roaCount }
CALL { WITH a MATCH (a)-[:AS_PRESENT_AT]->(f:FACILITY) RETURN count(f) AS facilityCount }
CALL { WITH a MATCH (a)-[:IX_MEMBER]->(x:INTERNET_EXCHANGE) RETURN count(x) AS ixpCount }
RETURN a.name AS name,
a.rir AS rir,
a.orgName AS orgName,
a.asRank AS asRank,
a.coneAsns AS coneAsns,
a.conePrefixes AS conePrefixes,
a.coneAddresses AS coneAddresses,
a.registrationDate AS registrationDate,
a.reputationScore AS reputationScore,
a.reputationCategory AS reputationCategory,
a.overallThreatLevel AS overallThreatLevel,
a.abuseEmail AS abuseEmail,
a.hijackPostureScore AS hijackPostureScore,
a.hijackOriginMismatchCount AS hijackOriginMismatchCount,
a.routeLeakCount AS routeLeakCount,
a.routeLeakTypes AS routeLeakTypes,
a.degreeCustomer AS degreeCustomer,
a.degreePeer AS degreePeer,
a.degreeProvider AS degreeProvider,
operatorNames, countries, organizations,
samplePrefixes, samplePeers, sampleConflicts,
signals, sampleExchanges, sampleFacilities, sampleRoas,
prefixCount, peerCount, conflictCount, roaCount, facilityCount, ixpCountRun yourself →The five networks that most often share this ASN's observed BGP paths.
MATCH (a:ASN {name: $asn})<-[:BGP_PATH]-(b:BGP_PATH_OBSERVATION)
WITH b LIMIT 200
MATCH (b)-[:BGP_PATH]->(up:ASN)
WHERE up.name <> $asn
WITH up.name AS asn, count(*) AS observations
ORDER BY observations DESC
LIMIT 5
RETURN asn, observationsRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.