AS215261 VIPY-AS ByteFly Kft

🇭🇺

Org handle: ORG-BK192-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

7total

6 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)1,280

Announced (BGP)1,536

IPv6 Addresses

Allocated (RIR)1.2×10²⁴

Announced (BGP)1.2×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2024-03-22

Announced Prefixes

(BGP)7

Prefix	RPKI	IRR	Last Seen
45.146.6.0/24	Valid	RIPE	2026-10-09
94.156.37.0/24	Valid	RIPE	2026-10-09
167.148.167.0/24MOAS	Valid	Other IRRRIPE	2026-10-09
212.73.137.0/24	Valid	RIPE	2026-10-09
213.181.206.0/24	No ROA	-	2026-10-09
222.167.192.0/24MOAS	Invalid	-	2026-10-09
2001:67c:fac::/48	Valid	RIPE	2026-10-09

(RIR)6

Prefix	Country	RIR	Status
45.146.6.0/24	🇭🇺 HU	RIPENCC	allocated
94.156.37.0/24	🇭🇺 HU	RIPENCC	allocated
212.73.137.0/24	🇭🇺 HU	RIPE	assigned
213.181.206.0/24	🇭🇺 HU	RIPE	assigned
222.167.192.0/24	🇪🇺 EU	RIPE	assigned
2001:67c:fac::/48	🇭🇺 HU	RIPENCC	assigned

(seen in AS paths)

Networks AS215261 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 AS215261 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/215261" | jq