Bot Insights — fleet movement brief

Bot & Edge Movement — www.example.com, week of 2026-04-07 → 2026-04-14

How bot traffic and edge health shifted vs the prior week.

Comparison window
2026-04-07 00:00 → 2026-04-14 00:00 UTC
vs 2026-03-31 00:00 → 2026-04-07 00:00 UTC
Executive summary

What this report says

Total requests up +20% week-over-week — ASN 64500 covers 87.2% of the increase.

3 metrics need attention.

Recommended action Investigate the volume mover.

3 Investigate 0 Watch 0 Stable 0 Insufficient data

3 metrics need attention (out of 3).

Shared signal

ASN 64500 covers 87.2% of the total requests move

Movement detail

Per-metric movement vs prior week

Metric Current Baseline Delta % change Verdict
Bot share 34 29 +5.5pp +19.0% Investigate
429 rate 2 0.90 +1.2pp +120.0% Investigate
Total requests 1.50M 1.25M +250.00K +20.0% Investigate
Attribution

Top movers — who drove the change

ASN 64500 covers 87.18% of the total requests move.

ASN Current Baseline Delta Covers
64500 420.00K 80.00K +340.00K 87.18%
64600 260.00K 210.00K +50.00K 12.82%
Recommended next steps

Investigations to queue from this report

  1. Break down request volume by ASN, host, and bot class for the affected window.
    Total requests
  2. Pull rate-limit policy for known good crawlers and check policy collateral.
    429 rate
  3. Compare crawler/AI populations vs. prior week; check policy surfaces.
    Bot share
Hosts in scope

Scorecard rollup

Per-host scoring detail lives in the scorecard brief. This rollup only cross-references which hosts the movement applies to.

Host Score Band Verdict
www.example.com 48 Medium review Close — expected
Method & caveats

What this report is and isn't

Rule-based scorecard for Www.example.com · , built from mechanical features only, compared against week over week. It reports what was measured, not why. Missing feature inputs are reported as such — they are not scored as safe.

Schema, source table, and constraints
Schema
bot_posture_movement.v1
Comparison
Week over week
Tenant / database
Www.example.com ·
Table
bi_summary_day
Constraints
Movement only; No causal claim; LLM may summarize structured evidence only
Orientation — what this report measures
What this measures

Fleet-wide edge metrics (request volume, bot-like share, cache miss rate, error rate, 429 rate) compared with the prior equivalent window.

How to read the score

Movement is reported as percent change and percentage-point change. Confidence is qualitative based on volume and coverage.

  • escalate · 0–40
  • monitor · 40–70
  • observe · 70–100
What this can't say

Not a root-cause diagnosis. Volume changes do not imply attack or intent without additional evidence.