asn.dev

Autonomous system

AS13999 Mega Cable, S.A. de C.V.

Unclassified LACNIC

IPv4 addresses 1.95M 957 prefixes
IPv6 prefixes 333 counted as prefixes, not addresses
Countries 1 mostly MX
Exchanges 1 recorded by PCH
Upstreams 7 29 downstream
Flagged prefixes 0 none

Summary

Mega Cable

Mexico · AI-generated

isp telecom infrastructure

Nearly two million addresses whose reverse names announce which city each customer is in and whether they share an address.

What it's used for

  • A national cable broadband network. 1,970,176 addresses across 962 IPv4 prefixes plus 327 IPv6 prefixes, all announced from Mexico.

Notable

  • The largest blocks are 177.226.0.0/16, 187.240.0.0/16 and 187.242.0.0/16.
  • Netnames are the address ranges themselves, in the form 177.224.0.0 - 177.231.255.255.
  • Every sampled address returned a name. They take the form customer-GDL-PUBLIC-CGN-32-0.megared.net.mx, with a three or four letter city code, an optional PUBLIC, and the last two octets.
  • The routing status lookup failed, so neighbour count and first-seen date are unknown.
  • The registry lookup for 177.224.192.0/18 failed.

Interesting

  • CGN marks addresses shared between many subscribers rather than assigned to one. Publishing that in reverse DNS tells anyone querying an address whether it identifies a household or a few hundred of them, which matters enormously to anyone trying to act on an address.
  • The word PUBLIC appears alongside CGN on some names and not others, so the same naming scheme distinguishes shared space from dedicated space within one city. That distinction is usually invisible from outside a provider.
  • The netnames are the first and last address of each range. Where other registries take a short label, this one records the boundaries, which makes the field useless as an identifier and perfect as a description.
  • Eighteen sampled addresses gave eleven different city codes. A provider that labels every address with its location has built its reverse DNS from the same inventory that tracks where the equipment physically is.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

Recorded at 1 exchange in 1 country, largest first.

ExchangeLocationTheir address
MEX-IX McAllenMcAllen, United States206.71.142.17

Transit providers

7 upstream, 29 downstream and 53 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS32098Transtelco Inc82,443
AS174Cogent Communications, LLC40,732
AS3356Level 3 Parent, LLC8,354
AS3491PCCW Global (HK) Ltd.6,336
AS1299Arelion Sweden AB4,346
AS6762TELECOM ITALIA SPARKLE S.p.A.1,402
AS8151UNINET33

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 957 prefixes · 1.95M addresses IPv6 333 prefixes

CountryNamePrefixes
MXMexico1,290

Registry

Allocation record

LACNIC · via Atlas (registry data)
Registry
LACNIC
Registered
1999-10-01
Allocation
allocated

Routing security

RPKI and IRR

Full detail
RPKI
66% valid · 1,756 valid, 913 with no ROA
ROAs
168 authorising AS13999
ASPA
no ASPA record
IRR
100% registered · 2,669 of 2,669 announcements
Route objects
272 naming AS13999

Reputation

Classification and threat

Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 440 networks and 1,773 prefixes, as published 2026-10-13. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check