Skip to main content

AS42798

VOLSNET-AS

Sergey Vyacheslavovich Gliga

Registry

Authoritative registration data

AS number
42798
Name
VOLSNET-AS
Organisation
Sergey Vyacheslavovich Gliga
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 AS42798
91.193.124.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 AS42798
Address families
1-IX EU 10,000 Mbps IPv4
1-IX UA 10,000 Mbps IPv4
DTEL-IX: PUBLIC 10,000 Mbps IPv4
Giganet IXN Odesa: Odessa local exchange 10,000 Mbps IPv4
Giganet IXN: Global exchange 10,000 Mbps IPv4
RUDAKI-IX 1,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 AS42798 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS42798 in AS paths

Observed upstreams
Families
AS34187 137 191
v4
AS199995 OT-AS 92 102
v4
AS50263 56 66
v4
AS44837 8 11
v4
AS8218 NEO-ASN 3 9
v4
AS49434 2 2
v4
AS42295 TBISS-AS 1 1
v4
AS60812 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS42798 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 6
v4
AS1257 SWIPNET 1 1
v4
AS48919 1 1
v4
AS50629 LWLCOM 1 1
v4
AS209823 1 1
v4
AS211509 1 1
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.