Autonomous system
AS122 UPMC-AS122 - UPMC
Unclassified ARIN Enterprise
Summary
University of Pittsburgh Medical Center (UPMC)
enterprise legacy
An early allocation (UPMC-AS122) serving the University of Pittsburgh Medical Center, a large academic health system in Pittsburgh, Pennsylvania.
What it's used for
- Clinical, research, and administrative networking across a large integrated healthcare system.
Notable
- An institutional network for a major academic medical center, not commercial hosting. The low AS number marks it as an early-internet allocation.
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
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| Pittsburgh Internet Exchange | Pittsburgh, United States | 206.71.141.22 |
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 28 prefixes · 271K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 29 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS122- Registry name
- UPMC-AS122
- Registrant
- UPMC
- Abuse contact
- infosecabuse@upmc.edu
- Registered
- 1987-08-21
- Last changed
- 2020-01-09
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- UPMC AS122
- Also known as
- University of Pittsburgh Medical Center
- Network type
- Enterprise
- Scope
- Regional
- Traffic ratio
- Not Disclosed
- Peering policy
- Selective
- Present at
- 1 exchanges
- Website
- http://www.upmc.com
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 8% valid · 1 valid, 12 with no ROA
- ROAs
- 1 authorising AS122
- ASPA
- no ASPA record
- IRR
- 92% registered · 12 of 13 announcements 1 other origin
- Route objects
- 17 naming AS122
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