Window: last 7 days · dataset fibr_axp_page_hits · auto-refresh every 5 min
Bot hits
7,625
↓ 17.2% vs prior 7d
Stripped
2
↑ 100% · 0.0% share
Origin bot-miss
760
↓ 5.9% · 10.0% fell through
Unique paths
1,909
↑ 2.4% distinct URLs
Unique bots
15
↓ 16.7% UA matches
Avg latency
397 ms
↑ 10.1% worker wall-clock
Max latency
164,862 ms
↑ 1499% 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 7d 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: 115/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
760
448 ms
98 ms
10,618 ms
stripped
2
388 ms
347 ms
429 ms
stripped-edited
6,863
391 ms
34 ms
164,862 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/*
1,831
0
0
0.0%
/blog/*
952
1
146
0.1%
/
853
0
0
0.0%
/glossary/*
608
1
168
0.2%
/landing-page/*
570
0
12
0.0%
/tools/*
494
0
6
0.0%
/conversion-rate-optimization/*
460
0
31
0.0%
/ab-testing/*
451
0
44
0.0%
/geo/*
269
0
3
0.0%
/pricing/*
73
0
0
0.0%
/whitepaper/*
72
0
39
0.0%
/about-us/*
64
0
0
0.0%
/pilot/*
61
0
4
0.0%
/customer-stories/*
51
0
19
0.0%
/croagency/*
45
0
3
0.0%
/seed-funding/*
41
0
0
0.0%
/guides/*
36
0
8
0.0%
/privacy-policy/*
31
0
0
0.0%
/partnership-program/*
25
0
25
0.0%
/terms-and-conditions/*
24
0
0
0.0%
By country
Code
Country
Hits
US
United States
5,458
SG
Singapore
365
PL
Poland
248
AU
Australia
236
CH
Switzerland
133
IN
India
131
BR
Brazil
129
NZ
New Zealand
111
DE
Germany
104
GB
United Kingdom
98
CN
China
93
ES
Spain
91
JP
Japan
89
ID
Indonesia
71
KR
South Korea
57
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
ChatGPT-User
Microsoft Corporation
match
2,123
Amazonbot
Amazon Technologies Inc.
match
1,297
Amazonbot
Amazon Data Services Northern Virginia
match
1,260
Meta-ExternalAgent
Meta Platforms Ireland Limited
match
475
ChatGPT-User
Microsoft Limited
match
446
ClaudeBot
Anthropic, PBC
match
389
Bytespider
Amazon Data Services Singapore
spoof?
359
OAI-SearchBot
Microsoft Limited
match
275
PerplexityBot
Amazon Technologies Inc.
match
178
ChatGPT-User
Microsoft do Brasil Imp. e Com. Software e Video G
match
108
Amazonbot
Amazon.com, Inc.
match
105
Bytespider
China Unicom Hebei province network
spoof?
72
Claude-User
Google LLC
match
35
Perplexity-User
Amazon Technologies Inc.
match
33
GPTBot
Microsoft Limited
match
25
OAI-SearchBot
Microsoft Corporation
match
24
Bytespider
CHINANET hebei province network
spoof?
21
Claude-User
So-net Service
spoof?
17
OAI-SearchBot
Infraly, LLC
spoof?
17
ChatGPT-User
Microsoft Corp
match
14
ChatGPT-User
Microsoft Deutschland MCIO GmbH
match
13
ClaudeBot
Infraly, LLC
spoof?
12
CCBot
Infraly, LLC
spoof?
10
GPTBot
Infraly, LLC
spoof?
9
Google-CloudVertexBot
BuyVM
spoof?
9
PerplexityBot
Infraly, LLC
spoof?
9
ChatGPT-User
SIA Singularity Telecom
spoof?
8
Amazonbot
BuyVM
spoof?
8
xAI
Infraly, LLC
spoof?
8
Google-CloudVertexBot
Infraly, LLC
spoof?
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/24,30356.4%
HTTP/1.13,32043.5%
HTTP/320.0%
TLS version
TLSv1.37,47299.2%
TLSv1.2600.8%
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
Microsoft Corporation
2,153
3
Amazon Technologies Inc.
1,508
3
Amazon Data Services Northern Virginia
1,260
1
Microsoft Limited
749
4
Meta Platforms Ireland Limited
475
1
Anthropic, PBC
389
1
Amazon Data Services Singapore
359
1
Microsoft do Brasil Imp. e Com. Software e Video G
108
1
Amazon.com, Inc.
105
1
Infraly, LLC
80
8
China Unicom Hebei province network
72
1
BuyVM
44
7
Google LLC
36
2
CHINANET hebei province network
21
1
Hostodo
21
7
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.