Skip to main content

AS49106

OPTICOM-AS

Opticom Group AO

Registry

Authoritative registration data

AS number
49106
Name
OPTICOM-AS
Organisation
Opticom Group AO
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS49106
46.150.160.0/19 IPv4 /19 not checked
46.150.160.0/20 IPv4 /20 not checked
46.150.176.0/20 IPv4 /20 not checked
62.122.192.0/21 IPv4 /21 not checked
46.150.160.0/22 IPv4 /22 not checked
62.122.192.0/24 IPv4 /24 not checked
62.122.198.0/24 IPv4 /24 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 AS49106
Address families
CLOUD-IX MSK 7,000 Mbps IPv4
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 7,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 7,000 Mbps IPv4
W-IX: vlan800 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 AS49106 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS49106 in AS paths

Observed upstreams
Families
AS8641 384 1,150
v4
AS29076 233 615
v4
AS20764 RASCOM-AS 249 304
v4
AS1299 TWELVE99 90 239
v4
AS50384 W-IX_LTD 104 147
v4
AS51601 26 57
v4
AS9049 24 30
v4
AS20485 12 30
v4
AS50509 21 28
v4
AS25478 14 16
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS49106 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS35598 2 4
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.