Skip to content

SYSTEM Cited by 1 source

Cloudflare AI Gateway User Insights

Cloudflare AI Gateway User Insights is an AI Gateway analytics feature that turns already-proxied AI traffic into a behavioral view for each identified account. It learns a per-account session-cost baseline, ranks sessions that depart from that history, and presents a review queue to an administrator. The feature is monitoring-oriented: it does not infer intent or automatically block an account. (Source: sources/2026-08-05-cloudflare-catching-rogue-ai-behavior-with-identity-aware-analytics)

Detection model

For each account, User Insights evaluates sessions rather than isolated requests:

  1. Build a rolling personal baseline from the p95 session cost over the last 30 days.
  2. Treat a session above 2× that p95 as a relative anomaly candidate.
  3. Require the candidate to also exceed the organisation's account-level p99 session-cost floor.
  4. Apply a dollar floor so a very large percentage increase on a tiny spend value does not alert.
  5. Put qualifying accounts in an administrator-facing rogue-behavior feed.

The two thresholds deliberately separate unusual behavior from material spend. A high-cost user whose sessions are normal for them should not alert merely because they are expensive; a low-spend agent whose cost grows by 10× should not disappear inside an organisation-wide dollar threshold.

Identity dependency

The strongest per-user view depends on Cloudflare Access protecting a custom AI Gateway domain. Access authenticates the caller through a SAML-supported identity provider and AI Gateway attaches the verified Access user ID as cf.user_id request metadata. Without that mapping, User Insights can still observe account IDs, but cannot turn the anomalous entity into a person or agent an administrator can readily investigate.

Scope and controls

User Insights tracks cost signals and highlights associated inefficiency hints such as low cache-hit rate or oversized context windows. It does not itself decide whether use is malicious, whether a credential is compromised, or whether a request should be stopped. Separate AI Gateway spend controls can block additional requests or route to a lower-cost model after a per-user limit is reached.

Caveats

The source does not disclose session-boundary rules, sampling or retention policy, minimum history needed for a baseline, cross-tenant aggregation boundaries, detector precision/recall, alert latency, or how frequently the rolling statistics are recomputed. Its $200 account-p99 example is Cloudflare internal traffic, not a documented default.

Seen in

Last updated · 622 distilled / 1,953 read