Event Forwarding Client IP address is in banned Country list | Community
Skip to main content
G
gluke
Level 1
July 21, 2026
Question

Event Forwarding Client IP address is in banned Country list

  • July 21, 2026
  • 3 replies
  • 46 views

Hi everyone,

I'm running into an issue with an Event Forwarding CAPI integration and was wondering if anyone has encountered something similar.

We're consistently receiving a 403 response from the destination endpoint. The response message indicates that the client IP address is in the banned country list.

What's puzzling is that the requests are being sent from our Event Forwarding setup, and the vendor has stated that they do not believe the issue is on their side.

A few questions for the group:

  • Have you seen a similar 403 error related to a banned-country or geo-restriction policy?
  • Is there a way to determine the actual source IP being used by the Event Forwarding request?
  • Could this be caused by proxying, cloud infrastructure, or regional routing that results in requests originating from an unexpected location?
  • Were there any configuration changes or allowlisting steps required to resolve it?

Any insights, troubleshooting tips, or similar experiences would be greatly appreciated.

Thanks in advance!

    3 replies

    G
    GaneshKalamadug
    Level 2
    July 21, 2026

    I raised Adobe support ticket exact same reason we are running into. We whitelisted these ip addresses on our APIGEE layer but still I was seeing 403 for new ip addresses.  https://teams.public.onecdn.static.microsoft/evergreen-assets/safelinks/2/atp-safelinks.html

    I still did not recieve any response from support team, I will keep you posted if I we solve this puzzle.

    D
    davidwarner
    Level 2
    July 22, 2026

    A 403 like this is often caused by the destination seeing a cloud or proxy IP that geolocates to a restricted country. Check the logs and ask the vendor which source IP they’re receiving, then verify its location. If it’s unexpected, you may need to allowlist the Event Forwarding IP range or adjust the vendor’s geo-blocking rules.

    K
    kalarav.vasavada
    Level 2
    July 29, 2026

    Adobe Event Forwarding runs on the AEP Edge Network, so outbound calls egress from Adobe's global edge Point of Presence  (PoP) not based on your IPs. The PoP used is chosen by the Edge closest to the incoming event, so your CAPI calls can appear to originate from any Adobe region (often EU/APAC), which is what's tripping the vendor's banned-country filter.

    Few steps which can help:

    1. Confirm the source : In the Event Forwarding rule, temporarily point the Send Data action at a request-inspection endpoint (e.g., webhook.site or requestbin) and read the x-forwarded-for / source IP. You will see Adobe Edge egress IPs, not yours.

    2. Get the IP ranges from Adobe : Adobe does not publish a static egress IP list for Edge, this you can get through ticket you have already created.

    3. Vendor allowlist : Send those ranges to the vendor to allowlist, overriding the geo-block. This is the standard resolution, the vendor does need to act, the geo-filter is theirs.

    4. Reduce region spread : If your datastream is multi-region, the Edge PoP is dynamic. You can't pin a region for Event Forwarding today, so allowlisting the full published range is the only reliable path.

    5. Interim workaround : Route the call through your own proxy/gateway (Apigee, Cloudflare Worker, AWS API Gateway) with a fixed egress IP in an allowed country, and point Event Forwarding at that proxy instead of the vendor directly.

    It is mostly not misconfiguration on your side it's Edge geo-egress behavior. Get Adobe's egress CIDR list via Support, have the vendor allowlist it, or front the vendor with your own fixed-IP proxy.

    Terms & ConditionsAccessibility statement

    Loading footer...