Skip to main content

AS46512

UT-MEDICAL-CENTER

University of Tennessee Medical Center

Registry

Authoritative registration data

AS number
46512
Name
UT-MEDICAL-CENTER
Organisation
University of Tennessee Medical Center
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS46512
165.6.0.0/16 IPv4 /16 not checked
165.6.0.0/17 IPv4 /17 not checked
165.6.0.0/18 IPv4 /18 RPKI not found
165.6.128.0/18 IPv4 /18 RPKI not found
50.144.16.0/24 IPv4 /24 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS46512 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS46512 in AS paths

Observed upstreams
Families
AS701 UUNET 259 975
v4
AS3450 UTK 283 397
v4
AS22909 COMCAST-22909 252 323
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS46512 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS7018 ATT-INTERNET4 1 1
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.