Home ASN LookupAS25073

AS25073 INETKOM-AS LTD "KOMIN"

🇷🇺

Org handle: ORG-LA35-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

11total

11 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)2,816

Announced (BGP)2,816

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇷🇺 RU

RIR

RIPE NCC

Status

allocated

Allocated

2002-07-19

Announced Prefixes

(BGP)11

Prefix	RPKI	IRR	Last Seen
193.109.76.0/24	No ROA	RIPE	2026-10-10
193.109.77.0/24	No ROA	RIPE	2026-10-10
193.109.89.0/24	No ROA	RIPE	2026-10-10
194.145.168.0/24	No ROA	RIPE	2026-10-10
194.145.169.0/24	No ROA	RIPE	2026-10-10
194.145.170.0/24	No ROA	RIPE	2026-10-10
194.145.171.0/24	No ROA	RIPE	2026-10-10
195.140.204.0/24	No ROA	-	2026-10-10
195.140.205.0/24	No ROA	-	2026-10-10
195.140.206.0/24	No ROA	-	2026-10-10

1-10 of 11

1 / 2

Allocated Prefixes

(RIR)4

Prefix	Country	RIR	Status
193.109.76.0/23	🇷🇺 RU	RIPENCC	assigned
193.109.89.0/24	🇷🇺 RU	RIPENCC	assigned
194.145.168.0/22	🇷🇺 RU	RIPENCC	assigned
195.140.204.0/22	🇷🇺 RU	RIPENCC	assigned

All 11 announced prefixes of AS25073 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS44050PIN Petersburg Internet Network8
AS45054Metrobit3

ASPA

No ASPA

Abuse Contact

+31205354444

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 AS25073 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/25073

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

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