Skip to content

Autonomous System

AS147181 — FLAREZENLTD-AS-AP - Flarezen Ltd.(BD)

Last fetched

AS147181 is an Autonomous System operated by FLAREZENLTD-AS-AP - Flarezen Ltd. and registered in BD. As of Wed, 12 Aug 2026 18:39:34 GMT, it announces 15 routed IP prefixes and peers with 13 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS147181Routing diversity6.0/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/147181

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS135103ALEX-NEO-AS-AP - Alex NeoSG
AS136557HOST-AS-AP - Host Universal Pty LtdAU
AS137967DIGICON-ISP-AS - Digicon Telecommunication LtdBD
AS138594COLOCITY-AS-AP - CoLoCity LtdBD
AS151323NAMEPART-AS-AP - NamepartBD
AS151368GOTMYHOST-AS-AP - GOTMYHOSTBD
AS154112NEXELOGYLTD-AS-AP - Nexelogy Ltd.BD
AS17471CYBERNET-BD-AS - Grameen Cybernet Ltd. Bangladesh. AS for local peering and transit. DhakaBD
AS203915ISHRAK-203915 - Ishrak RahmanBD
AS205563zGato - Marc GomezES
AS30058FDCSERVERS - FDCservers.netUS
AS38067RADIANT - Radiant Communications LimitedBD
AS63969RACEONLINE-BD - Race Online LimitedBD

Blast radius

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

21,433 hostnames depend on this network.Exact count across all 17 announced prefixes. Snapshot Fri, 29 May 2026 22:01:16 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS147181.

Cypher and MCP

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

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