Skip to main content

AS42518

UNETCOM-AS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Registry

Authoritative registration data

AS number
42518
Name
UNETCOM-AS
Organisation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

0

Total announced

12

Announced prefixes

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

Prefixes announced by AS42518
146.120.64.0/20 IPv4 /20 not checked
146.120.64.0/21 IPv4 /21 not checked
146.120.72.0/21 IPv4 /21 not checked
146.120.80.0/21 IPv4 /21 not checked
146.120.80.0/22 IPv4 /22 not checked
146.120.84.0/22 IPv4 /22 not checked
91.192.188.0/22 IPv4 /22 not checked
91.215.120.0/22 IPv4 /22 not checked
91.192.188.0/23 IPv4 /23 not checked
91.192.190.0/23 IPv4 /23 not checked
91.215.120.0/23 IPv4 /23 not checked
91.215.122.0/23 IPv4 /23 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 AS42518
Address families
GNM-IX 10,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4
MSK-IX Saint-Petersburg: MSK-IX Saint-Petersburg peering network 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 AS42518 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS42518 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 118 608
v4
AS20764 RASCOM-AS 90 464
v4
AS8218 NEO-ASN 4 112
v4
AS25091 IP-Max 7 104
v4
AS33891 CORE-BACKBONE 7 72
v4
AS6939 HURRICANE 13 56
v4
AS50629 LWLCOM 6 48
v4
AS47692 2 48
v4
AS137409 GSLNETWORKS-AS-AP 4 44
v4
AS57304 9 36
v4
AS50673 3 32
v4
AS34927 iFog-GmbH 2 24
v4
AS39351 ESAB-AS 2 24
v4
AS41327 FIBERTELECOM-AS 2 24
v4
AS61049 2 24
v4
AS42295 TBISS-AS 2 20
v4
AS49434 2 20
v4
AS56911 2 16
v4
AS6663 1 12
v4
AS9198 1 12
v4
AS15958 1 12
v4
AS13194 1 8
v4
AS62000 1 8
v4
AS56655 GIGAHOST 1 4
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS42518 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

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 120
v4
AS3170 1 12
v4
AS13004 1 12
v4
AS28910 1 12
v4
AS29049 1 12
v4
AS35598 1 12
v4
AS36236 NETACTUATE 1 12
v4
AS37721 ORG-VTS1-AFRINIC 1 12
v4
AS41722 1 12
v4
AS44901 1 12
v4
AS49673 TRUENETWORK 1 12
v4
AS51185 MAINSTREAMING-AS 1 12
v4
AS199524 GCORE 1 12
v4
AS200612 GulfBridgeInternational 1 12
v4
AS205112 PHILUNET 1 12
v4
AS208972 1 12
v4
AS209823 1 12
v4
AS28917 1 8
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.