AS270141 REHEDMEX S.A de C.V

🇲🇽

Org handle: 323309

LACNICallocated

Announced Prefixes (BGP)

38total

1 IPv437 IPv6

IPv4 Addresses

Allocated (RIR)0

Announced (BGP)256

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)4.4×10²⁵

Prefix Limit (IPv4)

Prefix Limit (IPv6)

200

Country

RIR

Status

allocated

Allocated

2021-12-15

Announced Prefixes

(BGP)38

Prefix	RPKI	IRR	Last Seen
38.225.237.0/24	No ROA	Other IRR	2026-10-11
2806:3dc:1::/48	Valid	-	2026-10-11
2806:3dc:3::/48	Valid	-	2026-10-11
2806:3dc:4::/48	Valid	-	2026-10-11
2806:3dc:5::/48	Valid	-	2026-10-11
2806:3dc:6::/48	Valid	-	2026-10-11
2806:3dc:7::/48	Valid	-	2026-10-11
2806:3dc:8::/48	Valid	-	2026-10-11
2806:3dc:9::/48	Valid	-	2026-10-11
2806:3dc:a::/48	Valid	-	2026-10-11

1-10 of 38

1 / 4

(RIR)1

Prefix	Country	RIR	Status
2806:3dc::/32	🇲🇽 MX	LACNIC	allocated

(seen in AS paths)

Networks AS270141 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 AS270141 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/270141" | jq