Autonomous system detail

AS755

Not announced

Operated by MERIT-AS-21 - Merit Network Inc..

Summary

// analyst note
Dormant/legacy ASN with zero announcements per two independent routing sources (bgp.he.net, bgp.tools). No PeeringDB entry and no AS755-specific peering policy exist; Merit's active operational network runs under a separate ASN, AS237, whose Selective peering policy must not be attributed to AS755. AS rank (79459, CAIDA's sentinel rank for unrouted ASNs), customer cone (singleton: 1 ASN / 0 prefixes / 0 addresses), and IPv4 address estimate (0, per RIPEstat) are sourced from CAIDA AS Rank and RIPEstat rather than left null.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-28; not in Spamhaus ASN-DROP (checked live); no NANOG archive or web search results tying AS755 to hijacks, leaks, or abuse.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: High

AS755 is a dormant legacy autonomous system number registered under ARIN to Merit Network, Inc., a nonprofit research-and-education network based in Ann Arbor, Michigan; live BGP monitors show it announcing zero IPv4 and zero IPv6 prefixes and not currently present in the global routing table.

Merit Network was founded in 1966 and historically re-engineered and operated the NSFNET backbone from 1987 until April 1995, later founding NANOG and RADb. AS755 (MERIT-AS-21) sits in a contiguous block of sequential Merit-assigned ASNs — AS750 through AS754 correspond to MERIT-AS-16 through MERIT-AS-20 — consistent with legacy per-institution numbering from Merit's NSFNET-era scheme, though no source documents AS755's specific original assignee or historical purpose.

Both Hurricane Electric's BGP toolkit (bgp.he.net) and bgp.tools independently confirm 0 announced IPv4/IPv6 prefixes and 0 observed peers for AS755; bgp.tools states explicitly that the ASN is not currently in the global routing table. AS755 has no PeeringDB entry (peeringdb.com/asn/755 returns a live HTTP 404), and no AS755-specific peering policy is published anywhere. Merit's actively operated ASN, AS237, is a separate registration with its own published Selective peering policy — that policy describes AS237, not AS755.

ARIN RDAP records AS755 (handle MERIT-AS-21) with status Active, a top-level registration event of 1990-10-08, and a last-changed date of 2012-04-02; this is corroborated independently by bgp.tools, which lists the ASN as established October 8, 1990. Because AS755 announces no prefixes, RPKI ROA coverage cannot be assessed.

Operator
Merit Network, Inc. (nonprofit R&E network; ARIN handle MERIT-AS-21, Ann Arbor, MI) [Confirmed] — https://rdap.arin.net/registry/autnum/755, https://www.merit.edu/about/
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/755
Allocated
1990-10-08 (ARIN RDAP autnum top-level registration event, corroborated by bgp.tools); last changed 2012-04-02 [Confirmed] — https://rdap.arin.net/registry/autnum/755, https://bgp.tools/as/755
Org status
active independent nonprofit corporation (Merit Network), governed by Michigan's public universities; founded 1966; ARIN record status Active [Confirmed] — https://rdap.arin.net/registry/autnum/755, https://www.merit.edu/about/
Contacts
abuse@merit.edu; HQ 880 Technology Drive, Suite B, Ann Arbor, MI 48108 [Confirmed] — https://rdap.arin.net/registry/autnum/755

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-28 — not in Spamhaus ASN-DROP (checked live), no NANOG archive or general web results naming AS755 in hijack/leak history

[Likely] — https://www.spamhaus.org/drop/asndrop.json, https://bgp.he.net/AS755

Network & routing

Network type
regional research-and-education (R&E) nonprofit network; AS755 is a legacy/dormant Merit ASN (Merit's active network runs under AS237) [Confirmed] — https://www.merit.edu/about/, https://bgp.tools/as/755
Size
dormant — 0 IPv4 and 0 IPv6 announced prefixes; not in the global routing table; IPv4 address estimate 0 (RIPEstat announced_space.v4.ips); CAIDA AS rank 79,459 (the standard sentinel rank for unrouted ASNs; not seen, not clique member); customer cone is a singleton — 1 ASN, 0 prefixes, 0 addresses
[Confirmed] — https://bgp.he.net/AS755, https://bgp.tools/as/755, https://api.asrank.caida.org/v2/restful/asns/755
Routing/peering
NOT announced — 0 prefixes, 0 peers on both bgp.he.net and bgp.tools; no PeeringDB entry for AS755 (404, confirmed live) and no AS755-specific peering policy published; AS237 (Merit's separate flagship ASN) runs a Selective policy that does not apply to AS755
[Confirmed] — https://www.peeringdb.com/asn/755, https://www.peeringdb.com/asn/237
RPKI
not assessable — AS755 announces no prefixes, so there is no ROA coverage to validate [Confirmed as absence] — https://bgp.he.net/AS755
Notable usage
no source documents AS755's specific historical assignee/purpose; it falls in a contiguous run of sequential Merit "MERIT-AS-1x/2x" registrations (AS750–AS754 = MERIT-AS-16 through MERIT-AS-20), consistent with legacy per-member-institution ASN assignments from Merit's NSFNET era
[Likely, pattern-based] — https://bgp.potaroo.net/cidr/autnums.html
Related ASNs
AS237 (Merit's active operational network, Selective peering); AS750–AS754 (contiguous MERIT-AS-16 through MERIT-AS-20 block) [Confirmed for AS237; Likely for the numbering pattern] — https://www.peeringdb.com/asn/237, https://bgp.potaroo.net/cidr/autnums.html
Analyst note
Dormant legacy ASN in Merit Network's sequential MERIT-AS block; WHOIS/RDAP resolves to Merit, but all live routing runs under AS237, not AS755. No PeeringDB entry and no AS755-specific peering policy exist — do not conflate with AS237's published Selective policy. CAIDA AS Rank places AS755 at 79,459 (CAIDA's sentinel rank for unrouted ASNs) with a singleton customer cone (1 ASN, 0 prefixes, 0 addresses); IPv4 address estimate is 0 per RIPEstat, not unmeasured.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.