# Warehouse Native Pulse results delayed for customers with IP allowlists configured

- Provider: [Statsig](https://down.guide/providers/statsig)
- Confidence: Confirmed
- Impact: Degraded
- lasted 0m
- started 2026-06-16 20:00 UTC
- id: DWN-b93c2e418c
- Official page: https://stspg.io/vdx16fb807rs

## Updates from Statsig
### 2026-06-16 20:00 UTC: resolved
A recent infra change spun up WHN compute with public IPs instead of routing through our published NAT ranges. Pulse traffic briefly left from an IP address which isn't in our published list. We've fixed routing; egress is back on the published IPs. No allowlist change needed.

From the builder: does your app depend on Statsig? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=statsig) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Statsig.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-b93c2e418c), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.