Static Egress IPs

Every outbound connection from Requesty’s production infrastructure leaves through a fixed set of public IP addresses. Add them to your allowlist when a resource Requesty connects to only accepts known sources, for example:

MCP servers that the MCP Gateway calls on your behalf
Webhook endpoints that receive spending alerts or sample requests
Provider accounts used with Bring Your Own Keys that restrict access by network, such as an Azure OpenAI resource with network rules

These addresses cover traffic from Requesty to you. To restrict which addresses can send requests to Requesty with your API keys, use Allowed IPs on the Compliance page.

IP Addresses

Requesty runs in three AWS regions, with one address per availability zone. A connection can come from any of these addresses, so allowlist all nine.

Region	Location	IP addresses
`eu-central-1`	Frankfurt, Germany	`63.177.190.101` `18.159.89.51` `63.178.188.162`
`us-east-1`	N. Virginia, USA	`52.86.22.125` `54.236.210.165` `52.22.124.156`
`ap-southeast-1`	Singapore	`18.141.19.224` `18.140.181.208` `47.130.48.5`

The full list, ready to paste into a firewall rule:

177.190.101/32
159.89.51/32
178.188.162/32
86.22.125/32
236.210.165/32
22.124.156/32
141.19.224/32
140.181.208/32
130.48.5/32

Last modified on November 12, 2026

Getting Started

LLM Gateway

Model Capabilities

Analytics & Monitoring

Access Control

Organization

MCP Gateway

IP Addresses

​IP Addresses

IP Addresses