Skip to content

Autonomous System

AS18233PTTNET Philippine Telegraph and Telephone Corporation(PH)

Last fetched

AS18233 is an Autonomous System operated by PTTNET Philippine Telegraph and Telephone Corporation and registered in PH. As of Thu, 21 May 2026 10:51:44 GMT, it announces 36 routed IP prefixes and peers with 11 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS18233Routing diversity7.8/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/18233

Routing footprint

AS18233 announces 36 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
AS6939HURRICANE - Hurricane Electric LLCUS
AS140708VITROINC-AS-AP VITRO INC.PH
AS137406ACI-AS-AP Airlive Communications Inc.PH
AS135607INFINIVAN-AS-AP Infinivan IncorporatedPH
AS132454PTTNET Philippine Telegraph and Telephone CorporationPH
AS132193SSSGOV-AS-AP Social Security SystemPH
AS63927RISE-HK RISEHK
AS38909ARDION-AS-AP ARLINE BERBA ESTRADA ta ARDION LINE WEB DESIGNPH
AS38609AMDATEX-PH-AS American Data Exchange Corporation Ltd.PH
AS17895GLOBALREACH-AP Globalreach eBusiness Networks, Inc.PH
AS14110GENESYS-ASN - Genesys Telecommunications Laboratories,Inc.US

Blast radius

Approximate count of dependent hostnames if AS18233 disappeared from the routing table.

~414 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 10:51:44 GMT.

MOAS / hijack watch

Prefixes routed by AS18233 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 AS18233 is unique to AS18233 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS18233.

Cypher and MCP

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

MATCH (a:ASN {name: "AS18233"})-[: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.