Autonomous System
AS23674
Last fetched
AS23674 is operated by NAYATEL-PK - Nayatel (Pvt) Ltd, registered in PK, and announces 550 prefixes to 19 BGP neighbours. AS23674 has a reputation score of 14.4 (NEUTRAL); 602 of its 145,152 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 550
- BGP neighbours
- 19
- RPKI ROAs
- 601
- MOAS conflicts
- 0
- CAIDA AS-rank
- 1,535
- Customer-cone ASNs
- 22
- Facilities
- 0
- Internet exchanges
- 0
- Customer degree
- 21
- Peer degree
- 0
- Provider degree
- 3
- 45.115.84.0/24
- 45.115.85.0/24
- 45.115.84.0/22
- 45.115.86.0/24
- 45.115.87.0/24
- 58.65.128.0/24
- 58.65.129.0/24
- 58.65.130.0/24
- 58.65.131.0/24
- 58.65.132.0/24
- 58.65.133.0/24
- 58.65.134.0/24
- 58.65.135.0/24
- 58.65.136.0/24
- 58.65.137.0/24
- 58.65.138.0/24
- 58.65.139.0/24
- 58.65.140.0/24
- 58.65.141.0/24
- 58.65.142.0/24
- 58.65.143.0/24
- 58.65.128.0/19
- 58.65.144.0/24
- 58.65.145.0/24
- 58.65.146.0/24
Route origin authorizations
A sample of 10 of this network’s 601 ROAs.
- 154.192.0.0/16 · max length /24
- 154.192.64.0/24 · max length /24
- 154.192.69.0/24 · max length /24
- 101.50.100.0/24 · max length /24
- 101.50.101.0/24 · max length /24
- 101.50.102.0/24 · max length /24
- 101.50.103.0/24 · max length /24
- 101.50.104.0/24 · max length /24
- 101.50.105.0/24 · max length /24
- 101.50.106.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS23674.
Blast radius
- Announced IPv4 addresses
- 145,152
- Threat-listed addresses
- 602
- Threat density
- 0.4147 %
- Routed prefixes
- 491
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 19 of this network’s 19 BGP neighbours.
- CLOUDFLARENET - Cloudflare, Inc. · AS14789
- PKTELECOM-AS-PK - Pakistan Telecommunication Company Limited · AS17557
- TWA-AS-AP - Transworld Associates (Pvt.) Ltd. · AS38193
- SKYTELECOM-AS-PK - House # 39 Street 38 F10 /4 · AS55453
- BYTENESTS-AS-AP - Bytenests Pvt Ltd · AS132103
- FFCL-AS-AP - Fauji Fertilizer Company Limited · AS134357
- IWEB-AS-AP - I-WEB · AS134663
- NAYATEL-AS-AP - Naya Tel (Pvt.) Limited · AS136818
- BDTPL-AS-AP - Big Data Technologies Pvt Ltd · AS141234
- GPL-AS-AP - Grand Tel Private Limited · AS142063
- LRPL-AS-AP - LMK Resources Pakistan (Private) Limited · AS147055
- DSIPL-AS-AP - Dubai Sky Internet · AS149009
- TELEHOUSEPVTLTD-AS-AP - TeleHouse Pvt Ltd · AS150108
- DOTSISNETWORK-AS-AP - DOTSIS NETWORK · AS150324
- PTABPL-AS-AP - Pace Telecom and Brodcasting Private Limited · AS150371
- MTCL-AS-AP - Mansoorah Telecommunications Company Pvt Ltd · AS150671
- PBPL-AS-AP - PLAY BROADBAND (PRIVATE) LIMITED · AS151330
- JAVEDNETFIRM-AS-AP - Javed Net · AS154386
- MULTILINK-AS-AP - Multilink Communications Pvt Ltd · AS154755
Reputation
14.4reputation score (NEUTRAL)
AS23674 (NAYATEL-PK - Nayatel (Pvt) Ltd, PK) has a reputation score of 61.3 (NEUTRAL).
- Threat density
- 48.7/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
- Registered to
- Naya Tel (Pvt.) Limited
- RIR
- APNIC
- Registered
- Thu, 04 Sep 2008 06:40:34 GMT
- Abuse contact
- abuse@nayatel.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS23674 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.