Summary
- The Hawai‘i Internet Exchange is administered by the University of Hawai‘i Information Technology Services, not by the carrier-hotel owner, and it describes itself as free: membership is open to Hawai‘i government, education and research networks, and HIX states that it does not charge to establish peering with a participant.
- One of its two peering points is a colocated router inside DRFortress’s data centre near Honolulu Airport, and HIX’s own technical specification requires connections there to be made through DRFortress’s commercial DRFxchange fabric — no direct connection to the HIX router permitted.
- So the free part is an instrument: eligibility, BGP-4, a registered AS number, routes originating in Hawai‘i, a signed agreement. The paid part is a door: circuit, cross-connect and colocation, and neither operator publishes a price for any of them.
Start with the correction
The exchange on the Honolulu fabric is not operated by the owner of the carrier hotel. That premise was worth testing and it fails on the publisher’s own pages. The Hawai‘i Internet Exchange is managed and funded by the University of Hawai‘i Information Technology Services to keep local government, education and research traffic local to the state, and UH ITS administers its administrative and routing policies under AS19035 (HIX home page; HIX About page). DRFortress LLC runs a different exchange inside its own building, DRFxchange, and HIX maintains a peering with it.
What survives the correction is better than the premise. A university runs the rulebook and charges nothing for it; a commercial landlord owns the room where half of that rulebook has to be executed.
Two peering points, one of them rented
HIX describes two peering points in Honolulu: the UH ITS data centre on the University of Hawai‘i at Mānoa campus, and a colocated router at the DRFortress data centre near Honolulu Airport (HIX About page). Access is Ethernet at either point, with other methods arranged case by case. Membership is open to all government, education and research network providers in the state. A participant must run BGP-4 only, hold a valid registered AS number, originate routes within Hawai‘i, sign and return the HIX agreement, and establish a circuit before connecting (HIX How to Join page).
The money sentence is on the same page, and it is narrow: “HIX does not charge to establish a peering with a network participant.” The next sentence hands the rest back — circuit costs and colocation fees at DRFortress are the responsibility of the participant (HIX How to Join page). That is a fee waiver on one object and a shrug on every other object in the transaction.
The 2013 decision that made the split permanent
HIX’s About page prints its own history, and the hinge is 2013: “In 2013 the University decided to un-commercialize the HIX and focus on Government, Education and Research Networks. Most (if not all) commercial local service providers were peering with the DRFortress IX at the DRFortess colocation site.” (HIX About page).
Read that as the publisher’s account, because no board minute or resolution behind it was obtained. But it explains the architecture now in front of a reader: one fabric for public-sector and research networks, a second fabric for commercial networks, both reachable in the same city, one of them physically inside a commercial colocation room.
2009, in the specification’s own words
A colocated router is a piece of equipment with an address and a policy. What the exchange requires at that address is printed in the technical specification, version 3.6, dated 21 April 2009 — a document that says of itself that it may be superseded in whole or in part.
Its operative sentence is unambiguous: “HIX connections via Ethernet at DRFortress must be made through the DRFortess IX – no direct connection to the HIX router at DRFortress shall be permitted.” (HIX Technical Specification v3.6, 21 April 2009). The same document splits address administration: DRFortress IX addresses are administered by DRFortress, while the Mānoa addresses are administered by UH ITS. It also excludes Tier-1 ISPs with nationwide backbones from peering, except on a case-by-case exemption.
Put plainly: at one of the two sites, the exchange’s own rule says you do not connect to the exchange. You connect to the landlord’s fabric and meet the exchange there.
Two exchanges, one building
DRFortress describes DRFxchange as the largest commercial internet exchange in the state of Hawaii, offering low-cost peering access and cross-connections inside its data centre, on a fully redundant peering exchange LAN that supports port-based VLANs (DRFortress DRFxchange page). Its address is printed as 3375 Koapaka Street, Suite D-198, Honolulu, Hawaii 96819. Those adjectives — largest, low-cost — are the publisher’s own and carry no figure.
The registry numbers are the only counts available. PeeringDB’s record for the DRFortress exchange, ix/267, organises it under DRFortress LLC in Honolulu and lists 35 peers, 41 connections, 22 open-policy peers and total capacity of 2.4T, on IPv4 LAN 206.197.210.0/25 and IPv6 LAN 2606:7c80:3375:50::/64 with MTU 1500, route servers AS26212 at 206.197.210.7 and 206.197.210.8 at 400G; that record was last updated 22 January 2020 (PeeringDB exchange record ix/267).
HIX’s side of the same directory is thin. Its exchange record, ix/189, notes that it offers routes from Hawaii facilities to Hawaii facilities only, prints LAN prefixes 205.166.205.0/24 and 2607:f278:2:4::/64, lists exactly one connected network — University of Hawaii AS6360 at 10G — and was last updated 2 February 2023 (PeeringDB exchange record ix/189). The AS19035 record types HIX as an educational/research network with an open general policy, no ratio requirement and contract requirement not required, and lists a single public peering connection at the DRFortress exchange at 10G, IPv4 206.197.210.10 and IPv6 2606:7c80:3375:50::10, last updated 7 February 2023 (PeeringDB AS19035 record).
DRFortress’s own 2026 contacts sheet lists the same HIX connection at ASN 19035 on a 1G exchange port, gives DRFortress’s ASN as 40300, offers a multilateral peering agreement or bilateral arrangements, and points readers to ix/267 for participants. It prints no port price and no cross-connect price (DRFxchange contacts sheet, 2026).
The landlord is not only a landlord. A Federal Communications Commission public notice dated 30 May 2025 records DR Fortress as a licensee on the Hawaiki cable system under licence SCL-LIC-20160906-000019 and as the operator and manager of the Oahu, Hawaii cable landing station; the notice concerns transfers of control accepted for filing, not a final grant (FCC Public Notice, Report No. SCL-00550NS). No cable capacity, length or landing count enters this article from that document, and none should.
The arithmetic, and the reconciliation I refuse
Three comparisons are mine, computed from the records’ own fields, and printed here with the label attached.
- 41 connections minus 35 peers leaves 6 more connections than listed peers in the DRFortress exchange record retrieved on 20 November 2026. The record prints no rule for counting a connection against a peer, so I adopt none (ARITH-1).
- 22 open-policy peers divided by 35 peers is 62.9 per cent. That says nothing about traffic, price or which peers actually exchange packets (ARITH-2).
- HIX’s port at the DRFortress exchange prints as 10G in the PeeringDB record and as 1G in the 2026 contacts sheet — a factor of ten as printed. That is a comparison of two documents, not a measurement of either port (ARITH-3).
Four further printings do not reconcile, and none of them is adjudicated here. The contract requirement is stated twice incompatibly: “Contract Requirement Not Required” on the AS19035 record against a Join page that requires a signed HIX agreement before connection. The FAQ describes DRFxchange as accepting 10/100/1000 Mbps Ethernet while the 2026 contacts sheet lists participants at 1G, 10G and 100G — an undated legacy sentence set beside a current sheet, with no conversion attempted (HIX FAQs). The registry lists one connected network for HIX while HIX’s own pages describe a wider government, education and research membership; a registry row set is not a member roll and no member total is asserted. And the word “free” appears twice on HIX’s pages — free membership, no charge to establish peering — and never once as a statement about the cost of reaching either peering point.
What a participant actually decides
Strip the argument to the transaction. A network in Hawai‘i that wants local peering has three options and only two of them are free.
Terminate at Mānoa: Ethernet into the UH ITS data centre, no HIX charge, and the university’s eligibility rule decides whether you may be there at all. Terminate at DRFortress: you buy a cross-connect and colocation from the landlord, your session with HIX runs over DRFxchange, and the total you pay is a number that appears in no document either party publishes. Or don’t peer locally.
That is the whole control surface. The exchange decides who may appear on the fabric and which routes may be announced. The landlord decides who may stand in the room and what it costs to stand there. Both can be reasonable; neither of them is free, and only one of them is even priced privately in a document a stranger can check.
Boundaries
- Reading modes first: the HIX pages were retrieved as page text on 20 November 2026, some through a direct fetch and some through an exact-URL search extract; the 2009 technical specification and the 2026 contacts sheet were obtained only as text extracts for their exact PDF URLs, never as page-image reads, so sections of either may be missing from what I saw.
- The specification read is version 3.6 dated 21 April 2009 and states in its own text that it may be superseded in whole or in part. No later technical specification was obtained. The must-go-through-DRF-IX rule, the split address administration and the Tier-1 exclusion are therefore reported as the 2009 text, and current practice at that facility is unverified.
- No HIX agreement, order form, port price or fee schedule was obtained for either exchange. “HIX does not charge to establish a peering” is a sentence on the Join page, not a tariff; the total cost a participant bears at DRFortress is unknown to me and no figure for it appears anywhere in the material read.
- DRFortress publishes no port price, cross-connect price or colocation price in anything I read; “low-cost” is its own marketing adjective, quoted as the publisher’s word and never as a measured price.
- PeeringDB is a self-reported directory. The DRFortress exchange record was last updated 22 January 2020 and the HIX exchange record 2 February 2023, so peer counts, capacities and prefixes may be stale; no BGP session, looking glass, IRR database or RPKI repository was queried, and the route-server addresses are printed as unqueried registry rows.
- HIX’s port at the DRFortress exchange is printed at 10G by PeeringDB and at 1G by the 2026 contacts sheet. Both printings are in the body and neither is adopted, because I cannot tell which document describes the port in service.
- The contract requirement is printed twice and incompatibly: “Contract Requirement Not Required” on the AS19035 record against a Join page that requires a signed HIX agreement before connection. Reported, not reconciled.
- The HIX exchange record lists exactly one connected network, University of Hawaii AS6360, while HIX’s own pages describe a wider government, education and research membership. A registry row set is not a member roll; no HIX member count or participant total is asserted anywhere in this article.
- The FAQ’s 10/100/1000 Mbps statement about DRFxchange is reported as an undated legacy sentence set beside the 1G, 10G and 100G participant rows of the 2026 contacts sheet, with no conversion between them.
- “Largest commercial internet exchange in the state of Hawaii” and “low-cost” are DRFortress’s own sentences about itself. Neither was independently measured and neither is repeated as fact.
- The FCC document is an acceptance-for-filing public notice of proposed transfers of control, not a final grant, and it describes a transaction as proposed. Nothing about the state of that transaction today is asserted.
- The 2013 un-commercialisation account, the 2008 change to Ethernet-only access at Mānoa and the intent to keep local traffic local are HIX’s own narrative sentences. No board minute, resolution or contemporaneous filing was obtained.
- No Hawaiki or other submarine cable capacity figure, landing count or bandwidth comparison enters this article. The cable appears only because a federal notice names DR Fortress a licensee on it and the operator of the Oahu landing station.
- No claim is made that any price is unfair, that any participant was refused, that DRFortress favours any network, that UH ITS restricts access for any reason other than its printed eligibility rules, or about the conduct of any officer of the University of Hawai‘i, DRFortress, 1547 or Harrison Street.
- Documents located but not read, and therefore not used: any HIX BGP-community policy document, any DRFortress multilateral peering agreement text, any colocation agreement, any Hawaii broadband office filing, and the submarine-cable station pages that were not part of this retrieval.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






