Window: last 3 days · dataset fibr_axp_page_hits · auto-refresh every 5 min
Bot hits
3,113
↓ 19.5% vs prior 3d
Stripped
1,217
↓ 28.5% · 39.1% share
Origin bot-miss
1,177
↓ 3.0% · 37.8% fell through
Unique paths
1,237
↓ 10.4% distinct URLs
Unique bots
15
↓ 6.3% UA matches
Avg latency
357 ms
↑ 10.8% worker wall-clock
Max latency
10,664 ms
↑ 256% worst-case
Daily volume stripped vs origin-bot-miss
Each bar = one UTC day. Green = served from stripped/. Orange = bot-miss (path we don't have stripped, fell through to Framer).
Daily volume by class live vs search-index vs training
Live (blue) = real-time agents fetching while a user asks an AI a question. Search-index (purple) = crawlers building a search index that AI assistants then query at chat time (Perplexity, Claude-SearchBot, etc.). Training (orange) = offline crawlers indexing for model training. Watching live + search-index trend up means humans-via-AI are finding our content.
Daily coverage % share of bot requests served from stripped/
Higher = more bot traffic served the fast, clean stripped HTML. As more pages get stripped over time, this should trend up.
Hourly heatmap day-of-week × hour, UTC
Each cell = one hour of one weekday over the 3d window. Darker = more bot hits at that time. Reveals when crawlers are most active so you can plan deploys around quiet windows. Buckets are UTC and don't follow the timezone toggle — shifting them would silently misalign the grid.
lessmorepeak: 141/hr
Latency by served variant stripped vs origin pass-through
Worker wall-clock time. Stripped = bot got pre-stripped HTML from the Assets binding. Origin-bot-miss = bot fell through to Framer (extra TLS + network round-trip). The gap is the latency benefit the strip pipeline gives bots.
Variant
Hits
Avg
Min
Max
origin-bot-miss
1,177
412 ms
51 ms
10,664 ms
stripped
1,217
315 ms
119 ms
1,417 ms
stripped-edited
719
340 ms
44 ms
6,417 ms
Status code breakdown HTTP responses we returned to bots
Healthy = mostly 2xx. Spikes in 4xx/5xx mean bots are seeing errors — investigate before they de-rank us.
Coverage by path family which sections of the site have gaps
First URL segment groups paths into families (/faq/*, /blog/*, etc.). Compare stripped vs miss to see where the strip pipeline has the worst coverage.
Family
Total
Stripped
Bot-miss
Coverage
/faq/*
687
661
0
96.2%
/guides/*
666
6
648
0.9%
/blog/*
248
73
12
29.4%
/glossary/*
197
150
47
76.1%
/
159
0
0
0.0%
/ab-testing/*
98
65
16
66.3%
/conversion-rate-optimization/*
84
64
2
76.2%
/api/*
75
0
75
0.0%
/customer-stories/*
66
19
18
28.8%
/tools/*
60
40
6
66.7%
/landing-page/*
52
33
2
63.5%
/@fs/*
37
0
37
0.0%
/userfiles/*
34
0
34
0.0%
/pricing/*
33
0
0
0.0%
/geo/*
28
13
0
46.4%
/pilot/*
22
1
0
4.5%
/seed-funding/*
21
0
0
0.0%
/croagency/*
18
13
2
72.2%
/.ssh/*
17
0
17
0.0%
/about-us/*
17
0
0
0.0%
By country
Code
Country
Hits
US
United States
2,575
SG
Singapore
126
DE
Germany
47
TW
Taiwan
43
IN
India
41
BE
Belgium
34
BR
Brazil
29
CA
Canada
29
NL
Netherlands
27
CN
China
23
DK
Denmark
20
GB
United Kingdom
19
PL
Poland
19
JP
Japan
17
CH
Switzerland
9
Bot vs AS-org identity verification
Match = bot UA arrives from a network the vendor is known to use. Spoof? = UA + AS-org don't line up; likely UA fake. Unknown = no expected list yet for this bot.
Bot
AS organisation
Verdict
Hits
Meta-ExternalAgent
Meta Platforms Ireland Limited
match
909
ClaudeBot
Anthropic, PBC
match
360
Amazonbot
Amazon Data Services Northern Virginia
match
350
Amazonbot
Amazon Technologies Inc.
match
330
ChatGPT-User
Microsoft Limited
match
137
PerplexityBot
Amazon Technologies Inc.
match
125
Bytespider
Amazon Data Services Singapore
spoof?
119
CCBot
Amazon Data Services Northern Virginia
match
98
OAI-SearchBot
Microsoft Limited
match
79
Claude-User
Google LLC
match
67
ClaudeBot
Google LLC
match
50
ChatGPT-User
Microsoft Corporation
match
49
PerplexityBot
Google LLC
spoof?
34
Amazonbot
Amazon.com, Inc.
match
34
Grok
Google LLC
spoof?
33
DuckAssistBot
Google LLC
spoof?
21
OAI-SearchBot
Google LLC
spoof?
19
Amazonbot
Google LLC
spoof?
18
Bytespider
Google LLC
spoof?
16
CCBot
Google LLC
spoof?
16
GPTBot
Google LLC
spoof?
15
ChatGPT-User
Google LLC
spoof?
14
Grok
Cloudflare London, LLC
spoof?
13
Meta-ExternalAgent
Google LLC
spoof?
13
Bytespider
Beijing Zhonglianlixin Technology Co., Ltd.
spoof?
12
Google-Extended
Google LLC
match
12
GPTBot
Microsoft Limited
match
12
YouBot
Google LLC
spoof?
11
MistralAI-User
Google LLC
match
10
OAI-SearchBot
Microsoft Deutschland MCIO GmbH
match
8
HTTP / TLS mix spoof signal
A bot UA pretending to be a major vendor over an unusual HTTP/TLS combo (e.g. claiming to be GPTBot but speaking HTTP/1.1 + TLS 1.2 when real OpenAI uses HTTP/2 + TLS 1.3) is a likely spoof. Watch the long tail, not the dominant bar.
HTTP protocol
HTTP/22,08667.0%
HTTP/1.11,02432.9%
HTTP/330.1%
TLS version
TLSv1.33,109100.0%
AS-org leaderboard top networks fetching us, regardless of UA
Independent of bot name — useful for spotting volume from networks that don't claim a bot UA, or cross-checking against the Bot vs AS-org table above.
AS organisation
Hits
Distinct bots
Meta Platforms Ireland Limited
909
1
Amazon Technologies Inc.
455
2
Amazon Data Services Northern Virginia
448
2
Anthropic, PBC
360
1
Google LLC
349
15
Microsoft Limited
229
4
Amazon Data Services Singapore
119
1
Microsoft Corporation
54
2
Amazon.com, Inc.
34
1
Cloudflare London, LLC
21
2
Beijing Zhonglianlixin Technology Co., Ltd.
12
1
Microsoft Deutschland MCIO GmbH
9
2
Reliance Jio Infocomm Limited
9
2
You.com
8
1
China Unicom Hebei province network
7
1
Live tail last 50 bot hits in the past 6h
Period-independent — same on 7D / 14D / 30D. AE write delay is ~30–90s, so "live" actually lags real-time by about a minute. Useful for incident triage and spotting bot spikes.