Autonomous System
AS56309
Last fetched
AS56309 is operated by SIAMDATA-TH - Siamdata Communication Co.,Ltd., registered in TH, and announces 60 prefixes to 11 BGP neighbours. AS56309 has a reputation score of 15.4 (NEUTRAL); 78 of its 30,720 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 60
- BGP neighbours
- 11
- RPKI ROAs
- 191
- MOAS conflicts
- 0
- CAIDA AS-rank
- 4,415
- Customer-cone ASNs
- 5
- Facilities
- 16
- Internet exchanges
- 3
- Customer degree
- 4
- Peer degree
- 2
- Provider degree
- 5
- 43.228.84.0/24
- 43.228.84.0/22
- 43.228.86.0/24
- 43.229.77.0/24
- 43.229.76.0/22
- 43.229.78.0/24
- 43.229.132.0/23
- 43.229.132.0/22
- 43.229.134.0/24
- 43.229.134.0/23
- 43.229.148.0/23
- 43.229.148.0/22
- 43.229.151.0/24
- 43.249.32.0/23
- 44.31.100.0/24
- 45.91.133.0/24
- 45.91.134.0/24
- 45.91.135.0/24
- 45.136.236.0/22
- 45.136.252.0/22
- 45.144.164.0/22
- 45.150.128.0/22
- 45.150.130.0/24
- 45.154.24.0/22
- 103.13.28.0/24
Infrastructure presence
Internet exchanges (3 total)
Facilities (16 total)
- CS LoxInfo Data Center - CW Tower
- CS LoxInfo Data Center - The Cloud
- TCC Technology Data Center- Bangkok,Thailand (TCC BNDC,TCC Bangna,TCCtech)
- JasTel Data Center (Thailand)
- NT Bangrak Tower
- NT Nonthaburi Telecommunication Center
- Arise IDC - Bangkok North 1, Thailand
- Tellus Data Center
- STT Bangkok 1
- NTT Bangkok 1 Data Center (BKK1)
- ETIX Bangkok #1
- NTT Bangkok 2 Data Center (BKK2)
- AIMS Bangkok 44 N Sathon Rd
- Telehouse – Bangkok
- ReadyIDC DC1
- ReadyIDC Edge DC2 - Srisaman
Route origin authorizations
A sample of 10 of this network’s 191 ROAs.
- 103.107.52.0/22 · max length /24
- 103.114.201.0/24 · max length /24
- 103.114.203.0/24 · max length /24
- 103.117.148.0/22 · max length /24
- 103.13.28.0/22 · max length /24
- 103.22.180.0/22 · max length /24
- 103.224.84.0/22 · max length /24
- 103.253.72.0/22 · max length /24
- 103.40.118.0/23 · max length /24
- 103.99.11.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS56309.
Blast radius
- Announced IPv4 addresses
- 30,720
- Threat-listed addresses
- 78
- Threat density
- 0.2539 %
- Routed prefixes
- 55
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 11 of this network’s 11 BGP neighbours.
- HURRICANE - Hurricane Electric LLC · AS6939
- SGGS-AS-AP - SG.GS · AS24482
- SBN-AWN-IIG-AS-AP - SBN-IIG/AWN-IIG transit provider · AS45430
- JASTEL-NETWORK-TH-AP - JasTel Network International Gateway · AS45629
- JASTEL-NETWORK-TH-NIX-AP - Jasmine International Tower · AS45642
- GSLNETWORKS-AS-AP - GSL Networks Pty LTD · AS137409
- IGCL-AS-AP - International gateway co., Ltd · AS137557
- DEX-AS-AP - DEXSERVER · AS146996
- METASMART-AS-AP - METASMART CO., LTD. · AS153657
- S2NITANDSERVICECOMPANYLIMITED-AS-TH - S2N IT AND SERVICE COMPANY LIMITED · AS153787
- RTNA-AS-AP - Triplify Cloud (Thailand) Co., Ltd. · AS154018
Reputation
15.4reputation score (NEUTRAL)
AS56309 (SIAMDATA-TH - Siamdata Communication Co.,Ltd., TH) has a reputation score of 59.3 (NEUTRAL).
- Threat density
- 42.9/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
- Siamdata Communication Co.,ltd.
- RIR
- APNIC
- Registered
- Tue, 21 Jun 2011 03:47:32 GMT
- Abuse contact
- admin@readyidc.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS56309 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.