Publisher Auto-Reconnect enables a Publisher to reconnect to another eligible Point of Presence (PoP) when the Global Server Load Balancing (GSLB) service identifies a sufficient latency improvement. Reconnection can briefly interrupt connectivity.
Administrators control tenant enablement in the Netskope UI where the setting is available, and configure individual Publisher Active Windows in the Publisher Wizard.
Enable or disable auto-reconnect
On tenants that provide the Enable Publisher Auto-reconnect control, configure the setting directly in Publisher Global Attributes:
- Go to Settings → Security Cloud Platform → Traffic Steering → Publishers.
- Open Publisher Global Attributes.
- Select Enable Publisher Auto-reconnect.
- Click Save.
The global setting applies to all Publishers across the tenant. To disable it, clear Enable Publisher Auto-reconnect and click Save. If the control is unavailable, contact Netskope Support for tenant enablement assistance.
Check the tenant setting rather than assuming auto-reconnect is enabled after a software upgrade. An individual Publisher’s local enablement and Active Windows also affect whether it reconnects.
Configure Active Windows
Use Auto-reconnect settings in the Publisher Wizard to control when an individual Publisher may reconnect. Open Configure auto-reconnect settings and enter one or more daily time ranges using the 24-hour clock. Separate multiple ranges with commas.
- Default: 00:00-23:59 (all day).
- Off-hours example: 00:00-06:00,20:00-23:59.
Active Windows use the Publisher’s local time. Outside those windows, auto-reconnect conditions are evaluated, but reconnection is not performed. Inside a window, a reconnect may occur when GSLB’s conditions are met. The Publisher Wizard also allows auto-reconnect to be disabled for that Publisher.
Request threshold tuning
For latency-based switching between PoPs within the same tier, the documented default criteria require both a 50% relative RTT improvement and a 50 ms absolute RTT improvement. Tenant-specific settings may differ. These values are centrally managed and are not configurable in Publisher Global Attributes or the Publisher Wizard.
For example, a change from 150 ms to 60 ms provides a 60% relative improvement and a 90 ms absolute improvement, satisfying both default latency criteria. A lower-latency alternative alone does not guarantee reconnection; eligibility, policy and Active Windows also apply.
Contact Netskope Support to request a review of the reconnection thresholds. Include:
- Tenant ID and affected Publisher names or identifiers, software versions and locations.
- Incident timestamps with timezone, current PoP, alternative PoPs and observed RTT measurements.
- Business impact, whether reconnects occur too frequently or fail to occur, and the desired outcome.
- Publisher log bundles covering the incident and the configured Active Windows.
Netskope Support can coordinate a review with the GSLB / Platform Engineering team. Changes are evaluated for the tenant’s network conditions and reconnection stability.