AS262612 Piotr Piwowar

🇧🇷

Org handle: 134666

LACNICallocated

Announced Prefixes (BGP)

43total

30 IPv413 IPv6

IPv4 Addresses

Allocated (RIR)6,144

Announced (BGP)18,432

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)1.7×10²⁹

Prefix Limit (IPv4)

100

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2011-10-14

Announced Prefixes

(BGP)43

Prefix	RPKI	IRR	Last Seen
177.85.192.0/21	Valid	-	2026-10-11
177.85.192.0/22	Valid	-	2026-10-11
177.85.192.0/24	Valid	-	2026-10-11
177.85.193.0/24	Valid	-	2026-10-11
177.85.194.0/24	Valid	-	2026-10-11
177.85.195.0/24	Valid	-	2026-10-11
177.85.196.0/22	Valid	-	2026-10-11
177.85.196.0/24	Valid	-	2026-10-11
177.85.197.0/24	Valid	-	2026-10-11
177.85.198.0/24	Valid	-	2026-10-11

1-10 of 43

1 / 5

(RIR)3

Prefix	Country	RIR	Status
177.85.192.0/21	🇧🇷 BR	LACNIC	allocated
191.242.80.0/20	🇧🇷 BR	LACNIC	allocated
2804:6e4::/32	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

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

ASPA

No ASPA

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 AS262612 should publish an ASPA object
IPv4 transfers in the LACNIC 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/262612" | jq