Autonomous system
AS54531 LPCH-PA - LUCILE SALTER PACKARD CHILDREN'S HOSPITAL AT STANFORD
Unclassified ARIN
Summary
Lucile Packard Children's Hospital at Stanford
hospital healthcare business us
LPCH-PA is operated by Lucile Packard Children's Hospital at Stanford.
What it's used for
- The address space carries hospital infrastructure, with the primary netname
LPCH-PALOregistered to the hospital. - The AS announces 1280 IPv4 addresses across 2 prefixes and maintains 4 observed neighbours, indicating a small, self-contained corporate network rather than a transit or access provider.
- Traffic from this AS consists of internal hospital systems, clinical data, and administrative endpoints for the pediatric and obstetric care facility in Palo Alto.
Notable
- Registrants for the primary prefix
199.68.152.0/22align with the announcer, while the secondary prefix38.70.239.0/24is registered to Cogent Communications, LLC. - The address inventory is finely subdivided into two distinct blocks, consistent with an internal corporate estate managing separate segments for different operational needs.
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
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-06, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 1.28K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 2 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS54531- Registry name
- LPCH-PA
- Registrant
- LUCILE SALTER PACKARD CHILDREN'S HOSPITAL AT STANFORD
- Abuse contact
- syamanaka@stanfordchildrens.org
- Registered
- 2012-03-12
- Last changed
- 2019-06-14
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 2 with no ROA
- ROAs
- 0 authorising AS54531
- ASPA
- no ASPA record
- IRR
- 50% registered · 1 of 2 announcements
- Route objects
- 1 naming AS54531
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: 454 networks and 1,854 prefixes, as published 2026-11-06. 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