AS33973 Epam-AS Epam Systems FLLC

🇧🇾

Org handle: ORG-ESZ1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

7total

6 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)1,536

Announced (BGP)1,536

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)1.2×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2004-09-20

Announced Prefixes

(BGP)7

Prefix	RPKI	IRR	Last Seen
87.252.249.0/24	No ROA	RIPE	2026-10-10
91.120.43.0/24	Valid	RIPE	2026-10-10
213.184.231.0/24	No ROA	RIPE	2026-10-10
213.184.243.0/24	No ROA	RIPE	2026-10-10
217.21.56.0/24	No ROA	RIPE	2026-10-10
217.21.63.0/24	No ROA	RIPE	2026-10-10
2602:815::/48	Valid	ARIN	2026-10-10

(RIR)6

Prefix	Country	RIR	Status
87.252.249.0/24	🇧🇾 BY	RIPE	assigned
91.120.43.0/24	🇭🇺 HU	RIPE	assigned
213.184.231.0/24	🇧🇾 BY	RIPE	assigned
213.184.243.0/24	🇧🇾 BY	RIPE	assigned
217.21.56.0/24	🇧🇾 BY	RIPE	assigned
217.21.63.0/24	🇧🇾 BY	RIPE	assigned

(seen in AS paths)

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

ASPA

No ASPA

Abuse Contact

External Links

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 AS33973 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

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

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