Rhythms outbound IP ranges for allowlisting

When Rhythms connects to one of your systems — Jira, a database, an on-premises API, an MCP server — the connection originates from Rhythms. If that system restricts inbound traffic by IP address, add the ranges below to its allowlist.

These are outbound ranges only. They are the addresses Rhythms connects from. Nothing here opens inbound access to your Rhythms workspace.

The ranges

Both ranges are required.

Do you need IP ranges, a domain allowlist, or both?

These are separate controls, and the one you need depends on what the other system inspects.

• Domain allowlist — permits requests to a hostname: https://app.rhythms.ai/**.

• IP allowlist — permits connections from an address: the ranges above.

In the vast majority of cases, allowlisting https://app.rhythms.ai/** is sufficient on its own. Add the IP ranges when your information security policy requires restrictions on source IP, or when the system filtering the traffic cannot match on hostname.

The two controls are independent. Allowing the domain does not imply the IP ranges are allowed, and vice versa.

If these ranges ever change

The ranges above are static. We do not rotate them.

If we ever need to change them, we will:

• notify affected workspace administrators at least 30 days in advance, and

• run the old and new ranges in parallel through the transition, so there is no window where a correct allowlist stops working.