Autonomous System
AS13768
Last fetched
AS13768 is operated by COGECO-PEER1 - Aptum Technologies, registered in CA, and announces 503 prefixes to 22 BGP neighbours. AS13768 has a reputation score of 9.0 (REPUTABLE); 28 of its 619,776 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 503
- BGP neighbours
- 22
- RPKI ROAs
- 150
- MOAS conflicts
- 0
- CAIDA AS-rank
- 1,528
- Customer-cone ASNs
- 22
- Facilities
- 15
- Internet exchanges
- 1
- Customer degree
- 19
- Peer degree
- 8
- Provider degree
- 6
- 5.44.16.0/21
- 5.44.24.0/22
- 5.44.28.0/22
- 23.180.80.0/24
- 36.255.72.0/22
- 37.203.42.0/24
- 45.41.192.0/24
- 45.41.193.0/24
- 46.20.112.0/20
- 62.128.132.0/24
- 62.128.133.0/24
- 62.128.140.0/22
- 62.128.128.0/19
- 62.192.169.0/24
- 64.34.8.0/22
- 64.34.20.0/22
- 64.34.24.0/22
- 64.34.28.0/23
- 64.34.30.0/23
- 64.34.40.0/24
- 64.34.48.0/22
- 64.34.64.0/20
- 64.34.96.0/20
- 64.34.127.0/24
- 64.34.128.0/20
Infrastructure presence
Internet exchanges (1 total)
Facilities (15 total)
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- Equinix MI1 - Miami, NOTA
- Equinix TR1 - Toronto
- CoreSite - Los Angeles (LA1) One Wilshire
- Telehouse - London (Docklands East)
- Harbour Centre Vancouver
- Neutral Data Toronto
- Telehouse Toronto (151 Front St West)
- Cologix TOR1
- Equinix LD5 - London, Slough
- Equinix TR2 - Toronto
- Telehouse Toronto (250 Front St West)
- Cologix TOR2
- Telehouse Toronto (905 King Street West)
- Coloware YTZ1
Route origin authorizations
A sample of 10 of this network’s 150 ROAs.
- 104.255.171.0/24 · max length /24
- 104.255.172.0/24 · max length /24
- 192.107.133.0/24 · max length /24
- 192.150.214.0/23 · max length /23
- 192.154.204.0/24 · max length /24
- 192.154.214.0/24 · max length /24
- 209.15.37.0/24 · max length /24
- 209.15.40.0/24 · max length /24
- 209.15.41.0/24 · max length /24
- 209.25.176.0/21 · max length /21
Upstreams
The networks that most often share an observed BGP path with AS13768.
Blast radius
- Announced IPv4 addresses
- 619,776
- Threat-listed addresses
- 28
- Threat density
- 0.0045 %
- Routed prefixes
- 486
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 22 of this network’s 22 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- TWELVE99 - Arelion Sweden AB · AS1299
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- LEVEL3 - Level 3 Parent, LLC · AS3356
- ZAYO-6461 - Zayo Bandwidth · AS6461
- DATTO-INT - Datto, LLC · AS17158
- ACDLABS-AS - ACD/Labs · AS18721
- CALLTOWER - CallTower, Inc. · AS20340
- ISPT - ISP Telecom · AS22964
- ONX - OnX Enterprise Solutions Inc. · AS23136
- HYPERWALLET-VB - HyperWALLET Systems Inc · AS26441
- SAQ-UK-AS - SEMTEC LIMITED · AS29219
- EVAULT-AS - Open Text Corporation · AS33459
- THRIVE-CA1 - Thrive Operations, LLC · AS35947
- CONTABO - Contabo GmbH · AS51167
- VCOMP - Venture Computers of Canada · AS53525
- BBDTEL - Broadband Dynamics, LLC · AS53845
- QITX-INC - Chris Danielle Micro Solutions (CDMS) Inc. · AS54044
- ASTUTEHOSTING - Astute Internet · AS54527
- IDIGITAL - Idigital Internet Inc. · AS54643
- ANTHEIA - NSI (Holdings) Limited · AS196962
- WIZ1 - Wizard Tower Techno Services · AS393653
Reputation
9.0reputation score (REPUTABLE)
AS13768 (COGECO-PEER1 - Aptum Technologies, CA) has a reputation score of 73.0 (REPUTABLE).
- Threat density
- 82.2/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
- Aptum Technologies
- RIR
- ARIN
- Registered
- Mon, 10 Jun 2002 04:00:00 GMT
- Abuse contact
- abuse@aptum.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS13768 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.