Skip to main content
  • EN

Howdy!

I'd like a breakdown of how publishers make the best determination for traffic that is routed through them. I understand that you need a publisher CLOSET to the source of what you're trying to connect to (destination) however, there isn't anything that prevents me from adding ALL my publishrs to a private app. 
If I do this though, what happens exactly during the publisher selection? how does the traffic decide what the most efficient route is? What is the logic behind this routing? 

Also if there’s a “publisher” doc that I just haven't found that someone has, I’ll accept that as well :) 

 

thanks! 

 

When the Latency-based Publisher Selection feature is enabled, NPA will choose the Publisher closest to the user from the configured pool of Publishers, based on latency.


When not enabled: When a set of Publishers are defined within a Private App, connections are load balanced across the different Publishers.


Publisher Selection - Netskope Knowledge Portal

When the Latency-based Publisher Selection feature is enabled, NPA will choose the Publisher closest to the user from the configured pool of Publishers, based on latency.


When not enabled: When a set of Publishers are defined within a Private App, connections are load balanced across the different Publishers.


Publisher Selection - Netskope Knowledge Portal

 

When you say “load balanced across the different publishers” does that mean, theoretically, if I apply ALL of my publishers for a private app, it could possibly choose an inefficient publisher?

For ex: Say I have 6 publishers, all geographically spread across the US, and the destination of the private app is on the West coast, but I selected ALL publishers for this private app, load balancing could end up choosing the East coast publisher instead? 

Hope this makes sense. 

Reply


Terms & ConditionsCookie settings