Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The November 11, 2026 announcement confirms traffic, error, latency, response-size and security views with server-side sorting by relevant metrics.
- The documentation provides detailed metrics for full-state operations over the last 24 hours or seven days. Align the window and operation identity before comparing.
- Workers or Waiting Room request paths can leave origin latency unpopulated. Missing data does not establish zero latency, a healthy service or a good browser experience.
- Editing operation identity changes its ID. Deleting a full-state operation stops metric tracking, and previous historical metrics cannot be restored.
What changed in the five views?
On November 11, 2026, Cloudflare announced traffic, error, latency, response-size and security views in Web Assets → Operations. Each view surfaces relevant metrics and supports server-side sorting, so teams with large inventories can prioritize operations around the problem they are investigating.
An operation is an API endpoint identified by its HTTP method, hostname pattern and path pattern. For example, GET and POST on the same path should not automatically be treated as the same investigation target. This is a conceptual example; no requests were executed.
In a Cloudflare account you are authorized to use, open Web Assets → Operations and check the target operation’s identity and state. The announcement does not provide a complete plan, pricing or country list for the five views, or an exact rollout time. Check actual account eligibility and permissions for access.
Choose a view around the question
The following is investigation advice. To understand impact, start with the traffic view and identify operations receiving substantial request volume. For failed requests, switch to the error view and distinguish 4xx, 5xx and their combined rate. High volume and a high error proportion answer different questions; read rankings alongside business importance.
Use the latency view for slow operations and the response-size view when investigating response-body changes. The documentation describes latency as average origin response time in milliseconds and response size as the average response size in bytes. Do not relabel an average as p99 or treat response bytes as a bill amount.
The security view can help investigate relevant signals, but opening it does not itself enable detection or blocking. Select a small set of operations for investigation and inspect their details before considering rule changes based on any single ranking.
Check the window and missing data first
Endpoint Management documents detailed metrics for full-state operations over the last 24 hours or seven days. Before comparing operations or observations, record the window, method, hostname and path. Request totals from 24-hour and seven-day windows do not represent the same observation period.
Some performance metrics cannot be measured accurately when a request is handled by Workers, or by a Workers-based product such as Waiting Room, in a way that prevents it from being passed directly to the origin. Cloudflare specifically says origin latency may remain unpopulated in the dashboard.
A blank latency value therefore does not mean 0 ms or establish that the origin is healthy. Check the services in the request path and whether the metric applies, then use your existing logs and monitoring to investigate. This origin metric also does not replace independent measurement of the browser’s page experience.
Preserve identity and history when managing the inventory
Cloudflare computes operation IDs from the HTTP method, hostname and path. Editing these identity fields produces a different ID. Record the original operation and reason for a correction rather than assuming records before and after the change form one continuous history merely because their display names look similar.
Deleting a full-state operation stops tracking its associated performance and analytics data. Its previous historical metrics cannot be restored. If the operation later returns to the full state, tracking restarts from that point. Deletion is not a routine way to clear an error rate or reset an observation window.
Record the current window, operation identity and problem description before deciding whether a management change is necessary. This is advice for preserving investigation context, not a new automatic save or recovery feature announced by Cloudflare. This article did not modify any Cloudflare account.
Choose the next step from the evidence
When an operation’s errors or average latency warrant attention, check its business purpose, request path and corresponding monitoring. For blank metrics, check collection limitations first. The views help identify investigation targets; they do not independently establish a root cause, a successful fix or site-wide performance.
Schema Profiles eligibility and Sensitive Data Detection requirements in the documentation apply to those respective features. Do not reuse them as one eligibility rule for all five metric views. Fees, regional scope and account rollout details absent from the announcement remain unknown; a visible control does not establish free access or availability to every account.
To move from observation into schema learning, read the existing guide: https://puppyip.com/en/resources/cloudflare-api-shield-manual-schema-learning-guide . This article did not perform account operations, generate test traffic or validate the reader’s environment.
Sources
Frequently Asked Questions
Do discovered operations automatically start profile learning?
No. Cloudflare says discovery only adds operations to the inventory. After checking operation identity, a user with the appropriate eligibility and permissions must select Learn profile for the intended operation. API Security customers already have Schema Profiles access; Enterprise customers without that entitlement need an invitation to the closed beta and can contact their account team. This is not a general eligibility rule for metric views.
Are sensitive-data labels available to every account?
The documentation requires the zone to have the Sensitive Data Detection managed ruleset enabled and makes the feature available to Enterprise customers on the Advanced application security plan. Once enabled, full-state operations whose responses matched that ruleset during the past week can receive the cf-risk-sensitive label. A label does not establish that a problem has been fixed or that every blocking rule is enabled.