Skip to main content

AS206663

MTS-MEDIA

--- Peering At INEX ---

Registry

Authoritative registration data

AS number
206663
Name
MTS-MEDIA
Organisation
--- Peering At INEX ---
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS206663
185.94.46.0/24 IPv4 /24 not checked
185.94.47.0/24 IPv4 /24 RPKI valid
37.203.54.0/24 IPv4 /24 RPKI valid
37.203.55.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

Internet Exchange memberships listed for AS206663
Address families
INEX LAN1: INEX LAN1 10,000 Mbps IPv4
INEX LAN2 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS206663 in AS paths

Observed upstreams
Families
AS174 COGENT-174 231 520
v4
AS39122 BLACKNIGHT-AS 168 406
v4
AS6939 HURRICANE 24 60
v4
AS6204 ZET-NET 2 5
v4
AS3303 SWISSCOM 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS206663 in AS paths

Observed downstreams
Families
AS205743 munster 139 166
v4
AS212493 ClearWave 139 166
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS13237 LAMBDANET-AS 2 5
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.