GraniteIX is a carrier-neutral Internet Exchange serving Salt Lake City and the surrounding Wasatch Front metros — built on next-generation architecture with community at its core.
No preferred providers. No hidden agendas. Every network participates as an equal on the GraniteIX fabric.
Born from a passion for networking and the Wasatch Front tech community. We exist to serve local networks, not corporate interests.
Our fabric is built on modern, flexible principles — engineered for reliability, scalability, and long-term growth.
Contact our NOC at [email protected] for pricing and onboarding, or visit the member portal to get started.
View our full profile on PeeringDB: peeringdb.com/ix/4622
Our Story GraniteIX was founded out of a clear observation: the Salt Lake City metro and broader Wasatch Front lacked diversity in the Internet Exchange space. As the region’s tech sector grew rapidly, local network operators had limited options for peering and traffic exchange — a gap that constrained competition, resiliency, and community-driven growth.
Our Footprint GraniteIX serves the Salt Lake City metro and the broader Wasatch Front corridor — one of the fastest-growing technology markets in the United States. Our infrastructure is strategically positioned to serve the region’s growing network operator community. Primary Coverage Salt Lake City Metro GraniteIX is present in the following Salt Lake City area carrier-neutral data centers:
Join GraniteIX GraniteIX operates an open peering policy. We welcome any network that operates in or serves the Salt Lake City metro and Wasatch Front region — no minimum traffic requirements, no exclusivity clauses. Connection Options Standard IX Ports Connect to the shared GraniteIX fabric and peer with all participants via our route servers or bilateral sessions.
Overview GraniteIX (AS401542) operates redundant route servers that support large (32-bit) BGP communities for route filtering and traffic engineering. Standard 2-octet communities are not supported — only large communities in the format 401542:function:target are accepted. The default behavior is to announce all routes to all peers. There is no need to tag routes with the default announce community (401542:1:0) unless you are re-applying it after a more specific filter.