Skip to main content

AS207656

EPINATURA

Ukrainian Data Network

Registry

Authoritative registration data

AS number
207656
Name
EPINATURA
Organisation
Ukrainian Data Network
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS207656
193.218.118.0/24 IPv4 /24 not checked
193.218.119.0/24 IPv4 /24 not checked
2a0f:e586::/32 IPv6 /32 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 AS207656
Address families
DTEL-IX: PUBLIC — IPv4 · IPv6
Giganet IXN: Global exchange 10,000 Mbps IPv4 · IPv6
RUDAKI-IX 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 AS207656 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS207656 in AS paths

Observed upstreams
Families
AS29632 NASSIST-AS 375 720
v4 v6
AS8772 NLineLLC 354 654
v4 v6
AS211509 RUDAKI-AS 59 121
v4 v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS207656 in AS paths

Observed downstreams
Families
AS209630 273 342
v4
AS8772 NLineLLC 57 117
v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS207301 1 1
v6

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.