> For the complete documentation index, see [llms.txt](https://policies.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://policies.appfarm.io/service-and-usage/static-ip-for-web-requests-policy.md).
# Static IP for Web Requests Policy
This policy sets out the terms that apply when a customer procures the **Static IP for Web Requests** capability for one or more of its Solutions. To support Appfarm's documentation (see the [Product Glossary](https://policies.appfarm.io/glossary/product-glossary#static-ip-for-web-requests) and the [Appfarm documentation](https://docs.appfarm.io/library/action-nodes/web-request#use-static-ip)), this policy focuses on the operational terms of the capability and its impact on SLA commitments. By requesting and enabling Static IP for Web Requests, the Customer accepts the terms of this policy.
**How the capability is provided:** When Static IP for Web Requests is enabled, outbound web requests from the Solution originate from a fixed set of one or more public IP addresses assigned and communicated by Appfarm (the "Static IPs"). The Static IPs belong to the application cluster on which the Solution runs. This allows the Customer to restrict access to their systems to traffic originating from the Static IPs by allowlisting the Static IPs communicated by Appfarm.
**Inherent limitation accepted by the Customer:** Fixed IP addresses tie a Solution to specific infrastructure, and has one natural and unavoidable consequence: if the Solution is moved, outbound web requests may originate from other IP addresses until the Static IPs are restored or configurations are updated, and integrations that only accept traffic from the Static IPs will fail in that period. In practice, this means:
* **Relocation to protect availability:** Although all necessary efforts to avoid such situations will always be made, Appfarm may need to move Solutions to another application cluster where this is necessary to restore or protect the availability of the Service, for example, if a cluster degrades or fails. The Solution will normally be restored quickly, but its web requests will then originate from other IP addresses than the Static IPs. Integrations restricted to the Static IPs will be unavailable until Appfarm has restored the original Static IPs by reassigning them to the cluster now serving the Solution or by returning the Solution to its original cluster. Alternatively, if the above is not feasible, until the Customer and its third parties have allowlisted the new addresses provided by Appfarm. Appfarm will make commercially reasonable efforts to keep this period short.
* **Limited SLA exception:** Failures in third-party integrations caused by the Solution's web requests originating from other IP addresses than the Static IPs (following a relocation as described above, or a notified change) are a natural consequence of using fixed IP addresses. Such integration failures do not constitute downtime, a warranty incident, or a breach of the Service Level Agreement, and the Customer cannot claim compensation, refunds, or other remedies under the Service Level Agreement for them. For the avoidance of doubt, this is a limited exception: the Service Level Agreement otherwise remains in full force for the subscription, including its availability commitments and support service levels.
* **Changes to the Static IPs:** Appfarm reserves the right to change the Static IPs where necessary for operational, maintenance, security, or infrastructure lifecycle reasons. Planned changes will be notified to the Customer in writing at least three (3) weeks before the change takes effect. The Customer is responsible for updating firewall openings and integration configurations, including those managed by the Customer's third parties, within this notice period. Integration failures occurring after a notified change has taken effect, where configurations have not been updated, are covered by the limited SLA exception above.
**Customer responsibilities:** The Customer is responsible for allowlisting all Static IPs communicated by Appfarm, keeping firewall and integration configurations up to date, ensuring that notices from Appfarm reach the personnel (and any third parties) who manage the relevant configurations, and acting on such notices within the notice period.
Except for the limited SLA exception noted above, all other terms of the customer's subscription agreement and Appfarm's policies remain unchanged and in full effect. This policy does not alter any contract provisions or documentation beyond clarifying the consequences of enabling Static IP for Web Requests. The Subscription Form and the Additional Resources Agreement govern enabling, pricing, and termination of the capability itself.
## Revision history
| Date | Revision |
|---|
03.09.2026 | Document published. |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://policies.appfarm.io/service-and-usage/static-ip-for-web-requests-policy.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.