Skip to main content

AS44460

MEDIACENTER-AS

------------------------------------

Registry

Authoritative registration data

AS number
44460
Name
MEDIACENTER-AS
Organisation
------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS44460
92.43.200.0/21 IPv4 /21 not checked
185.68.72.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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS44460 in AS paths

Observed upstreams
Families
AS62214 RACKFOREST-AS 251 601
v4
AS6939 HURRICANE 27 29
v4
AS33891 CORE-BACKBONE 7 13
v4
AS15576 NTS 7 8
v4
AS47692 NESSUS 2 8
v4
AS21215 UGNI 1 2
v4
AS50261 ACENET 1 2
v4
AS6663 TTI-NET 1 1
v4
AS15958 CETIN_doo_AS 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS44460 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 2
v4
AS40994 Alwyzon 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.