asn.dev

Autonomous system

AS11441 FREDERICK-MEMORIAL-HOSPITAL

Unclassified ARIN

IPv4 addresses 256 1 prefixes
IPv6 prefixes 0 counted as prefixes, not addresses
Countries 1 mostly US
Exchanges 0 recorded by PCH
Upstreams 1 0 downstream
Flagged prefixes 0 none

Summary

Frederick Memorial Healthcare System (Frederick Health)

United States · AI-generated

enterprise legacy

FREDERICK-MEMORIAL-HOSPITAL belongs to the Frederick Memorial Healthcare System of Frederick, Maryland — the not-for-profit hospital and health system now trading as Frederick Health. It is a minimal enterprise AS.

What it's used for

RIS sees a single IPv4 prefix, 208.253.115.0/24 (256 addresses), no IPv6, and one observed neighbour. The prefix is registered in ARIN to Frederick Memorial Hospital, so the announcing organisation is also the registrant. The network handle is UU-208-253-115, a name inherited from UUNET-era address administration; that is a registry artefact of where the block originally came from, not evidence of a third party holding it today, and the org on the record is the hospital.

A hospital system's routed space is a small internet edge: published web presence, patient-portal and payer-facing endpoints, mail, and site-to-site or remote-access VPN terminations. Clinical systems themselves live on internal networks behind that edge. Nothing in the routing suggests otherwise — 256 addresses cannot carry a hosting estate, and there is no customer cone.

Notable

One observed neighbour is unusual even for an enterprise. Most organisations that bother with an AS number do so specifically to multihome, and would show two or more upstreams; a single adjacency means either one transit provider or a second path that RIS simply does not observe from its collectors. Either way, this is not a network selling connectivity to anyone.

Interesting

Healthcare providers are well represented among small legacy-number enterprise ASes: independent hospitals were early adopters of provider-independent space because clinical and payer connections cannot tolerate renumbering. The brand has since modernised to Frederick Health while the registry, as usual, still records the older name.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.

Transit providers

1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS7795LUMOS Networks, Inc.60

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-15, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 1 prefixes · 256 addresses IPv6 0 prefixes

CountryNamePrefixes
USUnited States of America1

Registry

Allocation record

ARIN · via Atlas (registry + RDAP)
Registry
ARIN
Handle
AS11441
Registry name
FREDERICK-MEMORIAL-HOSPITAL
Registrant
Frederick Memorial Healthcare System
Abuse contact
rsellers@frederick.health
Registered
2019-03-20
Last changed
2019-03-20
Allocation
assigned

Routing security

RPKI and IRR

Full detail
RPKI
0% valid · 0 valid, 1 with no ROA
ROAs
0 authorising AS11441
ASPA
no ASPA record
IRR
100% registered · 1 of 1 announcements
Route objects
1 naming AS11441

Reputation

Classification and threat

Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,782 prefixes, as published 2026-10-16. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check