Skip to main content

AS41802

KVIDEX-AS

*====== Upstreams ======*

Registry

Authoritative registration data

AS number
41802
Name
KVIDEX-AS
Organisation
*====== Upstreams ======*
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS41802
93.182.0.0/18 IPv4 /18 RPKI not found
93.182.28.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 AS41802
Address families
GNM-IX 10,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 2,048 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 AS41802 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS41802 in AS paths

Observed upstreams
Families
AS57304 RETNRU-AS 56 128
v4
AS35598 INETCOM 31 65
v4
AS1299 TWELVE99 19 49
v4
AS8732 COMCOR-AS 20 39
v4
AS6939 HURRICANE 11 20
v4
AS47692 NESSUS 2 8
v4
AS8218 NEO-ASN 2 6
v4
AS25091 IP-Max 2 4
v4
AS25159 SONICDUO-AS 2 2
v4
AS6204 ZET-NET 1 2
v4
AS6663 TTI-NET 1 2
v4
AS50673 Serverius-as 1 2
v4
AS56655 GIGAHOST 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS41802 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 8
v4
AS37721 ORG-VTS1-AFRINIC 1 2
v4
AS49544 i3Dnet 1 2
v4
AS49673 TRUENETWORK 1 2
v4
AS200612 GulfBridgeInternational 1 2
v4
AS205112 PHILUNET 1 2
v4
AS208972 1 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.