Skip to main content

AS50004

DKS-AS

Zhytomyr home network

Registry

Authoritative registration data

AS number
50004
Name
DKS-AS
Organisation
Zhytomyr home network
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS50004
31.43.0.0/20 IPv4 /20 not checked
31.43.16.0/20 IPv4 /20 not checked
195.211.172.0/22 IPv4 /22 not checked
2001:678:1f4::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS50004 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS50004 in AS paths

Observed upstreams
Families
AS3326 Datagroup 507 1,291
v4 v6
AS6939 HURRICANE 19 60
v4
AS14840 ASN14840 2 15
v4
AS6663 TTI-NET 1 3
v4
AS199995 OT-AS 1 3
v4
AS264409 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS50004 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 6
v4
AS212483 level86 1 6
v4
AS48919 1 3
v4
AS198150 SIACOM-AS 1 3
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.