ResearchRouting table, RPKI, IRR & looking glass

AS3582 University of Oregon

AS3582 (UONET) is registered to University of Oregon in US, through ARIN. It originates 7 prefixes in the global routing table.

5
IPv4 prefixes
2
IPv6 prefixes
149,504
IPv4 addresses
0%
RPKI valid

Who holds AS3582

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS3582
Handle
UONET
Organization
University of Oregon
Country
US
Registry
ARIN
ASPA
None published
WHOIS recordARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


ASNumber:       3582
ASName:         UONET
ASHandle:       AS3582
RegDate:        1994-05-11
Updated:        2024-06-13
Ref:            https://rdap.arin.net/registry/autnum/3582


OrgName:        University of Oregon
OrgId:          UNIVER-193-Z
Address:        UO Information Services
Address:        1225 Kincaid Street
City:           Eugene
StateProv:      OR
PostalCode:     97403
Country:        US
RegDate:        2021-08-12
Updated:        2023-03-03
Ref:            https://rdap.arin.net/registry/entity/UNIVER-193-Z


OrgAbuseHandle: UAD4-ARIN
OrgAbuseName:   UOnet Abuse Desk
OrgAbusePhone:  +1-541-346-4395 
OrgAbuseEmail:  abuse@uoregon.edu
OrgAbuseRef:    https://rdap.arin.net/registry/entity/UAD4-ARIN

OrgTechHandle: VANCE94-ARIN
OrgTechName:   Vance, Daniel 
OrgTechPhone:  +1-541-346-9724 
OrgTechEmail:  dvance@uoregon.edu
OrgTechRef:    https://rdap.arin.net/registry/entity/VANCE94-ARIN

OrgTechHandle: EDMIS1-ARIN
OrgTechName:   Edmiston, Jason 
OrgTechPhone:  +1-541-346-1759 
OrgTechEmail:  jfe@uoregon.edu
OrgTechRef:    https://rdap.arin.net/registry/entity/EDMIS1-ARIN

OrgTechHandle: JAD46-ARIN
OrgTechName:   Dominguez, Jose Alfredo
OrgTechPhone:  +1-541-346-4397 
OrgTechEmail:  jad@uoregon.edu
OrgTechRef:    https://rdap.arin.net/registry/entity/JAD46-ARIN

OrgNOCHandle: UONET-ARIN
OrgNOCName:   UOnet NOC
OrgNOCPhone:  +1-541-346-6387 
OrgNOCEmail:  uonethelp@uoregon.edu
OrgNOCRef:    https://rdap.arin.net/registry/entity/UONET-ARIN

RAbuseHandle: UAD4-ARIN
RAbuseName:   UOnet Abuse Desk
RAbusePhone:  +1-541-346-4395 
RAbuseEmail:  abuse@uoregon.edu
RAbuseRef:    https://rdap.arin.net/registry/entity/UAD4-ARIN

RTechHandle: VANCE94-ARIN
RTechName:   Vance, Daniel 
RTechPhone:  +1-541-346-9724 
RTechEmail:  dvance@uoregon.edu
RTechRef:    https://rdap.arin.net/registry/entity/VANCE94-ARIN

RNOCHandle: UONET-ARIN
RNOCName:   UOnet NOC
RNOCPhone:  +1-541-346-6387 
RNOCEmail:  uonethelp@uoregon.edu
RNOCRef:    https://rdap.arin.net/registry/entity/UONET-ARIN

RTechHandle: JAD46-ARIN
RTechName:   Dominguez, Jose Alfredo
RTechPhone:  +1-541-346-4397 
RTechEmail:  jad@uoregon.edu
RTechRef:    https://rdap.arin.net/registry/entity/JAD46-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#

What AS3582 announces

Prefixes originated by AS3582 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
5
IPv6 prefixes
2
IPv4 addresses
149,504 (584 /24s)
RPKI valid
0 0%
RPKI invalid
0
RPKI not found
7
ROAs naming AS3582
0
With an IRR route object
7 100%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

Who AS3582 is reached through

The AS just before AS3582 in the paths our looking glass collectors hold, for 7 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.