---
title: IP addresses
description: The two fixed addresses per region Dashies connects from for SQL Server, Oracle Database, and PostgreSQL added as only accepting known addresses.
updated: 2026-09-22
---

Dashies connects to a SQL Server or Oracle Database, and to a PostgreSQL database you added as
only accepting known addresses, only from the two addresses listed below for the region your
workspace runs in: one IPv4 and one IPv6. Other data sources do not yet, and "Which data sources
connect from these addresses" on this page says which. Your workspace's
region, with the same two addresses, is shown in Settings, on your workspace's **General** page,
in the **Region** card.

We announce any change to this list here at least 30 days before it takes effect.

## Addresses by region

| Region | Code | IPv4 | IPv6 |
|---|---|---|---|
| Frankfurt | `fra` | `209.71.109.49` | `2a09:8280:e612:1:0:179:aaa3:0` |
| Toronto | `yyz` | `209.71.100.209` | `2a09:8280:e637:1:0:181:371a:0` |

Allow both addresses for your region. A rule that names only the IPv4 address fails when
Dashies reaches your database over IPv6. If your firewall accepts IPv4 rules only, the IPv4
address is the one that applies.

These addresses are shared by every Dashies workspace in that region, so a rule that admits
them admits Dashies rather than one workspace. The read-only login you create for Dashies is
still what protects your data.

## Which data sources connect from these addresses

| Data source | Connects only from these addresses | What to allow |
|---|---|---|
| [SQL Server](/guides/connect-warehouse/sqlserver) | Yes: the connection test, reading your schema, checking a query, and every refresh. | Both addresses, on port 1433. |
| [Oracle Database](/guides/connect-warehouse/oracle) | Yes: the connection check, reading your schema, checking a query, and every refresh. | Both addresses, on your listener port. On Autonomous Database, add them to the access control list, the IPv4 address at least. |
| [PostgreSQL](/guides/connect-warehouse/postgres) | Yes, when you add it as only accepting known addresses: the connection test, reading your schema, checking a query, and every refresh. A PostgreSQL data source added without that setting connects from other addresses. | Both addresses, on your database's port. Tick "This database only accepts connections from known IP addresses" when you add the data source, and the form shows them. |
| [Snowflake](/guides/connect-warehouse/snowflake), [BigQuery](/guides/connect-warehouse/bigquery), [Databricks](/guides/connect-warehouse/databricks) | Not yet. Adding the data source and building a dashboard connect from other addresses. | Not available yet. |
| [Redshift](/guides/connect-warehouse/redshift) | Not applicable. Dashies calls the Redshift Data API rather than your cluster's endpoint. | Nothing. |

If you need a Snowflake, BigQuery or Databricks database that only accepts known addresses,
contact support.

## Before Dashies connects

Every connection to a SQL Server or Oracle Database, or to a PostgreSQL database added as only
accepting known addresses, checks, before it dials, that it is leaving from your region's
addresses. If it cannot confirm that, it stops without connecting and the
run is reported as a Dashies fault rather than a refusal by your firewall.