Autonomous System
AS9123
Last fetched
AS9123 is operated by TimeWeb-AS - JSC "TIMEWEB", registered in RU, and announces 953 prefixes to 36 BGP neighbours. AS9123 has a reputation score of 17.1 (NEUTRAL); 419 of its 236,544 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 953
- BGP neighbours
- 36
- RPKI ROAs
- 802
- MOAS conflicts
- 1
- CAIDA AS-rank
- 2,347
- Customer-cone ASNs
- 12
- Facilities
- 167
- Internet exchanges
- 13
- Customer degree
- 11
- Peer degree
- 31
- Provider degree
- 17
- 2.59.40.0/24
- 2.59.41.0/24
- 2.59.42.0/24
- 2.59.43.0/24
- 5.23.48.0/24
- 5.23.49.0/24
- 5.23.50.0/24
- 5.23.51.0/24
- 5.23.52.0/24
- 5.23.53.0/24
- 5.23.54.0/24
- 5.23.55.0/24
- 5.42.96.0/24
- 5.42.97.0/24
- 5.42.98.0/24
- 5.42.99.0/24
- 5.42.100.0/24
- 5.42.101.0/24
- 5.42.102.0/24
- 5.42.103.0/24
- 5.42.104.0/24
- 5.42.105.0/24
- 5.42.106.0/24
- 5.42.107.0/24
- 5.42.108.0/24
Routing posture
- Hijack posture score
- 0.41
- Origin mismatches
- 5
Infrastructure presence
Internet exchanges (13 total)
Facilities (167 total)
- NIKHEF Amsterdam
- Telehouse - London (Docklands North)
- Telehouse - London (Docklands East)
- Digital Realty London LHR20
- Equinix LD8 - London, Docklands
- Digital Realty Frankfurt FRA1-27
- Telehouse - Paris 2 (Voltaire - Léon Frot)
- Global Switch Amsterdam
- Digital Realty AMS3/5/7/8/10 - Amsterdam
- ITENOS Frankfurt (FRA1)
- Equinix FR5 - Frankfurt, KleyerStrasse
- Digital Realty AMS17 - Amsterdam
- Equinix AM7 - Amsterdam, Kuiperberweg
- Equinix FR7 - Frankfurt, Gutleutstrasse
- Digital Realty VIE1/2 - Vienna
- Digital Realty BRU1 - Brussels
- Equinix AM8 - Amsterdam, Gyroscoopweg
- Digital Realty AMS9 - Amsterdam
- Digital Realty Dusseldorf DUS1-3
- Telehouse - Frankfurt
- EdgeConneX Munich (EDCMUC01)
- Digital Realty Frankfurt FRA28 (Closed)
- Equinix EN1 - Enschede
- Moscow M9
- NorthC Duesseldorf
Route origin authorizations
A sample of 10 of this network’s 802 ROAs.
- 103.74.93.0/24 · max length /24
- 103.74.94.0/24 · max length /24
- 103.74.95.0/24 · max length /24
- 103.88.240.0/24 · max length /24
- 103.88.241.0/24 · max length /24
- 103.88.242.0/24 · max length /24
- 103.88.243.0/24 · max length /24
- 104.171.128.0/24 · max length /32
- 104.171.129.0/24 · max length /32
- 104.171.130.0/24 · max length /32
Upstreams
The networks that most often share an observed BGP path with AS9123.
Blast radius
- Announced IPv4 addresses
- 236,544
- Threat-listed addresses
- 419
- Threat density
- 0.1771 %
- Routed prefixes
- 925
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 36 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- TWELVE99 - Arelion Sweden AB · AS1299
- XTOM-V-PS - xTom OU · AS3204
- SOVAM-AS - PJSC "Vimpelcom" · AS3216
- HURRICANE - Hurricane Electric LLC · AS6939
- MTS - MTS PJSC · AS8359
- RETN-AS - RETN Limited · AS9002
- ROSTELECOM-AS - PJSC Rostelecom · AS12389
- IMAQLIQ - Data-center IMAQLIQ Ltd. · AS12555
- RASCOM-AS - CJSC RASCOM · AS20764
- SGGS-AS-AP - SG.GS · AS24482
- CORE-BACKBONE - Core-Backbone GmbH · AS33891
- iFog-GmbH - iFog GmbH · AS34927
- Virtual Technologies & Solutions - Virtual Technologies & Solutions · AS37721
- StormNetworks - Storm Networks LLC · AS43298
- TKSWF-AS - Stadtwerke Feldkirch · AS48362
- INTERA-AS - Alexei Tingaev · AS48876
- TRUENETWORK - Truenetwork LLC · AS49673
- TRANSROUTE - Transroute Telecom LTD · AS50509
- LWLCOM - LWLcom GmbH · AS50629
- Serverius-as - Serverius Holding B.V. · AS50673
- TimewebCloud - JSC "TIMEWEB" · AS51789
- GIGAHOST - Gigahost AS · AS56655
- RETNRU-AS - JSC "RetnNet" · AS57304
- IQWEB - IQWeb FZ-LLC · AS59692
MOAS / hijack watch
1 announced prefix conflict with AS9123 — another network announces the same address space. A sample:
Reputation
17.1reputation score (NEUTRAL)
AS9123 (TimeWeb-AS - JSC "TIMEWEB", RU) has a reputation score of 55.8 (NEUTRAL).
- Threat density
- 43.8/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 60.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
- JSC "TIMEWEB"
- RIR
- RIPE
- Registered
- Tue, 01 Apr 2008 10:36:48 GMT
- Abuse contact
- abuse@timeweb.ru
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS9123 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.