Polymarket gains institutional co‑location

Polymarket’s own documentation now makes explicit something traders had been discussing in social posts for months: the venue offers direct co-location in Amazon Web Services’ eu-west-2 region for users that complete KYC or KYB checks. That places the prediction-market operator closer to the playbook used in other electronic markets, where firms pay for physical proximity to matching systems to cut execution time. Polymarket says eu-west-2 is the location of its primary servers and that direct co-location there provides the “lowest possible latency” to the venue. ### Where is the exchange actually sitting? Polymarket’s API documentation identifies eu-west-2 as the venue’s “Primary Servers” region and names eu-west-1 as the closest non-restricted alternative. Amazon identifies eu-west-2 as its London region in AWS’s regional infrastructure documentation. That matters because distance becomes part of execution. If a trader’s strategy depends on reacting first to a price change, the path between the trading system and the venue becomes a competitive variable, not just a hosting choice. (docs.polymarket.com) Polymarket does not spell out performance figures in the documentation, but it does state that direct co-location is available for the “lowest possible latency.” ### What does “co-location” mean on Polymarket? (docs.polymarket.com) Polymarket describes its market as a central limit order book with off-chain order matching and on-chain settlement on Polygon. In practice, that means the race for queue position happens before settlement, at the point where signed orders reach the operator’s matching infrastructure. The documentation says users who complete KYC or KYB can “co-locate directly in eu-west-2.” In traditional market structure terms, that is the important line: it means the venue is offering a path for firms to run trading systems in the same cloud region as the matching stack rather than sending orders from farther away. (docs.polymarket.com) ### Why are firms like Jump and Susquehanna being linked to this? CoinDesk reported in February, citing Bloomberg, that Jump Trading was set to take stakes in Polymarket and Kalshi tied to the liquidity it provides. (docs.polymarket.com) That does not by itself prove a co-location arrangement, but it does show Jump’s direct commercial involvement in prediction-market market making. Susquehanna has also been building out prediction-market activity. (docs.polymarket.com) Susquehanna’s own predictions business says it provides block-size liquidity and works with exchanges, brokerages and institutional participants, while separate March reporting linked Susquehanna Crypto and BitGo to institutional access for prediction markets. Social posts have named Jump Trading and Susquehanna as firms pursuing direct low-latency access on Polymarket. Reuters-style verification is limited here: Polymarket’s public docs confirm co-location exists, but I could not independently verify from primary public records that either firm has taken eu-west-2 co-location at Polymarket specifically. (coindesk.com) The institutional interest is supported; the named co-location participants remain unconfirmed in public documentation. (sig.com) ### Why does this matter for how the market trades? Polymarket’s structure makes speed relevant because orders are matched off-chain on a central limit order book. In that setup, the trader that sees a change first, recalculates first and submits first can win queue priority, spreads or inventory adjustments by fractions of a second. The shift is less about retail users suddenly disappearing than about the venue publishing infrastructure terms that accommodate professional trading firms. (docs.polymarket.com) Once a market offers direct co-location, other questions follow: who qualifies, whether access is standardized, what monitoring exists for fair access, and how the venue documents outages or performance differences across connectivity options. Polymarket’s public materials already answer one piece of that by tying the lowest-latency path to completed KYC or KYB. (docs.polymarket.com) ### What can traders verify for themselves right now? Polymarket’s documentation is the cleanest primary source. The geoblock page states that direct co-location is available in eu-west-2, and the trading overview confirms the venue operates a CLOB with off-chain matching and Polygon settlement. AWS’s own region documentation confirms eu-west-2 is London. The next public proof points will likely come from participant disclosures, hiring posts, or changes to Polymarket’s institutional and API documentation. (docs.polymarket.com) For now, the verifiable fact is narrower but still significant: Polymarket publicly offers direct co-location in its primary AWS region, and that puts prediction-market execution on infrastructure terms familiar to high-speed trading firms.