Skip to main content

AS60517

AS-CABLEVISION

Upstream Peering - AS33891 CORE-BACKBONE

Registry

Authoritative registration data

AS number
60517
Name
AS-CABLEVISION
Organisation
Upstream Peering - AS33891 CORE-BACKBONE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS60517
178.157.96.0/22 IPv4 /22 not checked
185.118.244.0/22 IPv4 /22 not checked
185.131.180.0/22 IPv4 /22 not checked
185.175.212.0/22 IPv4 /22 not checked
185.27.120.0/22 IPv4 /22 not checked
185.36.92.0/22 IPv4 /22 not checked
185.51.128.0/22 IPv4 /22 not checked
185.91.172.0/22 IPv4 /22 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 AS60517
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 10,000 Mbps IPv4 · IPv6
VIX 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 AS60517 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS60517 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS60517 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

39 adjacencies that may be an artefact of collector peering

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.