nantevo→Status
Last checked
Platform components
Component Status Latency Uptime (30d)

Reverse proxy / authentication

Credential validation layer — all nodes

Operational
<1ms
100.0%

DNS resolver — SFO (San Francisco)

West Coast · IPv4 + IPv6

Operational
9.6ms avg
99.98%

DNS resolver — CHI (Chicago)

Midwest · IPv4 + IPv6

Operational
14.1ms avg
99.97%

DNS resolver — DFW (Dallas)

South Central · IPv4 + IPv6

Operational
18.3ms avg
99.96%

DNS resolver — ATL (Atlanta)

Southeast · IPv4 + IPv6

Operational
21.8ms avg
99.97%

Telemetry pipeline

Per-client log ingestion and dashboard

Operational
—
99.89%

RoCi intelligence pipeline

Async threat analysis and rule propagation

Operational
—
99.94%

Dashboard & client portal

Web interface and API endpoints

Operational
—
99.95%
Performance — trailing 90 days
15.52ms
Fleet average query response time
PRODUCTION TELEMETRY · trailing 90 days
99.97%
Resolver availability — all nodes combined
TRAILING 90 DAYS
~25%
Queries blocked — threat, ad, and tracker filtering
FLEET AVERAGE · PRODUCTION
Zero
User-reported service interruptions beyond known CDN events
SINCE OCTOBER 2023
90-day uptime history
Operational Degraded Outage
Resolver availability 99.97%
90 days agoToday
Authentication layer 100.0%
90 days agoToday
RoCi intelligence pipeline 99.94%
90 days agoToday
Telemetry pipeline 99.89%
90 days agoToday
Resolver nodes — current
West Coast · US
San Francisco
avg response9.6ms
IPv4active
IPv6active
uptime 30d99.98%
Operational
Midwest · US
Chicago
avg response14.1ms
IPv4active
IPv6active
uptime 30d99.97%
Operational
South Central · US
Dallas
avg response18.3ms
IPv4active
IPv6active
uptime 30d99.96%
Operational
Southeast · US
Atlanta
avg response21.8ms
IPv4active
IPv6active
uptime 30d99.97%
Operational
Incident history — last 90 days
2026-02-14
06:12–11:47 UTC
Cloudflare global CDN degradation — partial resolver impact
A major Cloudflare global outage caused degraded performance and intermittent resolution failures for cloud-hosted Nantevo endpoints during the incident window. On-premise deployments were unaffected. Service restored automatically when Cloudflare infrastructure recovered. No Nantevo infrastructure failure — this was an upstream CDN dependency event. Motivates the architectural case for on-premise deployment independence.
External

No other incidents in the last 90 days

All user-reported events in this period were related to the Cloudflare CDN dependency noted above.

The Cloudflare dependency is a known characteristic of the current cloud infrastructure and is documented transparently on the How It Works and Enterprise pages. On-premise appliance deployment eliminates this dependency entirely. Multi-CDN redundancy is on the infrastructure roadmap.

Maintenance window policy

Scheduled maintenance is performed using TTL-aware DNS rotation. A node is removed from DNS at least one full TTL period before its maintenance window begins — ensuring no client resolver holds a cached record pointing to the node under maintenance. Maintenance is staggered across nodes so at least three of four nodes remain active at all times. Subscribers receive advance notice of planned maintenance windows.