Static IPs for ServiceNow Integrations

Restrict your ServiceNow instance by source IP and only allowlisted addresses can reach it, including your REST API integrations.

An integration on a cloud platform has a rotating egress IP, so ServiceNow rejects it even when the credentials are valid.

QuotaGuard gives you two fixed IPs you add to ServiceNow's IP Access Control once, so your integration keeps connecting no matter how its platform changes underneath.

Diagram showing Bloomberg data entering a shield with a lock, symbolizing secure integration.

Enterprise Connectivity & Allowlisting

ServiceNow lets administrators restrict access by source IP, through IP Address Access Control across the instance and through REST API Access Policies scoped to specific APIs.

Both apply to non-interactive REST integration accounts, not just human logins, so a server-side integration must come from an allowlisted IP.

An app on a cloud platform egresses from a rotating address, which the allowlist rejects. QuotaGuard gives that integration two static IPs that belong to your account, so you allowlist two addresses and never touch the list again.

Note: QuotaGuard is for connecting cloud integrations to IP-restricted enterprise resources like the ServiceNow REST API, partner APIs, SQL databases, and gateways. It is not for scraping consumer sites that block cloud infrastructure.

Fixed Outbound IP for the ServiceNow Allowlist

QuotaGuard provides a permanent, static outbound IP for your integration, so an IP-restricted ServiceNow instance always recognizes its traffic.

Redeploy on every push, scale up or down, move hosts, and the address ServiceNow sees stays the same. You add two IPs to ServiceNow once and your integration keeps working.

Two Static IPs to Allowlist

QuotaGuard gives you two fixed IPs in a load-balanced pair. Add both to ServiceNow's allowed set so your integration stays connected even if one node is in maintenance.

The addresses never change, so an allowlist entry written today is still valid next year.

Static Inbound IP for ServiceNow Callbacks

The reverse direction is covered too.

If you configure ServiceNow outbound REST messages or Flow actions to call your application, QuotaGuard gives you a static inbound entry point that ServiceNow can reach at one permanent address, which you allowlist on your side. Your hosting platform can rotate underneath without breaking the callback.

Diagram showing data flow from your integration with rotating IPs to QuotaGuard Static, then to Bloomberg Enterprise Console.
Diagram showing data flow from your integration with rotating IPs to QuotaGuard Static, then to Bloomberg Enterprise Console.
Diagram showing data flow from your integration with rotating IPs to QuotaGuard Static, then to Bloomberg Enterprise Console.

Native Configuration

QuotaGuard works at the application layer through environment variables.

No change to ServiceNow, no custom infrastructure. Point your ServiceNow REST API calls through the proxy and they exit from your two static IPs.

Environment Variable Setup

Store your QuotaGuard connection string as an environment variable on your integration's host.

Set the standard proxy variables so your HTTP client routes through it automatically, or attach the proxy to the specific calls that reach ServiceNow so nothing else is affected.

Clients in Python, Node.js, Go, and others respect the proxy variables without code changes.

Works With the Table API, OAuth, and Basic Auth

ServiceNow's REST Table API authenticates with OAuth 2.0 or Basic Auth.

The proxy carries the token request and the API calls alike, so every request that touches ServiceNow exits from your two static IPs. Nothing about the authentication flow changes.

Works on Any Integration Host

The setup is the same whether your integration runs on Heroku, AWS Lambda, a container platform, a serverless function, or your own server.

The proxy variables are read by your HTTP client, so there is nothing host-specific to configure and nothing that breaks when your platform changes its egress addresses.

Flowchart showing SSO Host and Data Host integration through QuotaGuard Static for Bloomberg access.

Reliability for Production Integrations

ITSM workflows run on a schedule and in bursts.

QuotaGuard handles that without becoming the bottleneck, and gives your integration a fixed network identity ServiceNow can trust on every request.

High-Availability IP Pair

Every QuotaGuard account gets two static IPs in a load-balanced pair with automatic failover. Both are active at the same time.

Add both to ServiceNow's allowed set so your integration stays connected even if one node needs maintenance.

Shared or Dedicated IPs to Match Your Security Model

On Starter, Production, and Business plans your two IPs are static and stable, but shared with other QuotaGuard customers.

If your security model requires that only your integration can reach a given endpoint, Enterprise gives you dedicated IPs and dedicated proxy resources reserved for your account.

EU Data Residency

QuotaGuard runs proxies in 11 AWS regions across the US, Canada, EU, Asia-Pacific, and South America.

Choose the region closest to your application to minimize latency, or an EU region to keep outbound traffic on an EU-based IP. Enterprise plans add dedicated regional IPs.

Map of Europe highlighting EU Region, Dedicated EU IPs, and Data Residency Add-on features with metadata note.
Map of Europe highlighting EU Region, Dedicated EU IPs, and Data Residency Add-on features with metadata note.
Map of Europe highlighting EU Region, Dedicated EU IPs, and Data Residency Add-on features with metadata note.

FAQs

Technical Configuration and Setup for ServiceNow Integrations

Does ServiceNow let you restrict access by IP?

Yes.

Administrators can restrict instance access by source IP through IP Address Access Control, and restrict API access specifically through REST API Access Policies.

Both apply to REST integration accounts, so a server-side integration must connect from an allowlisted IP.

How do I give my integration a static IP for ServiceNow with QuotaGuard?

Route your ServiceNow REST API calls through QuotaGuard by setting the proxy connection string as an environment variable on your integration's host.

Then add your two QuotaGuard IPs to the instance's IP Access Control or the relevant REST API Access Policy.

Every request to ServiceNow then arrives from one of those two fixed addresses.

How do I verify my integration is using the static IP?

From the integration host, after configuring the proxy, make a request to <code>https://ip.quotaguard.com</code>.

The response returns the IP your request came from, which should match one of the two static IPs in your dashboard.

Check a few times and you will see both IPs in rotation.

Does this work for the Table API and OAuth?

Yes.

The proxy carries both the OAuth token request and the Table API calls, so every request that reaches ServiceNow exits from your two static IPs, with the authentication flow unchanged.

Will this keep working when my hosting platform changes its IPs?

Yes. The static IPs are assigned to your QuotaGuard account, not to your hosting platform.

Your integration reads the proxy URL from its environment and connects through the same two IPs regardless of how the platform rotates its egress addresses.

Is QuotaGuard appropriate for regulated data on ServiceNow?

Use QuotaGuard Shield for that.

Shield uses SSL passthrough and never decrypts your traffic at the proxy, which is the model for HIPAA, PCI-DSS, and SOC 2 workloads.

QuotaGuard Static tunnels outbound HTTPS without decrypting the payload and is appropriate for standard ITSM integration traffic, but not for regulated data.

Still have questions?

We don’t outsource Support to non-Engineers.

Reach out directly to the Engineers who built Shield to discuss your specific architecture, integration challenges, or compliance constraints here 👇

Contact

🚀 Ready to Get Started? Choose Your QuotaGuard Path

QuotaGuard STATIC

Why: You need a rock-solid, fixed IP for general API access, AI workflows, or standard third-party integrations.
Best For: Developers, startups, and general application connectivity.
Key Feature: SOCKS5 support for secure database access.
Sign Up for QG Static for ServiceNow

QuotaGuard SHIELD

Why: You handle HIPAA, PCI, or sensitive PII data and require End-to-End Encryption (E2EE) for full compliance.
Best For: Regulated industries, financial services, and healthcare.
Key Feature: SSL Passthrough and key isolation.
Sign Up for QG Shield for ServiceNow

Trusted by Engineering Teams Everywhere

Reliability Engineered for the Modern Cloud

For over a decade, QuotaGuard has provided reliable, high-performance static IP and proxy solutions for cloud environments like Heroku, Kubernetes, and AWS.

Get the fixed identity and security your application needs today.

Start Free TrialTalk to an Engineer