Autonomous System
AS35133
Last fetched
AS35133 is operated by ERANIUM - Eranium B.V., registered in NL, and announces 8 prefixes to 67 BGP neighbours. AS35133 has a reputation score of 7.3 (REPUTABLE); 0 of its 768 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 8
- BGP neighbours
- 67
- RPKI ROAs
- 12
- MOAS conflicts
- 0
- CAIDA AS-rank
- 324
- Customer-cone ASNs
- 159
- Facilities
- 43
- Internet exchanges
- 4
- Customer degree
- 44
- Peer degree
- 20
- Provider degree
- 8
Signals
- ddos-mitigationProvides DDoS scrubbing or absorption for its customers.
Infrastructure presence
Internet exchanges (4 total)
Facilities (43 total)
- NIKHEF Amsterdam
- Telehouse - Paris 2 (Voltaire - Léon Frot)
- ITENOS Frankfurt (FRA1)
- Equinix FR5 - Frankfurt, KleyerStrasse
- Equinix AM8 - Amsterdam, Gyroscoopweg
- Digital Realty AMS17 - Amsterdam
- Equinix AM7 - Amsterdam, Kuiperberweg
- Digital Realty AMS3/5/7/8/10 - Amsterdam
- Digital Realty VIE1/2 - Vienna
- Equinix FR7 - Frankfurt, Gutleutstrasse
- BIT-1
- Equinix EN1 - Enschede
- Digital Realty AMS9 - Amsterdam
- Telehouse - Frankfurt
- InterDC Doetinchem
- NTT Frankfurt 1 Data Center (FRA1)
- NewColo Frankfurt
- Iron Mountain Data Center - Amsterdam (AMS-1)
- Equinix AM1/AM2 - Amsterdam, Luttenbergweg
- BIT-2
- Digital Realty AMS18 - Amsterdam
- Telehouse - Paris 3 (Magny)
- Equinix FR4 - Frankfurt, West
- Previder PDC2
- NorthC Amsterdam 1
Route origin authorizations
A sample of 10 of this network’s 12 ROAs.
- 2.58.57.0/24 · max length /24
- 2.58.59.0/24 · max length /24
- 217.18.95.0/24 · max length /32
- 2a07:5500::/29 · max length /29
- 2a07:5506::/32 · max length /32
- 2a07:5507::/32 · max length /32
- 2a09:e240:1337::/48 · max length /48
- 2a09:e240:22::/48 · max length /48
- 2a09:e240:2::/48 · max length /48
- 2a09:e244::/33 · max length /33
Upstreams
The networks that most often share an observed BGP path with AS35133.
Blast radius
- Announced IPv4 addresses
- 768
- Threat-listed addresses
- 0
- Threat density
- 0.0000 %
- Routed prefixes
- 3
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 25 of this network’s 67 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- HYONIX - Hyonix · AS931
- BYTEFILTER-AS - Bytefilter LLC · AS1002
- UTWENTE-AS - SURF B.V. · AS1133
- TWELVE99 - Arelion Sweden AB · AS1299
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- LEVEL3 - Level 3 Parent, LLC · AS3356
- Opentransit - Orange S.A. · AS5511
- AS6453 - TATA COMMUNICATIONS (AMERICA) INC · AS6453
- SEABONE-NET - TELECOM ITALIA SPARKLE S.p.A. · AS6762
- LibertyGlobal - Liberty Global Europe Holding B.V. · AS6830
- HURRICANE - Hurricane Electric LLC · AS6939
- NL-BIT - BIT BV · AS12859
- AS-VULTR - The Constant Company, LLC · AS20473
- SGGS-AS-AP - SG.GS · AS24482
- IT7NET - IT7 Networks Inc · AS25820
- FDCSERVERS - FDCservers.net · AS30058
- Servperso_Systems - Sarah Rossius trading as Servperso Systems · AS34872
- iFog-GmbH - iFog GmbH · AS34927
- TransitX-Ltd - TransitX Ltd · AS35200
- VIRTUASYS-EU - VIRTUA SYSTEMS SAS · AS35661
- UCSYSTEMS - CTA Systems B.V. · AS39563
- BAKKER-IT-AS - The Mastermind Holding B.V. · AS44103
- SPL - SPL B.V. · AS44299
- SYNLINQ - Oliver Horscht trading as "SYNLINQ" · AS44486
Reputation
7.3reputation score (REPUTABLE)
AS35133 (ERANIUM - Eranium B.V., NL) has a reputation score of 78.3 (REPUTABLE).
- Threat density
- 90.0/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 85.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
- Eranium B.V.
- RIR
- RIPE
- Registered
- Tue, 09 Apr 2019 14:09:36 GMT
- Abuse contact
- abuse@eranium.io
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS35133 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.