Support

Locations and network connectivity

North America locations

Overview

The following table provides an overview of the various connectivity options supported by Databento and their recommended use cases.

Connectivity option Services Best for Ports Latency (90th)
Internet Live, Historical Lowest cost 0.5+ ms
Dedicated: Interconnect with AWS, Google Cloud or Microsoft Azure Live, Historical Mission-critical, cloud-based applications requiring high uptime or consuming entire feed(s) 1G 1.7+ ms
Dedicated: Interconnect at proximity hosting location Live, Historical Mission-critical, self-hosted applications requiring high uptime or consuming entire feed(s) 1G 0.5+ ms
Dedicated: Cross-connect with any colocation or managed services provider (MSP) Live Applications requiring lowest latency 10G, 25G 42.4 μs
Dedicated: Colocation with Databento Live Applications requiring lowest latency 10G, 25G 42.4 μs
Peering Live, Historical Colocation, hosting and extranet providers, MSPs 10G, 25G 0.5+ ms

Connecting via internet

By default, our client libraries will connect to our gateways over internet, using our public DNS hostnames.

Databento's services are designed to be efficient when consumed over internet. We use a mix of compression and normalization techniques to minimize bandwidth requirements of our data services, so that you can even consume full venue feeds—which would typically require a 10+ gigabit cross-connect—over a regular internet connection.

Hosting your application in close geographical proximity to our gateways is the first step you can take towards ensuring a fast and stable connection. To help you make that determination, here are the locations of our gateways as well as hostnames that you can run a ping or traceroute against:

Service Nearest metro Data center Address Public DNS hostname
Historical (BO1) Boston CoreSite BO1 70 Inner Belt Rd, Somerville, MA hist.databento.com
Live (DC3) Chicago CyrusOne Aurora I 2905 Diehl Rd, Aurora, IL 60502 dc3.databento.com
Live (NY4) New York Equinix NY4 755 Secaucus Rd, Secaucus, NJ 07094 ny4.databento.com

There is no strong guarantee that the shortest route between your application and our gateways will be taken even if they're situated in the same data center. To address this issue and achieve stable routes across the internet, Databento relies on blended bandwidth and private peering agreements which are summarized in the table below. If minimizing network variance is important for your use case, we recommend using any of these providers.

Service Data center Transit providers and private peers
Historical (BO1) CoreSite BO1 Lumen, NTT, Telia, Cogent, Verizon, Google, Microsoft, Akamai
Live (DC3) CyrusOne Aurora I Lumen, Zayo
Live (NY4) Equinix NY4 Lumen, Hurricane Electric

If your security policies only allow traffic from designated IPs, ensure that you can route to the entire range of Databento's public IP addresses, from 209.127.152.0 to 209.127.159.255 (or 209.127.152.0/21 in CIDR notation). We are allocated exclusive ownership and usage of these public IPs by ARIN.

You should also allow the following UDP and TCP port ranges used by our services through your access lists and firewalls. The destination ports are port numbers that Databento's servers listen on.

Protocol Destination ports
NTP 123
HTTPS (historical) 443
FTP 21, 61000-61004
UDP 13000-13050
TCP (live) 13000-13050

Connecting via dedicated connectivity

See our dedicated connectivity guide for more details.

Connecting via peering

Databento supports private peering over BGP at CyrusOne Aurora and the Equinix NY2/4/5/6 facilities for our live data, and at Markley One Summer Street for historical data. Our BGP ASN is AS400138 and more info can be found on our PeeringDB profile. We do not support public peering at an IX at this time. Contact support to set up private peering with Databento.