Home ASN LookupAS39513

AS39513 ONECOM-AS TOV ONECOM

🇺🇦

Org handle: ORG-OA656-RIPE

=== IXP ===

RIPE NCCallocated

Announced Prefixes (BGP)

1total

1 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)1,024

IPv6 Addresses

Allocated (RIR)3×10²⁶

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇺🇦 UA

RIR

RIPE NCC

Status

allocated

Allocated

2006-03-10

Announced Prefixes

(BGP)1

Prefix	RPKI	IRR	Last Seen
193.93.76.0/22	Valid	RIPE	2026-10-11

Allocated Prefixes

(RIR)2

Prefix	Country	RIR	Status
193.93.76.0/22	🇺🇦 UA	RIPENCC	assigned
2a0c:d540:fe00::/40	🇺🇦 UA	RIPE	assigned

All 1 announced prefix of AS39513 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

Networks AS39513 hands its own prefixes to: transit providers, or peers at an exchange.

AS50263IXP 1 IX EU A Systems Sp. Z O.O1

Downstreams (1)

Networks whose own prefixes AS39513 passes on: usually its customers.

AS43998TRINITY KYIV Cifrovye Dispetcherskie Sistemy1

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

Learn more

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS39513 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Open

GEThttps://api.ipctl.io/v1/asn/39513

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/39513" | jq