Skip to main content

AS205226

MediaNet_AS

ORG-RA98-RIPE

Registry

Authoritative registration data

AS number
205226
Name
MediaNet_AS
Organisation
ORG-RA98-RIPE
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 AS205226
185.108.19.0/24 IPv4 /24 RPKI valid
212.113.111.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 AS205226
Address families
PITER-IX Moscow: MSK_PEERING_VLAN 40,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 40,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 AS205226 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS205226 in AS paths

Observed upstreams
Families
AS50509 TRANSROUTE 263 481
v4
AS29076 CITYTELECOM-AS 46 77
v4
AS1299 TWELVE99 14 21
v4
AS25091 IP-Max 6 9
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS205226 in AS paths

Observed downstreams
Families
AS208380 ASMIRAM 163 197
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 6
v4
AS37721 ORG-VTS1-AFRINIC 2 3
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.