Autonomous System
AS49870
Last fetched
AS49870 is operated by AS49870-BV - Alsycon B.V., registered in NL, and announces 24 prefixes to 15 BGP neighbours. AS49870 has a reputation score of 17.5 (NEUTRAL); 566 of its 8,704 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 24
- BGP neighbours
- 15
- RPKI ROAs
- 17
- MOAS conflicts
- 0
- CAIDA AS-rank
- 3,517
- Customer-cone ASNs
- 7
- Facilities
- 32
- Internet exchanges
- 3
- Customer degree
- 5
- Peer degree
- 36
- Provider degree
- 7
- 2.56.167.0/24
- 45.80.36.0/23
- 45.81.22.0/23
- 45.95.144.0/23
- 45.95.146.0/24
- 45.95.147.0/24
- 45.140.222.0/23
- 77.83.240.0/24
- 89.116.202.0/24
- 89.190.156.0/24
- 89.190.159.0/24
- 160.119.64.0/22
- 160.119.69.0/24
- 160.119.71.0/24
- 160.119.74.0/24
- 160.119.75.0/24
- 160.119.76.0/23
- 160.119.78.0/24
- 169.239.130.0/24
- 185.224.128.0/24
- 194.50.16.0/24
- 196.61.64.0/22
- 212.107.12.0/24
- 2a0e:3980::/29
Routing posture
- Hijack posture score
- 0.02
- Route leaks
- 1
Leak types observed: TYPE1_HAIRPIN_TURN.
Infrastructure presence
Facilities (32 total)
- NIKHEF Amsterdam
- Global Switch Amsterdam
- Equinix AM7 - Amsterdam, Kuiperberweg
- Equinix FR7 - Frankfurt, Gutleutstrasse
- Digital Realty AMS17 - Amsterdam
- Equinix FR5 - Frankfurt, KleyerStrasse
- Digital Realty AMS9 - Amsterdam
- Equinix AM8 - Amsterdam, Gyroscoopweg
- Equinix SK1 - Stockholm, Bromma
- Equinix AM1/AM2 - Amsterdam, Luttenbergweg
- nLighten Amsterdam AMS1
- LVRTC TV Tower
- Delska EU North Vilnius LT DC3
- Telia Telehouse KJJ
- KoloDC NL1
- NorthC Amsterdam 1
- Equinix AM5 - Amsterdam, Schepenbergweg
- Equinix AM3 - Amsterdam, Science Park
- NorthC Delft
- KoloDC NL2
- DFDC The Hague
- Eurofiber Datacenter Rotterdam 2
- Equinix AM6 - Amsterdam, Duivendrechtsekade
- Dataone AMS1
- INFONET DC
Route origin authorizations
A sample of 10 of this network’s 17 ROAs.
- 169.239.130.0/24 · max length /24
- 185.224.128.0/24 · max length /24
- 194.50.16.0/23 · max length /24
- 2.56.167.0/24 · max length /24
- 212.107.12.0/24 · max length /24
- 2a0e:3980::/29 · max length /29
- 45.140.222.0/23 · max length /23
- 45.80.36.0/23 · max length /23
- 45.81.22.0/23 · max length /23
- 45.95.144.0/23 · max length /23
Upstreams
The networks that most often share an observed BGP path with AS49870.
Blast radius
- Announced IPv4 addresses
- 8,704
- Threat-listed addresses
- 566
- Threat density
- 6.5028 %
- Routed prefixes
- 23
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 15 of this network’s 15 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- TWELVE99 - Arelion Sweden AB · AS1299
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- HURRICANE - Hurricane Electric LLC · AS6939
- HOSTUS-GLOBAL-AS - HostUS · AS7489
- RETN-AS - RETN Limited · AS9002
- BITE - UAB "Bite Lietuva" · AS13194
- ALSYCON-BV - Alsycon B.V. · AS49305
- EKMEDIA - EK-Media B.V. · AS51942
- FBX-AS - FiberXpress BV · AS57717
- SECUREBIT - Securebit AG · AS58057
- ALSYCON-BV - Alsycon B.V. · AS208911
- ipvendettainc - IP Vendetta Inc. · AS209101
- KOI-AS - KOI CLOUD SERVICES (Pty) Ltd · AS209425
- ALLSYSNET - IT HELP LCC · AS218859
Reputation
17.5reputation score (NEUTRAL)
AS49870 (AS49870-BV - Alsycon B.V., NL) has a reputation score of 54.9 (NEUTRAL).
- Threat density
- 30.6/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
- Alsycon B.V.
- RIR
- RIPE
- Registered
- Thu, 14 Nov 2019 08:50:00 GMT
- Abuse contact
- abuse@as49870.net
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS49870 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.