Skip to main content

AS49368

DOMOLAN-AS

+=======+ UPSTREAM TABLE +=======+

Registry

Authoritative registration data

AS number
49368
Name
DOMOLAN-AS
Organisation
+=======+ UPSTREAM TABLE +=======+
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS49368
188.126.32.0/20 IPv4 /20 not checked
188.126.48.0/20 IPv4 /20 not checked
188.94.32.0/21 IPv4 /21 not checked
2a14:9c7::/32 IPv6 /32 RPKI not found
2a14:9c0::/48 IPv6 /48 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 AS49368
Address families
CLOUD-IX MSK 40,000 Mbps IPv4
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4
GNM-IX 20,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 40,000 Mbps IPv4
PITER-IX Frankfurt 80,000 Mbps IPv4
PITER-IX Helsinki 80,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 80,000 Mbps IPv4
PITER-IX Rostov 80,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 80,000 Mbps IPv4
PITER-IX Tallinn: TLL_PEERING VLAN 80,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 AS49368 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS49368 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS49368 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

18 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.