Skip to main content

AS200000

Ukraine-AS

ORG-HUL6-RIPE

Registry

Authoritative registration data

AS number
200000
Name
Ukraine-AS
Organisation
ORG-HUL6-RIPE
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

31

IPv6 prefixes

17

Total announced

48

Announced prefixes

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

Prefixes announced by AS200000
173.242.48.0/20 IPv4 /20 not checked
217.173.208.0/20 IPv4 /20 not checked
109.205.96.0/21 IPv4 /21 not checked
37.139.64.0/21 IPv4 /21 not checked
46.247.80.0/21 IPv4 /21 not checked
185.104.44.0/22 IPv4 /22 not checked
185.124.8.0/22 IPv4 /22 not checked
185.149.40.0/22 IPv4 /22 not checked
185.209.168.0/22 IPv4 /22 not checked
185.225.212.0/22 IPv4 /22 not checked
185.226.24.0/22 IPv4 /22 not checked
185.233.116.0/22 IPv4 /22 not checked
185.233.120.0/22 IPv4 /22 not checked
185.233.136.0/22 IPv4 /22 not checked
185.233.152.0/22 IPv4 /22 not checked
185.233.36.0/22 IPv4 /22 not checked
185.233.40.0/22 IPv4 /22 not checked
185.233.44.0/22 IPv4 /22 not checked
185.234.176.0/22 IPv4 /22 not checked
185.235.168.0/22 IPv4 /22 not checked
185.239.180.0/22 IPv4 /22 not checked
185.25.116.0/22 IPv4 /22 not checked
185.39.224.0/22 IPv4 /22 not checked
185.65.244.0/22 IPv4 /22 not checked
185.68.16.0/22 IPv4 /22 not checked
185.69.152.0/22 IPv4 /22 not checked
91.222.136.0/22 IPv4 /22 not checked
194.247.12.0/23 IPv4 /23 not checked
195.64.184.0/23 IPv4 /23 not checked
91.206.200.0/23 IPv4 /23 not checked
45.154.218.0/24 IPv4 /24 not checked
2a04:8000::/29 IPv6 /29 not checked
2a05:480::/29 IPv6 /29 not checked
2a06:6440::/29 IPv6 /29 not checked
2a0c:6080::/29 IPv6 /29 not checked
2a0c:780::/29 IPv6 /29 not checked
2a0c:880::/29 IPv6 /29 not checked
2a0c:a80::/29 IPv6 /29 not checked
2a0c:c80::/29 IPv6 /29 not checked
2a0c:d80::/29 IPv6 /29 not checked
2a0c:e80::/29 IPv6 /29 not checked
2a0d:1100::/29 IPv6 /29 not checked
2a0d:6500::/29 IPv6 /29 not checked
2a0c:684::/30 IPv6 /30 not checked
2a0c:682::/31 IPv6 /31 not checked
2a00:7a60::/32 IPv6 /32 not checked
2a0c:681::/32 IPv6 /32 not checked
2001:67c:2070::/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

Internet Exchange memberships listed for AS200000
Address families
1-IX EU 40,000 Mbps IPv4 · IPv6
GNM-IX UA 10,000 Mbps IPv4 · IPv6

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

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS200000 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 689 10,847
v4 v6
AS9002 RETN-AS 97 1,778
v4 v6
AS1820 WNET 149 1,595
v4 v6
AS3326 Datagroup 186 1,381
v4 v6
AS50263 IXP-1-IX-EU 89 1,255
v4 v6
AS174 COGENT-174 77 722
v4 v6
AS13249 ITS-UA 46 368
v4 v6
AS8218 NEO-ASN 4 358
v4 v6
AS3255 UARNET-AS 11 122
v4 v6
AS47692 NESSUS 2 120
v4 v6
AS39351 ESAB-AS 2 88
v4 v6
AS49434 FBWNETWORKS 5 81
v4 v6
AS60171 AFRIX-AS 1 44
v4 v6
AS6204 ZET-NET 2 31
v4
AS42295 TBISS-AS 2 31
v4
AS9198 KAZTELECOM-AS 1 30
v4
AS15958 CETIN_doo_AS 1 30
v4
AS48648 KYIVLINK 1 17
v6
AS3303 SWISSCOM 3 4
v4 v6
AS50673 Serverius-as 2 2
v6
AS60812 IXP-1-IX-UA 2 2
v4 v6
AS6663 TTI-NET 1 1
v4
AS33891 CORE-BACKBONE 1 1
v6
AS56655 GIGAHOST 1 1
v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS200000 in AS paths

Observed downstreams
Families
AS200525 584 1,549
v4

No rows match “”.

Showing of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

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.