Skip to content

Autonomous System

AS264014 — AS264014 - Led Internet Eireli(BR)

Last fetched

AS264014 is an Autonomous System operated by AS264014 - Led Internet Eireli and registered in BR. As of Sun, 06 Sep 2026 18:01:43 GMT, it announces 10 routed IP prefixes and peers with 13 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS264014Routing diversity5.2/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/264014

Routing footprint

AS264014 announces 10 distinct routed prefixes. The 10-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
AS24482SGGS-AS-AP - SG.GSSG
AS263508AS263508 - SIMNET TELECOMUNICACOES LTDABR
AS264963AS264963 - LUMIAR TELECOMUNICACOESBR
AS265131AS265131 - GP4 SERVICOS E TECNOLOGIA LTDABR
AS265359AS265359 - gotcha net internet providerBR
AS266062AS266062 - R2 DADOS LTDA - MEBR
AS267613AS267613 - ELETRONET S.A.BR
AS271413AS271413 - E O L CASTRO TELECOMUNICACOES EIRELIBR
AS271418AS271418 - freynet telecomBR
AS37721Virtual Technologies & Solutions - Virtual Technologies & SolutionsBF
AS52468AS52468 - UFINET PANAMA S.A.PA
AS52549AS52549 - NET PREMIUM LTDA - MEBR
AS6939HURRICANE - Hurricane Electric LLCUS

Blast radius

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

30 hostnames depend on this network.Exact count across all 10 announced prefixes. Snapshot Fri, 17 Jul 2026 01:00:52 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS264014.

Cypher and MCP

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

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