Autonomous System
AS11019
Last fetched
AS11019 is operated by HAPROXY-TECHNOLOGIES - HAProxy Technologies, Inc., registered in US, and announces 50 prefixes to 19 BGP neighbours. AS11019 has a reputation score of 8.1 (REPUTABLE); 0 of its 7,168 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 50
- BGP neighbours
- 19
- RPKI ROAs
- 3
- MOAS conflicts
- 0
- CAIDA AS-rank
- 1,147
- Customer-cone ASNs
- 33
- Facilities
- 139
- Internet exchanges
- 12
- Customer degree
- 11
- Peer degree
- 142
- Provider degree
- 9
- 67.22.53.0/24
- 104.152.112.0/24
- 104.152.113.0/24
- 104.152.114.0/24
- 104.152.115.0/24
- 104.152.112.0/21
- 104.152.116.0/24
- 104.152.117.0/24
- 104.152.118.0/24
- 104.152.119.0/24
- 205.234.165.0/24
- 209.126.32.0/24
- 209.126.35.0/24
- 209.126.36.0/24
- 209.126.37.0/24
- 209.126.38.0/24
- 209.126.39.0/24
- 209.126.41.0/24
- 209.126.42.0/24
- 209.126.43.0/24
- 209.126.44.0/24
- 209.126.45.0/24
- 209.126.47.0/24
- 209.126.48.0/24
- 209.126.49.0/24
Infrastructure presence
Internet exchanges (12 total)
Facilities (139 total)
- Equinix CH1/CH2/CH4 - Chicago
- Digital Realty NYC (60 Hudson)
- Equinix MI1 - Miami, NOTA
- NIKHEF Amsterdam
- Telehouse - London (Docklands North)
- Equinix LD8 - London, Docklands
- Digital Realty Frankfurt FRA1-27
- Telehouse - Paris 2 (Voltaire - Léon Frot)
- Digital Realty AMS3/5/7/8/10 - Amsterdam
- Global Switch Amsterdam
- Equinix FR5 - Frankfurt, KleyerStrasse
- Equinix AM7 - Amsterdam, Kuiperberweg
- Digital Realty AMS17 - Amsterdam
- Equinix PA5 - Paris, Victor Hugo
- Digital Realty VIE1/2 - Vienna
- Equinix SE2/SE3 - Seattle
- Digital Realty AMS9 - Amsterdam
- Espanix Datacenter
- Digital Realty Madrid MAD1-2
- Digital Realty ATL13 - Atlanta
- Equinix SY1/SY2 - Sydney
- Moscow M9
- Equinix SK1 - Stockholm, Bromma
- Speedbone Berlin
- Equinix SP4 - São Paulo
Route origin authorizations
A sample of 3 of this network’s 3 ROAs.
- 104.152.119.0/24 · max length /24
- 209.126.52.0/24 · max length /24
- 2604:cac0::/32 · max length /48
Upstreams
The networks that most often share an observed BGP path with AS11019.
Blast radius
- Announced IPv4 addresses
- 7,168
- Threat-listed addresses
- 0
- Threat density
- 0.0000 %
- Routed prefixes
- 29
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: clean.
Peering ecosystem
A sample of 19 of this network’s 19 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- ASN-TELSTRA - Telstra Limited · AS1221
- TWELVE99 - Arelion Sweden AB · AS1299
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- LEVEL3 - Level 3 Parent, LLC · AS3356
- HURRICANE - Hurricane Electric LLC · AS6939
- AS7195 - EDGEUNO S.A.S · AS7195
- LONE-PINE-OLANCHA - LONE PINE Communications · AS19890
- MOMENTUM-ACCESS - Momentum Telecom, Inc. · AS25645
- REFLECTED - Reflected Networks, Inc. · AS29789
- SWIFTWILL2 - Swiftwill, Inc. · AS30361
- MOMENTUM33059 - Momentum Telecom, Inc. · AS33059
- ST-FRANCIS-COLLEGE - St. Francis College · AS39943
- BARNES-AND-NOBLE - Barnes & Noble Inc. · AS39960
- PROHCI - Hosting Consulting, Inc · AS40539
- VikingHost - Viking Host B.V. · AS48684
- C2HOSTING-01 - C2Hosting, LLC · AS53332
- EMPIRE-1 - Empire Resorts, Inc. · AS400392
Reputation
8.1reputation score (REPUTABLE)
AS11019 (HAPROXY-TECHNOLOGIES - HAProxy Technologies, Inc., US) has a reputation score of 75.8 (REPUTABLE).
- Threat density
- 90.0/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
- HAProxy Technologies, Inc.
- RIR
- ARIN
- Registered
- Wed, 09 Apr 2014 19:19:05 GMT
- Abuse contact
- abuse@haproxy.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS11019 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.