Autonomous System
AS7311
Last fetched
AS7311 is operated by FRONTIER - Frontier Networks Inc, registered in CA, and announces 100 prefixes to 35 BGP neighbours. AS7311 has a reputation score of 11.5 (NEUTRAL); 30 of its 128,768 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 100
- BGP neighbours
- 35
- RPKI ROAs
- 92
- MOAS conflicts
- 0
- CAIDA AS-rank
- 1,280
- Customer-cone ASNs
- 28
- Facilities
- 49
- Internet exchanges
- 5
- Customer degree
- 25
- Peer degree
- 35
- Provider degree
- 5
- 24.104.160.0/20
- 24.104.176.0/23
- 24.104.178.0/24
- 24.104.179.0/24
- 24.104.180.0/23
- 24.104.182.0/24
- 24.104.183.0/24
- 24.104.184.0/22
- 24.104.188.0/24
- 24.104.189.0/24
- 24.104.190.0/24
- 24.104.191.0/24
- 24.146.64.0/20
- 24.146.80.0/20
- 24.146.96.0/22
- 24.146.100.0/22
- 24.146.104.0/21
- 24.146.112.0/20
- 38.143.48.0/21
- 38.143.54.0/23
- 45.2.2.0/24
- 45.2.24.0/24
- 45.2.25.0/24
- 45.2.68.0/24
- 45.2.0.0/16
Routing posture
- Hijack posture score
- 0.08
- Route leaks
- 4
Leak types observed: TYPE1_HAIRPIN_TURN, TYPE4_PEER_TO_PROVIDER.
Infrastructure presence
Internet exchanges (5 total)
Facilities (49 total)
- Digital Realty NYC (60 Hudson)
- Equinix NY1 - New York, Newark
- Equinix TR1 - Toronto
- Digital Realty NYC (111 8th Ave)
- Equinix NY9 - New York, 111 8th Avenue
- Equinix NY2/NY4/NY5/NY6 - New York, Secaucus
- Digital Realty Seattle SEA10
- Equinix SE2/SE3 - Seattle
- Harbour Centre Vancouver
- Neutral Data Toronto
- 165 Halsey Meet-Me Room
- Telehouse Toronto (151 Front St West)
- KOMO Plaza Seattle (Formerly Fisher Plaza)
- Equinix NY7 - New York, North Bergen
- Intergate West / Digital.forest / Fortress
- CoreSite - New York (NY1)
- Telehouse - Teleport Center (New York)
- Cologix TOR1
- Cologix MIN1
- Telehouse - New York Chelsea
- Cologix VAN1
- Cologix VAN2
- Cologix MTL3
- Equinix TR2 - Toronto
- Telehouse Toronto (250 Front St West)
Route origin authorizations
A sample of 10 of this network’s 92 ROAs.
- 104.37.80.0/22 · max length /24
- 161.129.186.0/24 · max length /24
- 162.33.168.0/21 · max length /24
- 162.33.180.0/23 · max length /24
- 162.33.188.0/23 · max length /24
- 162.33.216.0/21 · max length /24
- 192.154.144.0/20 · max length /24
- 2001:470:47c::/48 · max length /48
- 2001:470:51d::/48 · max length /48
- 205.153.228.0/23 · max length /23
Upstreams
The networks that most often share an observed BGP path with AS7311.
Blast radius
- Announced IPv4 addresses
- 128,768
- Threat-listed addresses
- 30
- Threat density
- 0.0233 %
- Routed prefixes
- 99
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 35 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- BACOM - Bell Canada · AS577
- ROGERS-COMMUNICATIONS - Rogers Communications Canada Inc. · AS812
- GOCODEIT-EDGE - GoCodeIT Inc · AS835
- ASN852 - TELUS Communications Inc. · AS852
- AS-PRP-001 - Peel Regional Police · AS1070
- LEVEL3 - Level 3 Parent, LLC · AS3356
- SHERIDAN-NET - The Sheridan College Institute of Technology and Advanced Learning · AS5664
- SHAW - Shaw Communications · AS6327
- HURRICANE - Hurricane Electric LLC · AS6939
- RETN-AS - RETN Limited · AS9002
- B3ZDNA - B3zdna Systems Inc. · AS10261
- TRENDS-NET - @trends.ca · AS10678
- CONCORDE - Concorde inc. · AS10996
- LAVALIFE - Lavalife Corp. · AS13846
- FIBERSPEED - FiberSpeed · AS14673
- EDAP - Edaptivity.com Inc · AS16949
- HOSTSERVE-NET-AS - AllCore Communications Inc. · AS17266
- ACS-CORP - ALCOHOL COUNTERMEASURE SYSTEMS CORP · AS19821
- WIRELESSFARM-CA-TOR1 - Wireless Farm Inc. · AS20082
- BEANFIELD - Beanfield Technologies Inc. · AS21949
- BRAMPTON - City of Brampton · AS23457
- EICAT - E. I. Catalyst · AS30528
- HDTELECOMCA - HD Telecom Inc. · AS32012
- MEGAWIRE - Megawire Inc. · AS33044
Reputation
11.5reputation score (NEUTRAL)
AS7311 (FRONTIER - Frontier Networks Inc, CA) has a reputation score of 67.0 (NEUTRAL).
- Threat density
- 65.1/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
- Frontier Networks Inc
- RIR
- ARIN
- Registered
- Fri, 16 Oct 2009 20:10:53 GMT
- Abuse contact
- abuse@frontiernetworks.ca
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS7311 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.