Skip to content

Autonomous System

AS3754 — NYSERNET3-AS - NYSERNet(US)

Last fetched

AS3754 is an Autonomous System operated by NYSERNET3-AS - NYSERNet and registered in US. As of Wed, 20 May 2026 21:52:39 GMT, it announces 1 routed IP prefix and peers with 15 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS3754Routing diversity1.5/10Peering density4.8/10MOAS conflict✓ noneThreat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/asn/3754

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS12NYU-DOMAIN - New York UniversityUS
AS397066MIRANDA-AS Miranda-Media LLCUS
AS54177CHB-WAN - CORNHUSKER BANKUS
AS46621DERYTELECOM - Cogeco Connexion incUS
AS33703HT-OLD-NEXUS - Uniti Fiber Holdings Inc.US
AS32360VENTURACOUNTY - County of VenturaUS
AS25935Vogel Solucoes em Telecom e Informatica SAUS
AS23171OHIO-IX - OHIO IXUS
AS17324ALNET - Yeshiva UniversityUS
AS16813AMNH - American Museum of Natural HistoryUS
AS11872SYRACUSE-UNIVERSITY - Syracuse UniversityUS
AS11537INTERNET2-RESEARCH-EDU - Internet2US
AS5719SUNYSB - State University of New York at Stony BrookUS
AS4190BINGHAMTON-U - Binghamton UniversityUS
AS3756NYSERNET3-AS - NYSERNetUS

Blast radius

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

No dependent hostnames recorded for this network.Snapshot Wed, 20 May 2026 21:52:39 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS3754.

Cypher and MCP

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

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