Home ASN LookupAS51816

AS51816 ASTEC-AS ACTUAL I.T. d.d.

🇸🇮

Org handle: ORG-AA240-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

1total

1 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)256

Announced (BGP)256

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇸🇮 SI

RIR

RIPE NCC

Status

allocated

Allocated

2010-11-10

Announced Prefixes

(BGP)1

Prefix	RPKI	IRR	Last Seen
91.220.107.0/24	Valid	RIPE	2026-10-10

Allocated Prefixes

(RIR)1

Prefix	Country	RIR	Status
91.220.107.0/24	🇸🇮 SI	RIPENCC	assigned

All 1 announced prefix of AS51816 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

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

AS43061SI STELKOM D.O.O1

Transfer History

Registry transfers of AS51816 between organisations.

AS51816M&A · 2026-01-26
PRO.ASTEC d.o.o.
🇸🇮 SI RIPE NCC
→
ACTUAL I.T. d.d.
🇸🇮 SI RIPE NCC
AS51816M&A · 2020-12-07
Astec d.o.o.
RIPE NCC
→
PRO.ASTEC d.o.o.
RIPE NCC

Date	Resource	From	To	Type
2026-01-26	AS51816	PRO.ASTEC d.o.o. 🇸🇮 SI RIPE NCC	ACTUAL I.T. d.d. 🇸🇮 SI RIPE NCC	M&A
2020-12-07	AS51816	Astec d.o.o. RIPE NCC	PRO.ASTEC d.o.o. RIPE NCC	M&A

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 AS51816 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/51816

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

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