Skip to main content

AS122

UPMC-AS122

UPMC

Registry

Authoritative registration data

AS number
122
Name
UPMC-AS122
Organisation
UPMC
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

1

Total announced

13

Announced prefixes

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

Prefixes announced by AS122
128.147.0.0/16 IPv4 /16 not checked
150.232.0.0/16 IPv4 /16 not checked
151.195.0.0/16 IPv4 /16 not checked
157.229.0.0/16 IPv4 /16 not checked
205.223.240.0/20 IPv4 /20 not checked
198.136.8.0/21 IPv4 /21 not checked
198.55.8.0/21 IPv4 /21 not checked
128.147.75.0/24 IPv4 /24 not checked
157.229.75.0/24 IPv4 /24 not checked
192.80.29.0/24 IPv4 /24 not checked
198.177.199.0/24 IPv4 /24 not checked
198.184.147.0/24 IPv4 /24 not checked
2605:e900::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS122
Address families
PIT-IX: Peering-1500 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

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 AS122 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS122 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 156 1,640
v4 v6
AS174 COGENT-174 125 1,195
v4 v6
AS6939 HURRICANE 113 464
v4 v6
AS7016 CCCH-3 15 121
v4 v6
AS701 8 78
v4 v6
AS20326 TERASWITCH 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS122 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
AS19151 BBO-1 1 26
v4 v6

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.