Autonomous System
AS6300
Last fetched
AS6300 is operated by CCI-TEXAS - Fidium, registered in US, and announces 75 prefixes to 25 BGP neighbours. AS6300 has a reputation score of 13.5 (NEUTRAL); 50 of its 173,056 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 75
- BGP neighbours
- 25
- RPKI ROAs
- 0
- MOAS conflicts
- 0
- CAIDA AS-rank
- 1,282
- Customer-cone ASNs
- 28
- Facilities
- 22
- Internet exchanges
- 1
- Customer degree
- 23
- Peer degree
- 10
- Provider degree
- 3
- 64.92.0.0/19
- 64.92.32.0/20
- 64.92.32.0/19
- 64.92.48.0/20
- 66.170.192.0/19
- 66.170.208.0/20
- 70.9.0.0/21
- 70.9.8.0/24
- 70.9.10.0/24
- 70.9.16.0/21
- 70.9.24.0/21
- 70.9.0.0/18
- 70.9.32.0/21
- 70.9.48.0/23
- 72.26.0.0/19
- 76.164.64.0/20
- 76.164.80.0/20
- 76.164.64.0/18
- 76.164.96.0/20
- 76.164.112.0/20
- 135.26.0.0/19
- 135.26.0.0/18
- 135.26.32.0/20
- 135.26.48.0/20
- 135.26.64.0/19
Routing posture
- Hijack posture score
- 0.02
- Route leaks
- 1
Leak types observed: TYPE4_PEER_TO_PROVIDER.
Infrastructure presence
Internet exchanges (1 total)
Facilities (22 total)
- Equinix DA1 - Dallas
- Equinix DA3 - Dallas
- Digital Realty DFW (2323 Bryan St)
- Netrality Houston - 1301 Fannin
- Equinix DA - Dallas (previously Infomart Dallas)
- Databank Houston West (HOU1) (HOU2)
- CyrusOne Dallas (Carrollton)
- Flexential - Dallas/Downtown (DAL01)
- Equinix DA6 - Dallas
- Cologix DAL1
- Cologix DAL2
- DataBank Dallas (DFW5)
- Equinix DA2 - Dallas
- Evocative DA4
- Consolidated - 811 Louisiana
- QTS Irving - Dallas (DFW1)
- DataBank Dallas (DFW1)
- Aligned Dallas (DFW-01)
- QTS Fort Worth (FTW1)
- Stream Data Centers - Houston I
- Cologix DAL3
- Equinix DA11 - Dallas
Upstreams
The networks that most often share an observed BGP path with AS6300.
Blast radius
- Announced IPv4 addresses
- 173,056
- Threat-listed addresses
- 50
- Threat density
- 0.0289 %
- Routed prefixes
- 74
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 25 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- ASN1 - Montgomery County Hospital District · AS4900
- ZAYO-6461 - Zayo Bandwidth · AS6461
- LIVINGSTON-AS - Lake Livingston Communications Inc. · AS16716
- FAIRPOINT - Fidium · AS17093
- ETC - Eastex Telephone Cooperative, Inc. · AS19201
- FDL-42 - Fibertown · AS19366
- HOU-PHONOSCOPE - Phonoscope, Inc. · AS22442
- LEARN-COMMODITY - LEARN · AS22645
- KATYISD - Katy Independent School District · AS22788
- NTS-HUNTSVILLE-01 - Vexus Fiber · AS25798
- REGION7-ESC - Region VII Education Service Center · AS30350
- ANGELINA-COUNTY - ANGELINA COUNTY · AS31859
- WII - WholeSale Internet, Inc. · AS32097
- APOG-TOW - Apogee Telecom Inc. · AS33128
- TENARIS-NA - Tenaris Global Services (USA) Corp. · AS54999
- TXNET - TXNet Communications LLC · AS62467
- CARRIAGESERVICESAS - Carriage Services, Inc. · AS63325
- INU - DP Solutions, Inc. · AS394742
- ETEC-CORP-AS - ETEC · AS395183
- TYR-VLT-110 - Tyler Vault · AS395571
- FBISD-ASNONE - Fort Bend Independent School District · AS395868
- NACSPACE - NacSpace LLC · AS397980
- ENERMUSCLE-ASN - Alternative Internet Resources · AS398260
- DCTEXAS - DCTexas Internet · AS399388
Reputation
13.5reputation score (NEUTRAL)
AS6300 (CCI-TEXAS - Fidium, US) has a reputation score of 63.0 (NEUTRAL).
- Threat density
- 75.1/100
- Graph metrics
- 80.0/100
- Historical behaviour
- 55.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
- Fidium
- RIR
- ARIN
- Registered
- Thu, 16 Jul 1998 04:00:00 GMT
- Abuse contact
- abuse@consolidated.net
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS6300 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.