Edge analytics from the SwiftPress CDN (explained)
What Total Requests, cache rate, bandwidth, WAF events, traffic charts, and request logs mean in your CDN analytics.
SwiftPress serves your site through our CDN at the edge. Edge analytics show what reached the edge in a chosen period—requests, caching, bandwidth, and security (WAF)—so you can see traffic patterns and how much work was done at the edge vs your origin.
Analytics are usually scoped to a hostname (for example staging.yoursite.com or your live domain) and a time range (such as Last 24 hours). Exact screen labels in my.swiftpress.io may vary slightly as we improve the UI.
What you’re looking at
Data is collected as requests hit the edge (our CDN / WAF layer in front of WordPress). It is not a full replacement for server-only logs or Google Analytics, but it’s excellent for delivery, cache health, and blocked threats.
Summary metrics (top of the page)
These numbers summarise the selected site + timeframe.
| Metric | What it means |
|---|---|
| Total requests | How many HTTP(S) requests the edge handled (every page, image, script, API call, feed, etc. counts as one or more requests). |
| Cache rate | Share of responses that were served from edge cache (a hit) vs needing to fetch or revalidate from origin. Higher usually means faster responses and less load on your server—when content is cacheable. |
| Bandwidth | Approximate data transferred from the edge to visitors (and related). Useful for spotting spikes or heavy assets. |
| WAF events | Count of security events the Web Application Firewall logged for the period—often blocked or challenged requests matching rules (bots, probes, bad patterns). |
If everything is 0 or 0% for a busy site, check time range, hostname, or staging vs production—or allow time for data to populate after DNS changes.
Traffic over time (chart)
The chart helps you see trends instead of only totals.
Typical series you can toggle or overlay (names may vary):
- Requests — Volume of traffic over time.
- WAF blocks (or similar) — When security rules stopped bad traffic—spikes can mean attacks or aggressive scans.
- Cache rate — How “cache-friendly” traffic was over time (drops may mean more logged-in users, query strings, or uncacheable pages).
- Bandwidth — Data volume over time.
Use this to correlate marketing sends or spikes with requests, bandwidth, and security events.
Filters: method / status / timeframe
You may see filters such as:
- Method — e.g. GET, POST (most page views are GET; POST often forms, admin actions, REST).
- Status — HTTP response codes (200 OK, 301/302 redirects, 404 not found, 5xx errors).
Narrowing helps debug a specific issue (e.g. only 404s or only POSTs).
If you see “No traffic data available” / “No data for the selected timeframe”, the edge didn’t record matching events— widen the time range, confirm the correct domain, or check that traffic is routed through SwiftPress (DNS / CDN).
All requests (recent request log)
This table lists individual requests seen at the edge—useful for debugging URLs, bots, and response codes.
Common columns:
| Column | Meaning |
|---|---|
| Time | When the edge handled the request (timezone may follow your account or UTC—check the UI). |
| Method | Usually GET for normal page and asset loads. |
| URI | Path and query (e.g. /, /wp-content/..., /?feed=rss2). RSS feeds (feed=rss2, feed=comments-rss2) appear as normal GET requests. |
| Status | HTTP status returned by the edge/origin (e.g. 200 success). |
| IP | Client IP as seen by the edge (may be a visitor, bot, or feed reader). |
| Actions | Shortcuts to inspect or dig deeper (implementation depends on product version). |
You’ll often see pagination (e.g. “1–10 of 100 requests”)—the edge stores a sample or window of recent requests, not always an infinite archive.
Tip: Many GET requests to / or feeds with small IP ranges are normal RSS aggregators or monitors—not necessarily “users” in the marketing sense.
WAF events (security)
This section lists recent security-related events at the edge—typically blocked or flagged requests matching WAF rules.
Typical columns:
| Column | Meaning |
|---|---|
| Time | When the event occurred. |
| IP | Source address involved. |
| Path | Request path that triggered the rule. |
| Rule | Which rule or signature matched (helps support tune false positives). |
| Country | Geo signal for the IP (best-effort). |
| Actions | View details or follow-up tools if offered. |
“No data” here means no WAF events in the window—often good (nothing blocked). If you expect attacks during an incident, broaden the timeframe or confirm WAF is enabled for that hostname.
Why edge analytics are useful
- Cache rate — Tells you if your site is CDN-friendly; drops may mean cookies, query strings, or dynamic pages.
- Bandwidth — Spots heavy pages or traffic spikes.
- WAF — Visibility into blocked bad traffic without reading raw server logs.
- Request log — Quick URI + status debugging without SSH.
Run through these screens periodically when you change themes, plugins, or DNS—so you can confirm traffic still flows through SwiftPress and caching behaves as expected.
Need help?
Use — same as the Support link in the site footer (opens the chat widget). You can also sign in at my.swiftpress.io. We don’t offer email support — see How to contact customer support. If something in this article doesn’t match your dashboard, and we’ll point you to the right screen.