Home ASN LookupAS197570

AS197570 BladeX BladeX Networks LLC

🇺🇸

Org handle: ORG-BNL50-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

6total

6 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)1,536

IPv6 Addresses

Allocated (RIR)1.2×10²⁴

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇺🇸 US

RIR

RIPE NCC

Status

allocated

Allocated

2026-05-15

Announced Prefixes

(BGP)6

Prefix	RPKI	IRR	Last Seen
31.77.110.0/24	Invalid	-	2026-10-11
31.77.219.0/24MOAS	Invalid	-	2026-10-11
169.40.100.0/24	Valid	Other IRRRIPE	2026-10-11
178.83.89.0/24	Valid	Other IRRRIPE	2026-10-11
212.189.105.0/24MOAS	Invalid	-	2026-10-11
217.217.205.0/24	Valid	Other IRRRIPE	2026-10-11

Allocated Prefixes

(RIR)5

Prefix	Country	RIR	Status
31.77.110.0/24	🇪🇺 EU	RIPE	assigned
31.77.219.0/24	🇪🇺 EU	RIPE	assigned
178.83.89.0/24	🇲🇪 ME	RIPE	assigned
212.189.105.0/24	🇹🇭 TH	RIPE	assigned
2a06:9801:2fb::/48	🇺🇸 US	RIPE	assigned

All 6 announced prefixes of AS197570 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS8849MELBICOM EU Melbikomas UAB4
AS30058FDCservers.Net2

Transfer History

Registry transfers of AS197570 between organisations.

AS197570Transfer · 2019-07-08
Kan Sp z o.o.
RIPE NCC
→
KOBA Sp. z o.o.
RIPE NCC

Date	Resource	From	To	Type
2019-07-08	AS197570	Kan Sp z o.o. RIPE NCC	KOBA Sp. z o.o. RIPE NCC	Transfer

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 AS197570 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/197570

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

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