Skip to main content

AS43106

NEVACOM-AS

Nevacom Ltd

Registry

Authoritative registration data

AS number
43106
Name
NEVACOM-AS
Organisation
Nevacom Ltd
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS43106
91.108.44.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

Internet Exchange memberships listed for AS43106
Address families
GNM-IX 1,000 Mbps IPv4
Global-IX 1,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 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 AS43106 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS43106 in AS paths

Observed upstreams
Families
AS50509 470 631
v4
AS56534 52 69
v4
AS25091 IP-Max 8 16
v4
AS47692 NESSUS 4 8
v4
AS50673 Serverius-as 6 6
v4
AS137409 GSLNETWORKS-AS-AP 2 4
v4
AS9198 KAZTELECOM-AS 2 2
v4
AS60171 AFRIX-AS 2 2
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS43106 in AS paths

Observed downstreams
Families
AS56886 286 386
v4

No rows match “”.

Showing – of

Uncertain adjacencies

13 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 12
v4
AS13004 2 2
v4
AS28910 2 2
v4
AS35598 2 2
v4
AS37721 ORG-VTS1-AFRINIC 2 2
v4
AS41327 FIBERTELECOM-AS 2 2
v4
AS41722 2 2
v4
AS44901 belcloud 2 2
v4
AS49434 FBWNETWORKS 2 2
v4
AS200612 GulfBridgeInternational 2 2
v4
AS205112 PHILUNET 2 2
v4
AS208972 2 2
v4
AS209823 2 2
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.