Summary

  • Public registry, routing and lookup sources identify autonomous system AS18404 as HyderabadIX, described as a non-profit internet exchange point located in Hyderabad, India.
  • The same sources do not establish the exchange's current routing footprint, its operating entity or the scale of its peering fabric, while Hyderabad's live interconnection market is served by commercially operated platforms.

The identity line is unusually consistent for an organisation with so little else on the record. Public registry, routing and lookup sources describe AS18404 as an established autonomous system based in Hyderabad, India, and describe its function as an internet exchange rather than a transit or access network; the same set of public references names it directly as HyderabadIX, a non-profit internet exchange point in that city (public registry and lookup records, as-overview context, registry mirror, regional registry reference). That is the strongest statement the public record presently supports, and it is worth reading literally: the exchange is publicly identified, not publicly confirmed as operating.

The gap opens on the question an operator would ask first. When did AS18404 last appear in the global routing table? The collected public routing and registry sources do not answer it (routing view, exchange database context). Registration and reachability are different facts. An autonomous system record can remain current long after prefixes stop being announced, and a registry entry carries no obligation to announce traffic. Readers who treat registration as a proxy for an operating peering fabric will overstate continuity in exactly the way this record invites.

A second gap concerns dates. Registration data for AS18404 was reported as updated within a September 2025 window, without a single precise update date being retrievable from the consulted sources (registry mirror, regional registry reference). That ambiguity is not trivial in incident and continuity work, where the difference between a stale record and a recently refreshed one changes how much weight a reviewer should place on it.

Set against that thin record, Hyderabad's working interconnection market is comparatively well documented. DE-CIX India maintains presence across multiple data centres in the city, and its Hyderabad platform is the named commercial option most visible in public material (DE-CIX India, operator overview). Colocation and connectivity providers active in Hyderabad include CtrlS Datacenters, Tata Communications, Sify, AdaniConneX and Zenlayer (provider material, market listing, facility directory), and Extreme IX is also named among the exchange platforms serving the city (DE-CIX India, operator overview). The practical consequence is structural: Hyderabad's traffic exchange is not waiting for a non-profit exchange point to return to the routing table, because commercially operated fabrics and carrier-neutral facilities already anchor the market.

One further attribution deserves caution rather than repetition. Search-provider material describes the initiative as run by the Amaravati People Foundation as a non-profit effort. No inspectable page text confirming that attribution was obtained during this work (lookup record), so it is reported here as an unconfirmed second-hand claim, not as an accepted fact about the operator.

Why does any of this matter beyond one directory card? Non-profit exchange points exist to lower the cost of keeping domestic traffic domestic: they let regional networks, content caches and public institutions exchange routes without paying transit for traffic that never needed to leave the country. When such an exchange fades from the routing table, the immediate harm is rarely dramatic — traffic reroutes through commercial fabrics that charge for the privilege, latency and cost rise modestly, and the market absorbs it. The harm that persists is informational.

Communities that cannot distinguish a dormant exchange from an undocumented one cannot plan interconnection capacity, cannot audit public-interest connectivity claims, and cannot tell whether a non-profit commitment was quietly retired.

The correction is unglamorous and entirely verifiable. A registry query settles the registration status of AS18404; an independent routing-visibility lookup settles whether it announces prefixes today; an exchange database entry settles who participates. Each is a bounded, dated check. What none of them can supply is the discipline of asking for it — the point at which a published claim about an exchange's role is created rather than merely copied forward. That duty belongs to whoever publishes the claim.

The Exchange remains a real, identifiable organisation, and its directory entry is reachable here: HyderabadIX in the BTW directory. The honest position today is that the public record identifies it and then stops. Reporting that boundary is more useful than manufacturing the detail that would cross it.