Autonomous System
AS48678
Last fetched
AS48678 is operated by TR-PENTECH-AS - Pentech Bilisim Teknolojileri Sanayi Ve Ticaret Limited Sirketi, registered in TR, and announces 39 prefixes to 17 BGP neighbours. AS48678 has a reputation score of 14.2 (NEUTRAL); 8 of its 10,496 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 39
- BGP neighbours
- 17
- RPKI ROAs
- 166
- MOAS conflicts
- 5
- CAIDA AS-rank
- 1,599
- Customer-cone ASNs
- 21
- Facilities
- 78
- Internet exchanges
- 5
- Customer degree
- 18
- Peer degree
- 1
- Provider degree
- 4
- 5.181.85.0/24
- 31.58.200.0/22
- 31.210.48.0/24
- 45.11.96.0/24
- 45.11.97.0/24
- 45.11.98.0/24
- 45.11.99.0/24
- 62.106.94.0/24
- 77.92.146.0/24
- 78.135.66.0/24
- 78.135.72.0/24
- 78.135.104.0/24
- 81.18.55.0/24
- 85.153.142.0/24
- 134.255.199.0/24
- 149.3.171.0/24
- 176.96.130.0/24
- 178.211.130.0/24
- 185.7.241.0/24
- 185.17.139.0/24
- 185.229.15.0/24
- 185.231.110.0/24
- 188.132.153.0/24
- 188.132.185.0/24
- 188.132.189.0/24
Routing posture
- Hijack posture score
- 0.18
- Origin mismatches
- 1
Infrastructure presence
Internet exchanges (5 total)
Facilities (78 total)
- Telehouse - London (Docklands North)
- NIKHEF Amsterdam
- Equinix FR5 - Frankfurt, KleyerStrasse
- Digital Realty Frankfurt FRA1-27
- Digital Realty VIE1/2 - Vienna
- Telehouse - Paris 2 (Voltaire - Léon Frot)
- Digital Realty AMS9 - Amsterdam
- Equinix SK1 - Stockholm, Bromma
- Speedbone Berlin
- Moscow M9
- CE Colo Prague
- Digital Realty Marseille MRS1/2/3/4
- Digital Realty Stockholm STO1-6
- Dataplex Budapest
- Linxdatacenter (Moscow)
- NewTelco Kiev
- NXDATA-1 Bucharest (BUH1)
- Sitel Bratislava
- LIM Warsaw
- Equinix WA1 - Warsaw, Centrum LIM
- Ucomline Kiev
- Sofia Data Center (SDC)
- TELEPOINT Sofia Centre
- Bolshaya Morskaya 18
- Equinix SK2 - Stockholm, Sköndal
Route origin authorizations
A sample of 10 of this network’s 166 ROAs.
- 45.59.70.0/24 · max length /24
- 45.192.19.0/24
- 104.143.203.0/24 · max length /24
- 104.143.216.0/24 · max length /24
- 109.175.218.0/24 · max length /24
- 109.175.222.0/24 · max length /24
- 13.143.211.0/24 · max length /24
- 13.143.218.0/24 · max length /24
- 13.143.226.0/24 · max length /24
- 13.143.238.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS48678.
Blast radius
- Announced IPv4 addresses
- 10,496
- Threat-listed addresses
- 8
- Threat density
- 0.0762 %
- Routed prefixes
- 38
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 17 of this network’s 17 BGP neighbours.
- TTNet - Turk Telekomunikasyon Anonim Sirketi · AS9121
- Equinix - Equinix (EMEA) Acquisition Enterprises B.V. · AS15830
- StormNetworks - Storm Networks LLC · AS43298
- SPEX - SPEX YAZILIM VE SIBER GUVENLIK HIZMETLERI ANONIM SIRKETI · AS57397
- STORMWALL-AS - StormWall s.r.o. · AS59796
- sentreva - Sentreva Internet Hizmetleri Anonim Sirketi · AS199797
- OnurBilisim-AS - Ahmet Onur Guney trading as Onur Bilisim Ve Yazilim Hizmetleri · AS201021
- Onetra - Onetra Bilisim Teknolojileri San. Tic. LTD. STI. · AS203393
- AS-OZBAY - OZBAY BILISIM INTERNET HIZMETLERI LIMITED SIRKETI · AS203511
- hostturka - CND Medya Reklam ve Internet Hizmetleri Tic. Ltd. Sti. · AS203810
- NODE - NODE INTERNET VE BILISIM HIZMETLERI LTD. STI. · AS204205
- VDSGLOBAL - Pembe Gul Isguzar Karagoz · AS205463
- BUULDY - Emre Mert Delidere trading as Buuldy Bilisim · AS207582
- ASGENCBT - Genc BT Bilisim Teknolojileri Limited Sirketi · AS209828
- SFCTEK - SFCTEK Bilisim Yazilim ve Telekomunikasyon Hiz. San. ve Tic. LTD. STI. · AS212598
- ULTAHOST-AS - Ultahost, Inc. · AS214036
- ADEOXTECH - ADEOX · AS397563
MOAS / hijack watch
5 announced prefixes conflict with AS48678 — another network announces the same address space. A sample:
Reputation
14.2reputation score (NEUTRAL)
AS48678 (TR-PENTECH-AS - Pentech Bilisim Teknolojileri Sanayi Ve Ticaret Limited Sirketi, TR) has a reputation score of 61.6 (NEUTRAL).
- Threat density
- 49.4/100
- Graph metrics
- 80.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
- RIR
- RIPE
- Registered
- Thu, 31 Dec 2020 09:22:50 GMT
- Abuse contact
- abuse@pendc.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS48678 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.