Skip to content

Autonomous System

AS2018(ZA)

Last fetched

AS2018 is an Autonomous System registered in ZA. As of Sun, 19 Jul 2026 12:03:44 GMT, it announces 391 routed IP prefixes and peers with 47 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS2018Routing diversity10.0/10Peering density6.7/10MOAS conflict✓ noneThreat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/asn/2018

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS1103—NL
AS11537INTERNET2-RESEARCH-EDU - Internet2US
AS12779—IT
AS12859—NL
AS174COGENT-174 - Cogent Communications, LLCUS
AS17639—PH
AS1764—AT
AS20080AMPATH - Florida International UniversityUS
AS20562—NL
AS20766—FR
AS20965—NL
AS213241—BE
AS24482—SG
AS25091—CH
AS29075—FR
AS29632—BG
AS29838AMC - Atlantic Metro Communications II, Inc.US
AS31500—AG
AS3216—RU
AS329522—ZA
AS3303—CH
AS3333—NL
AS33891—DE
AS34019—FR
AS34549—DE
AS34927—CH
AS35280—FR
AS36944—MW
AS36982—ZA
AS37501—ZA
AS37520—ZA
AS37721—BF
AS39686—NL
AS48185—BE
AS48362—AT
AS50300—GB
AS50304—NO
AS50673—NL
AS5405—DE
AS56655—NO
AS61049—GB
AS6149—ZA
AS6204—RO
AS6939HURRICANE - Hurricane Electric LLCUS
AS8094—ZA
AS8359—RU
AS9002—GB

Blast radius

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

Blast radius: Computing — check back later. The precompute pipeline refreshes this panel within a few days.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS2018.

Cypher and MCP

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

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