Traffic statistic

This tool shows how much traffic protection processes and how it processes that traffic at different stages. The data is updated in real time.

Why use Traffic statistic?

You can see which countries requests come from, how protection processes them at each stage, how much traffic comes from people and bots, and how reliably your origin servers respond.

All data is shown in clear charts. You can enable auto-refresh to update a chart every 10 seconds.

Traffic statistic

Use the tool to assess:

  • Traffic volume: the Bandwidth metric shows the volume of traffic before and after filtering, as well as how much outbound data your servers send.

  • Traffic structure: open the Request classification and Request geography metrics to see which clients send requests most often (people or bots) and which countries they come from.

  • Protection performance: Request actions and CAPTCHA challenge statistics show how many requests protection blocks, passes, or checks with a challenge. Platform response codes and Request processing times show how quickly and correctly it processes requests.

  • Origin server health: monitor Origins response times, Origins response codes, and Origin 5xx errors to make sure your servers work without failures or delays.

How to use the tool

1. Open Traffic statistic

Go to Application protection → Resources. Next to the required resource, click …​ and select Traffic statistic.

2. Select the period for the statistics

Click Last 24 hours to open the Period menu. You can use one of the standard options (the last 5, 10, or 30 minutes; 1, 6, 12, or 24 hours; or 2, 7, 30, or 90 days) or specify a custom range.

Select a period

Click the refresh icon and select the data auto-refresh interval: off, 10 or 30 seconds, 1, 5, 15, or 30 minutes, or 1 hour.

Set auto-refresh

3. Select a metric

Click the required metric to display its charts.

Select a metric

Metric descriptions

Click a metric name to expand its description.

Request actions

The number of requests per minute or second that protection processes in different ways:

  • Passed—the request was passed to your origin server as legitimate traffic.

  • Blocked—the request was blocked because it violated security policies and was not sent to your origin server.

  • Redirected (301)—protection returned the HTTP 301 status code to the client, most often for an HTTP-to-HTTPS redirect.

  • Bad Request (400)—protection returned the HTTP 400 status code because of an invalid format or a protocol or policy violation.

  • JS Challenge—protection issued a JavaScript challenge to verify whether the client is legitimate.

  • Cookie Challenge—protection issued a cookie challenge to verify whether the client is legitimate.

  • CAPTCHA Challenge—protection issued a CAPTCHA to verify whether the client is legitimate.

CAPTCHA challenge statistics

This chart is on the same page as Request actions. It shows the number of requests per minute or second for which protection issued a CAPTCHA, grouped by action:

  • Issued—a CAPTCHA was issued.

  • Solved—a CAPTCHA was solved correctly.

  • Allowed—the request was passed to your origin server because the user solved a CAPTCHA correctly recently. Protection identified the user by their cookie.

Bandwidth

The volume of different types of traffic in bits per second:

  • Inbound—all inbound traffic received by protection.

  • Passed—traffic that passed protection checks and was sent to your servers.

  • Outbound—outbound traffic sent from your servers back to clients.

Request classification

The number of requests per minute or second from different client types:

  • Human—a request from a person.

  • Verified Bot—a request from an officially verified bot that performs a useful task on the internet, such as a search engine crawler (Googlebot) or monitoring service (UptimeRobot).

  • Bot—a request from a bot.

  • Likely Bot—a request most likely sent by a bot, although protection is not completely certain.

  • Likely Human—a request most likely sent by a person, although protection is not completely certain.

  • Whitelisted—a request from a client on the white list.

  • Blacklisted—a request from a client on the black list.

Origins response times

The time from when protection passes a client request to the origin server until it receives the origin response.

The chart shows the number of requests per minute or second grouped by origin response time:

  • < 0.3 sec.

  • 0.3–1 sec.

  • 1–3 sec.

  • 3–10 sec.

  • > 10 sec.

Origins response codes

The number of requests per minute or second for which your origin server returned a specific HTTP response code:

  • 2xx Success—2xx codes, successful requests.

  • 3xx Redirects—3xx codes, redirects.

  • 4xx Client Errors—4xx codes, client-side errors.

  • 5xx Server Errors—5xx codes, server-side errors.

Platform response codes

The number of requests per minute or second for which protection returned a specific HTTP response code:

  • 2xx Success—2xx codes, successful requests.

  • 3xx Redirects—3xx codes, redirects.

  • 4xx Client Errors—4xx codes, client-side errors.

  • 5xx Server Errors—5xx codes, errors on the protection side.

Request processing times

The time from when protection receives a client request until it sends a response.

The chart shows the number of requests per minute or second grouped by processing time:

  • < 0.3 sec.

  • 0.3–1 sec.

  • 1–3 sec.

  • 3–10 sec.

  • > 10 sec.

Origin 5xx errors

The number of requests per minute or second for which your origin server returned a 5xx error, grouped by response code:

  • 500 Internal Server Error—an unexpected error on the server.

  • 502 Bad Gateway—the server returned a response in an invalid format or with invalid data.

  • 503 Service Unavailable—the server is temporarily unavailable, for example because of overload or maintenance.

  • 504 Gateway Timeout—the server did not receive a response from one of its internal services in time.

Request geography

Countries that send the most requests. The table shows each country’s share of all requests. For example:

Request geography table