Autonomous system
AS16519 CUDENVER
Unclassified ARIN
Summary
University of Colorado Denver
education research infrastructure
Two blocks, two campuses, and the netnames are the only place the second campus is named.
What it's used for
- A university's network. Three prefixes announced from the United States, one of them IPv6, one hundred and thirty-one thousand and seventy-two addresses, through two observed BGP neighbours.
Notable
- Both IPv4 blocks are at the largest prefix size in common use, and both are registered to the same university under its city name.
- The netnames differ. One is two letters for the university system and the city, matching the AS handle exactly. The other is those same two letters and a different campus name entirely.
- That second campus appears nowhere else in the record. The registrant field on both blocks is identical, so only the netname distinguishes them.
- The two blocks come from unrelated parent ranges, one of them allocated long after the other.
- Six addresses were queried for reverse DNS and none returned a name.
Interesting
- A university with a medical campus usually ends up with two networks and one legal entity. Here the split is recorded in the one field nobody validates, which makes the netname the most informative thing in the record.
- Two allocations at the largest common size, for one institution, is what arriving early looked like. The second block came later and at the same size, which is unusual: by then, allocations this large were hard to justify.
- Nothing published in reverse DNS across a hundred and thirty thousand addresses is the campus norm. The names exist inside; the outside gets numbers.
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-10-30, 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 · 131K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 3 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS16519- Registry name
- CUDENVER
- Registrant
- University of Colorado Denver
- Abuse contact
- piotr.artwich@ucdenver.edu
- Registered
- 2000-05-05
- Last changed
- 2026-01-07
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- University of Colorado Denver
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Website
- https://www.ucdenver.edu
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
- 100% valid · 3 valid, 0 with no ROA
- ROAs
- 4 authorising AS16519
- ASPA
- no ASPA record
- IRR
- 100% registered · 3 of 3 announcements
- Route objects
- 4 naming AS16519
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: 447 networks and 1,848 prefixes, as published 2026-10-31. 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