BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Organisation profile

Organisation

Yury Kirsanov

Yury Kirsanov is a person lead in public internet-number registry records tied to AS136584, helping readers trace links to ASNs, number resources, or network-operations records.

The available evidence covers Legal type: person, Network identity: AS59204, Related networks: 37, and ASNs: 1.

Source description Yury Kirsanov is listed as a person in internet infrastructure or governance records in GB; available references connect the entry to 1 ASN, one supporting public reference.

United KingdomLatest 2026-08-02
  • 1ASNs
  • 37Relationships
Location
United Kingdom
Legal type
person
Network identity
AS59204
Related networks
37

Confidence

1
Information type
Public internet-number registry, RDAP, WHOIS, or routing evidence connects Yury Kirsanov to internet-number resources; current affiliation, public responsibility, and responsibility boundary still require independent verification.

Related details

Last updated: 2026-06-18

Current status

Legal type:personNot yet assessed

Network identity

1
AS59204

Related networks

37
Relationship topology: Yury KirsanovEQUINIX ACQUISITION ENTPRS B.…FALCORE INVEST PTY LTDAS148968RIPE NETWORK COORDINATION CEN…AS15830EQUINIX ACQUISITION ENTPRS B.…Equinix Equinix (EMEA) Acquis…FALCORE-AS-AP - Falcore Inves…Yury Kirsanov
This entityupstream / providerdownstream / customerpeercorporate / legalother

The entity sits in the centre; its customers fan out to the left and its upstream providers to the right (arrows show transit direction). Scroll or use the buttons to zoom · drag the background to pan · click a node to open it in the directory.

Data as of 2026-06

The entity sits on the left and its connections fan out by role on the right; the graph shows each group’s most confident connections, and the full list below carries every relationship.

Full list

EQUINIX ACQUISITION ENTPRS B.V.
downstreamHigh confidence· 3 records· 3 unrated· Latest 2026-06downstreamMedium confidence· 13 records· 13 unrated· Latest 2026-06
EQUINIX ACQUISITION ENTPRS B.V.
downstreamHigh confidence· Latest 2026-06
CLOUDFLARENET
downstreamMedium confidence· 3 records· 3 unrated· Latest 2026-06
FALCORE1-AS-AP ChannelCo.
downstreamMedium confidence· 3 records· 3 unrated· Latest 2026-06
DPL-AS-AP - DGTEK PTY LTD
downstreamMedium confidence· 4 records· 4 unrated· Latest 2026-06
ASN-TELSTRA
downstreamMedium confidence· 2 records· 2 unrated· Latest 2026-06
WIDEBAND-AS-AP
downstreamMedium confidence· 2 records· 2 unrated· Latest 2026-06
FALCORE-AS-AP - Falcore Investments Pty Ltd
downstreamHigh confidence· Latest 2026-06
Equinix Equinix (EMEA) Acquisition Enterprises B.V.
downstreamHigh confidence· Latest 2026-06
OPTUSCOM-AS01-AU SingTel Optus Pty Ltd
downstreamMedium confidence· Latest 2026-06
ASIA PACIFIC NETWORK INFORMATION CENTREAS7474
downstreamMedium confidence· 6 records· 6 unrated· Latest 2026-06
ASIA PACIFIC NETWORK INFORMATION CENTREAS149515
downstreamMedium confidence· 8 records· 8 unrated· Latest 2026-06
FALCORE INVEST PTY LTDAS148968
downstreamHigh confidence· 5 records· 5 unrated· Latest 2026-06

Other relationships

1
103.242.182.0/24
route originMedium confidence· 3 records· 3 medium· Latest 2026-08

People & contacts

2
Contact:Administrative contactHigh confidence· 2 records
Contact:Administrative contactNot yet assessed· 2 records

Related research

1
  • Yury Kirsanov and the Operational Troubleshooting Record Behind VoIP Systems

    Public issue trackers and technical mailing lists preserve a kind of infrastructure work that company biographies rarely show. Yury Kirsanov appears in official VoIPline material as a co-founder and technical leader, but the more useful evidence for readers is narrower: dated OpenSIPS and Asterisk records in which he described operating problems, tested a configuration hypothesis, and reported what happened next. Those records do not make him the author of an upstream fix, and they do not transfer every company result to one person. They do show how voice infrastructure becomes more dependable through observation, reproducible questions, bounded changes, and careful reporting. That distinction matters because operational continuity is built in running systems, not in titles alone.

    Primary articlePublished 2026-08-09