Header image

Symfony Finland
Random things on PHP, Symfony and web development

Sample Traffic Reports from CloudFlare Dashboard

I wrote an article on using CloudFlare to manage traffic peaks. A commenter on Reddit wished for some statistics. I cannot retrospectively get any response comparison times or anything that would be a truly meaningful benchmark.

CloudFlare does offer a comprehensive reporting on their dashboard on the bits they have served in the last 24 hours. Here are sample report graphs along with the explanations.

Requests Through CloudFlare

Sample Cloudflare statistics: Requests Through CloudFlare

Requests: Compares the total number of requests served from CloudFlare's cache and requests served from your origin server.

Bandwidth used

Sample Cloudflare statistics: Bandwidth used

Bandwidth: Bandwidth Saved by CloudFlare.

Unique Visitors

Sample Cloudflare statistics: Unique Visitors

Unique Visitors: The number of unique IP addresses that visited your website.

Threats

Sample Cloudflare statistics: Threats

Total Threats Stopped: Threats blocked by CloudFlare's network intelligence and your settings.

Performance

Sample Cloudflare statistics: Performance
Fewer Servers Needed

The Fewer Servers Needed percentage is a rough estimate of how much less capacity you need in order to handle your website’s traffic because you’re using CloudFlare. This number is based on the requests and bandwidth saved by CloudFlare.

Bandwidth Saved

CloudFlare saves you bandwidth by serving cached versions of your content from our data centers. This means that only a small number of requests actually go back to your origin server. The more content served by our edge servers, the more bandwidth you save.

Content Type Breakdown

This represents the breakdown by content type of all traffic flowing through CloudFlare for your site (including both cached and uncached responses).

Security

Sample Cloudflare statistics: Security
Total Threats Stopped

Total Threats Stopped measures the number of “suspicious” and “bad” requests that were aimed at your website. You can use the CloudFlare firewall to better protect your website.

Requests receive these labels by our IP Reputation Database as they enter CloudFlare’s network:

Legitimate: request pass directly to your website

Suspicious: request has been challenged with a CAPTCHA page or JavaScript challenge page

Bad: request has been blocked because our Browser Integrity Check, or because of user configured settings like WAF rules or IP range block

Traffic Served Over SSL

Total number of encrypted 'HTTPS' requests sent using SSL/TLS.

Note: In order to increase the amount of traffic served over HTTPS, create a Page Rule as follows: add a new rule with a URL Pattern (e.g., yourdomain.com/) and set Always Use HTTPS to On.

Types of Threats Mitigated

CloudFlare classifies each of the threats that it blocks or challenges.

  • Bad browser
  • Blocked hotlink
  • Human challenged
  • Browser challenge
  • Bad IP
  • Country block
  • IP block (user)
  • IP range block (/16)
  • IP range block (/24)
  • New CAPTCHA (user)
  • Captcha error
  • Bot Request

Top Threats, Request Origins and Search Engines

Sample Cloudflare statistics: Top Threats, Request Origins and Search Engines<
Top Threat Origins

The amount of malicious traffic to your website categorized by country of origin.

Note: CloudFlare uses a GeoIP database to map IP address to countries. “Unknown” means that there wasn't a record for in our geolocation database for an IP address.

Top Request Origins

CloudFlare uses IP addresses to identify where requests originate and map these requests by country.

Includes: real requests, crawlers, and threats

Top Search Engines

The amount of requests made by web crawlers:

Google, Bing, Baidu, MSN, Google, Facebook, Twitter, Yandex, LinkedIn, and Pingdom.


Written by Jani Tarvainen on Wednesday July 15, 2015
Permalink - Tags: web, cdn, cloudflare, performance

Leave a comment

comments powered by Disqus

« Will JavaScript take over the Enterprise? - Everlasting SEO principles that work, because the web is hypertext »