Autonomous System
AS21928
Last fetched
AS21928 is operated by T-MOBILE-AS21928 - T-Mobile USA, Inc., registered in US, and announces 541 prefixes to 13 BGP neighbours. AS21928 has a reputation score of 9.8 (REPUTABLE); 1,167 of its 13,130,240 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 541
- BGP neighbours
- 13
- RPKI ROAs
- 857
- MOAS conflicts
- 0
- CAIDA AS-rank
- 4,925
- Customer-cone ASNs
- 4
- Facilities
- 92
- Internet exchanges
- 10
- Customer degree
- 3
- Peer degree
- 57
- Provider degree
- 4
- 65.76.0.0/16
- 66.94.3.0/24
- 66.94.4.0/24
- 66.94.5.0/24
- 66.94.6.0/24
- 66.94.7.0/24
- 66.94.8.0/24
- 66.94.13.0/24
- 66.94.14.0/24
- 66.94.15.0/24
- 66.94.0.0/19
- 66.94.17.0/24
- 66.94.18.0/23
- 66.94.24.0/24
- 66.94.26.0/24
- 66.94.29.0/24
- 66.94.30.0/24
- 72.250.0.0/17
- 74.60.0.0/16
- 75.122.0.0/17
- 75.122.128.0/17
- 75.123.0.0/17
- 75.123.128.0/17
- 97.65.105.0/24
- 100.128.0.0/9
Infrastructure presence
Internet exchanges (10 total)
Facilities (92 total)
- Digital Realty SFO (200 Paul)
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- Equinix CH1/CH2/CH4 - Chicago
- CoreSite - Los Angeles (LA1) One Wilshire
- Digital Realty NYC (111 8th Ave)
- Digital Realty SFO (365 Main)
- CoreSite - San Jose (SV1)
- Digital Realty NYC (60 Hudson)
- Equinix LA1 - Los Angeles
- Equinix MI1 - Miami, NOTA
- Equinix NY2/NY4/NY5/NY6 - New York, Secaucus
- Digital Realty Seattle SEA10
- Equinix SE2/SE3 - Seattle
- Digital Realty ATL13 - Atlanta
- iM Critical Miami
- Level(3) Sunnyvale
- Markley Group One Summer Street Boston
- PTOR1
- 165 Halsey Meet-Me Room
- CoreSite - Los Angeles (LA2)
- CoreSite - Denver (DE1)
- KOMO Plaza Seattle (Formerly Fisher Plaza)
- Digital Realty OAK (720 2nd St)
- Equinix DA - Dallas (previously Infomart Dallas)
Route origin authorizations
A sample of 10 of this network’s 857 ROAs.
- 100.128.0.0/9 · max length /24
- 104.152.20.0/22 · max length /24
- 162.160.0.0/11 · max length /24
- 167.20.0.0/16 · max length /24
- 168.73.0.0/16 · max length /24
- 169.224.135.0/24 · max length /24
- 170.206.0.0/16 · max length /24
- 172.32.0.0/11 · max length /24
- 172.56.0.0/16 · max length /23
- 172.57.114.0/26 · max length /26
Upstreams
The networks that most often share an observed BGP path with AS21928.
Blast radius
- Announced IPv4 addresses
- 13,130,240
- Threat-listed addresses
- 1,167
- Threat density
- 0.0089 %
- Routed prefixes
- 283
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 13 of this network’s 13 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- LEVEL3 - Level 3 Parent, LLC · AS3356
- ASN-TELSTRA-GLOBAL - Telstra Global · AS4637
- ZAYO-6461 - Zayo Bandwidth · AS6461
- HURRICANE - Hurricane Electric LLC · AS6939
- AARNET-AS-AP - Australian Academic and Research Network (AARNet) · AS7575
- RETN-AS - RETN Limited · AS9002
- GOOGLE-PRIVATE-CLOUD - Google LLC · AS16550
- AMPLEX - Amplex Electric, Inc. · AS20205
- T-MOBILE-AS22140 - T-Mobile USA, Inc. · AS22140
- SGGS-AS-AP - SG.GS · AS24482
- F5 - F5 Networks SARL · AS35280
- VERSA-01 - Versa Networks, Inc. · AS400318
Reputation
9.8reputation score (REPUTABLE)
AS21928 (T-MOBILE-AS21928 - T-Mobile USA, Inc., US) has a reputation score of 70.7 (REPUTABLE).
- Threat density
- 68.4/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 85.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
- T-Mobile USA, Inc.
- RIR
- ARIN
- Registered
- Wed, 12 Jun 2002 04:00:00 GMT
- Abuse contact
- abuse@t-mobile.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS21928 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.