Window: last 30 days · dataset fibr_axp_page_hits · auto-refresh every 5 min
Bot hits
25,328
↑ 4.1% vs prior 30d
Stripped
7,874
↑ 112386% · 31.1% share
Origin bot-miss
6,859
↑ 21.7% · 27.1% fell through
Unique paths
2,525
↓ 23.2% distinct URLs
Unique bots
20
↓ 16.7% UA matches
Avg latency
376 ms
↓ 5.3% worker wall-clock
Max latency
10,664 ms
↓ 26.7% 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 30d 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: 352/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
6,859
389 ms
38 ms
10,664 ms
stripped
7,874
344 ms
100 ms
7,939 ms
stripped-edited
10,595
391 ms
36 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/*
6,453
3,989
75
61.8%
/guides/*
3,090
36
2,963
1.2%
/blog/*
2,474
553
273
22.4%
/glossary/*
2,397
1,203
462
50.2%
/
1,746
0
0
0.0%
/conversion-rate-optimization/*
882
467
42
52.9%
/ab-testing/*
699
306
81
43.8%
/landing-page/*
641
282
16
44.0%
/tools/*
626
268
76
42.8%
/customer-stories/*
577
155
215
26.9%
/geo/*
314
81
0
25.8%
/pricing/*
307
0
0
0.0%
/api/*
303
0
303
0.0%
/@fs/*
234
0
234
0.0%
/croagency/*
217
74
52
34.1%
/pilot/*
192
17
0
8.9%
/whitepaper/*
165
33
35
20.0%
/seed-funding/*
153
0
0
0.0%
/about-us/*
141
0
0
0.0%
/.ssh/*
127
0
127
0.0%
By country
Code
Country
Hits
US
United States
20,938
SG
Singapore
1,902
IN
India
276
CN
China
272
BE
Belgium
171
JP
Japan
171
DE
Germany
141
NL
Netherlands
134
AU
Australia
134
MY
Malaysia
119
TW
Taiwan
96
NZ
New Zealand
84
DK
Denmark
79
PL
Poland
75
BR
Brazil
74
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
4,917
Amazonbot
Amazon Technologies Inc.
match
3,770
Amazonbot
Amazon Data Services Northern Virginia
match
3,539
ClaudeBot
Anthropic, PBC
match
2,989
Bytespider
Amazon Data Services Singapore
spoof?
1,794
ChatGPT-User
Microsoft Limited
match
1,176
PerplexityBot
Amazon Technologies Inc.
match
1,128
OAI-SearchBot
Microsoft Limited
match
682
CCBot
Amazon Data Services Northern Virginia
match
522
Claude-User
Google LLC
match
514
Amazonbot
Amazon.com, Inc.
match
363
ChatGPT-User
Microsoft Corporation
match
313
GPTBot
Microsoft Limited
match
192
ClaudeBot
Google LLC
match
164
Grok
Google LLC
spoof?
156
PerplexityBot
Google LLC
spoof?
132
GPTBot
Google LLC
spoof?
118
Amazonbot
Google LLC
spoof?
113
Bytespider
Beijing Zhonglianlixin Technology Co., Ltd.
spoof?
109
ChatGPT-User
Google LLC
spoof?
105
YouBot
You.com
spoof?
102
OAI-SearchBot
Google LLC
spoof?
85
Bytespider
China Unicom Hebei province network
spoof?
83
Bytespider
CHINANET hebei province network
spoof?
78
Bytespider
Google LLC
spoof?
78
Google-Extended
Google LLC
match
74
Meta-ExternalAgent
Google LLC
spoof?
74
OAI-AdsBot
Microsoft Limited
match
69
OAI-AdsBot
Microsoft Corporation
match
69
OAI-SearchBot
Microsoft Deutschland MCIO GmbH
match
66
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/214,27456.4%
HTTP/1.111,03443.6%
HTTP/3200.1%
TLS version
TLSv1.325,291100.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
Amazon Technologies Inc.
4,921
12
Meta Platforms Ireland Limited
4,917
1
Amazon Data Services Northern Virginia
4,066
7
Anthropic, PBC
2,989
1
Microsoft Limited
2,144
5
Google LLC
1,881
17
Amazon Data Services Singapore
1,794
1
Microsoft Corporation
496
6
Amazon.com, Inc.
392
14
Infraly, LLC
175
8
Limestone Networks, Inc.
119
8
Beijing Zhonglianlixin Technology Co., Ltd.
109
1
You.com
102
1
China Unicom Hebei province network
83
1
CHINANET hebei province network
78
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.