19 days ago
Hi team,
My service (ups-voice-agent in project splendid-energy) makes outbound POST/GET requests to apis.ups.com (UPS's official API) for OAuth token + tracking lookups. Every request returns a raw HTML 403 Forbidden page (not a JSON error from UPS), which suggests the block is happening at a network/firewall layer rather than from UPS's application itself.
Outbound IP: 152.55.176.174
Target: https://apis.ups.com/security/v1/oauth/token
Credentials are confirmed correct and approved on UPS's side (UPS API support reviewed my account and confirmed everything is properly configured/approved)
The same request works fine when... actually it doesn't work from my local network either, so I can't 100% confirm this is Railway-specific, but UPS support suggested checking with my hosting provider in case Railway's shared IP range is blocked by UPS's firewall.
Could you confirm whether Railway IPs have any known issues reaching UPS's API endpoints, or whether a static/dedicated outbound IP is available on my plan?
Thanks!
1 Replies
19 days ago
Static outbound IPs are a Pro plan feature, not available on Hobby. On your current Hobby plan, outbound traffic uses shared IPs that can change between deploys. If UPS's WAF is blocking requests based on IP reputation, upgrading to Pro and enabling static outbound IPs for your service would give you a consistent set of IPs you could share with UPS for allowlisting. That said, since you mentioned the same request also fails from your local network, the issue may not be IP-related at all and could be on UPS's side or in the request itself.
Status changed to Awaiting User Response Railway • 19 days ago
Status changed to Solved deezniks • 18 days ago