Skip to content

Autonomous System

AS24319 — AKAMAI-TYO-AP - Akamai Technologies Tokyo ASN(SG)

Last fetched

AS24319 is an Autonomous System operated by AKAMAI-TYO-AP - Akamai Technologies Tokyo ASN and registered in SG. As of Tue, 04 Aug 2026 07:34:10 GMT, it announces 192 routed IP prefixes and peers with 11 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS24319Routing diversity10.0/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/24319

Routing footprint

AS24319 announces 192 distinct routed prefixes. The 25-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

11 distinct peers via BGP. The first 11 are listed below.

Peer ASNOperatorCountry
AS20940AKAMAI-ASN1 - Akamai International B.V.NL
AS2497IIJ - Internet Initiative Japan Inc.JP
AS2516KDDI - KDDI CORPORATIONJP
AS2914NTT-DATA-2914 - NTT America, Inc.US
AS3491PCCWG-APAC-HK - PCCW Global (HK) Ltd.HK
AS4637ASN-TELSTRA-GLOBAL - Telstra GlobalHK
AS4755TATACOMM-AS - TATA Communications formerly VSNL is Leading ISPIN
AS4766KIXS-AS-KR-KR - Korea TelecomKR
AS55836RELIANCEJIO-IN - Reliance Jio Infocomm LimitedIN
AS9286KINXIDC-AS-KR-KR - KINXKR
AS9498BBIL-AP - BHARTI Airtel Ltd.IN

Blast radius

Count of dependent hostnames if AS24319 disappeared from the routing table.

10,446 hostnames depend on this network.Exact count across all 192 announced prefixes. Snapshot Tue, 14 Jul 2026 11:00:56 GMT.

MOAS / hijack watch

Prefixes routed by AS24319 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.

No active MOAS conflicts. Every prefix announced by AS24319 is unique to AS24319 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS24319.

Cypher and MCP

Reproduce the headline metric directly against graph.whisper.security:

MATCH (a:ASN {name: "AS24319"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS country

Or query Whisper from your own LLM workflow via the Whisper MCP server.