Skip to main content

AS59514

DARNYTSIA-NET

Darnytsia Networks (Darnytsia.Net)

Registry

Authoritative registration data

AS number
59514
Name
DARNYTSIA-NET
Organisation
Darnytsia Networks (Darnytsia.Net)
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 AS59514
45.10.88.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 AS59514
Address families
1-IX UA 10,000 Mbps IPv4
Giganet IXN: Global exchange 10,000 Mbps IPv4
UA-IX 20,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 AS59514 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS59514 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 25,325 154,130
v4
AS6768 913 3,917
v4
AS6663 151 491
v4
AS48641 SYNTEGRA-AS 252 359
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS59514 in AS paths

Observed downstreams
Families
AS48693 776 3,507
v4

No rows match “”.

Showing of

Uncertain adjacencies

100 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS57463 NetIX 3,095 15,652
v4
AS13335 CLOUDFLARENET 1,025 7,390
v4
AS15169 GOOGLE 24 4,696
v4
AS24482 SGGS-AS-AP 237 2,699
v4
AS13188 TRIOLAN 1 1,630
v4
AS12741 398 1,141
v4
AS13194 BITE 114 1,075
v4
AS16276 OVH 218 1,057
v4
AS3326 189 1,016
v4
AS35320 162 710
v4
AS20804 ASN-TELENERGO 243 678
v4
AS3255 140 662
v4
AS60812 127 659
v4
AS44592 116 604
v4
AS24724 177 592
v4
AS8772 41 465
v4
AS12578 157 448
v4
AS21497 64 444
v4
AS28917 80 362
v4
AS15895 KSNET-AS 50 320
v4
AS31148 5 311
v4
AS6849 UKRTELNET 35 288
v4
AS49544 i3Dnet 35 226
v4
AS50581 UTG 34 205
v4
AS1820 15 173
v4
AS49453 GLOBALLAYER 14 155
v4
AS35297 50 144
v4
AS12963 VOLZ 64 136
v4
AS199995 OT-AS 50 124
v4
AS48648 26 117
v4
AS203446 33 103
v4
AS60068 19 103
v4
AS44600 45 98
v4
AS8801 ROCKETFIBRE 28 92
v4
AS8926 MOLDTELECOM-AS 4 85
v4
AS42739 25 83
v4
AS62206 28 82
v4
AS48278 9 76
v4
AS13307 7 68
v4
AS41820 NOVI-AS 15 66
v4
AS48422 IT-STARCOM-AS 14 63
v4
AS34251 IMC-AS 5 58
v4
AS49824 15 55
v4
AS39608 LANETUA-AS 13 55
v4
AS15497 Colocall 17 54
v4
AS56347 MEDIANA-AS 12 47
v4
AS21488 EMPLOT-AS 17 46
v4
AS24812 ASHOMENET 3 46
v4
AS6846 21 45
v4
AS29491 14 45
v4
AS31272 4 45
v4
AS43668 BIGNET-AS 25 44
v4
AS6876 TENET-AS 5 43
v4
AS25133 1 42
v4
AS60159 EUROLINE-NET 15 41
v4
AS43139 MAXIMUMA-AS 15 39
v4
AS59497 5 38
v4
AS41096 TIM-UMAN-AS 1 37
v4
AS49183 7 35
v4
AS24703 UN-UKRAINE-AS 7 34
v4
AS20940 AKAMAI-ASN1 2 34
v4
AS42331 2 34
v4
AS34700 5 33
v4
AS200000 2 33
v4
AS44032 1 33
v4
AS3920 PUSHPKT 12 32
v4
AS41540 8 32
v4
AS13249 12 29
v4
AS201814 9 27
v4
AS199524 GCORE 7 27
v4
AS29107 6 27
v4
AS12593 AS12593 13 26
v4
AS41435 UNDERNET-AS1 9 26
v4
AS43633 6 26
v4
AS49544 i3Dnet 5 26
v4
AS42512 X-COM-AS 2 26
v4
AS200081 1 26
v4
AS34867 COSMONOVA-AS 16 25
v4
AS42396 3 24
v4
AS204384 1 24
v4
AS12687 URAN 10 23
v4
AS28907 MIROHOST 9 23
v4
AS42905 LIMANET 6 23
v4
AS35213 COMPNETUA-AS 5 23
v4
AS196645 HOSTPRO-AS 1 23
v4
AS61297 DATACENTER-UA 10 20
v4
AS42352 QOS 5 20
v4
AS8788 9 19
v4
AS31725 4 19
v4
AS31445 2 18
v4
AS32934 FACEBOOK 2 18
v4
AS41985 2 17
v4
AS41009 VIZITNETUA-AS 7 16
v4
AS15377 2 16
v4
AS25521 2 16
v4
AS41710 2 16
v4
AS3261 1 16
v4
AS48239 ITTV-AS 12 15
v4
AS16223 3 15
v4
AS58349 2 15
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.