WHAT NEW IN X10.31 SAT

X 上的 AI 合集档案 · 22 个合集 · 61,986 条

museIMAGE

738 次实测:Muse 流量走哪些云厂商

有人搭测试站跑 738 次实验,统计 Muse 代理流量的 IP 来源,发现需要浏览器导航时 100% 走 Fastly,API/curl 场景则全走 Cloudflare。

Odd Diligence
@OddDiligence2026.09.24收录原推发布于 2026.09.24
738 次实测:Muse 流量走哪些云厂商
Odd Diligence @OddDiligence原推发布于 2026.09.24
在 X 上打开原推

Interesting $FSLY finding from testing Meta Muse. Through a series of hundreds of tests, it appears that the $FSLY role with Meta Muse is greater than analysts have noted Over the past week, I created several test websites and ran 738 controlled tests to send traffic from Muse agents to my websites I set up analytics on my website, and I was able to track things like IP address, user agent, operating system, etc From the IP addresses, across the 738 tests, Muse sent traffic from: -Cloudflare: 37.0% -Fastly: 29.3% -Meta: 19.4% -AWS: 14.4% Cloudflare is not a surprise – as there has been a lot of analyst commentary about Muse using Cloudflare. Fastly, on the other hand, was a surprising result I ran many different situations and tasks to try to understand why, or when, Muse sends traffic through Fastly – or others. And when I looked deeper, Muse used Fastly for 100% of the tests when browser navigation was required (e.g., “go to my favorite restaurant’s website and find me the menu”). And when Muse was requested to navigate on a website (e.g., make me a doctor appointment), Fastly was used in 100% of tests Then in other situations, for example when an API is involved or a curl request required, Cloudflare was used in 100% of tests Lastly, when requesting Muse to search the web, Muse split traffic through Fastly, Cloudflare, Meta directly, and AWS

x.com/odddiligence/status/2102810323233423720采集于 2026.09.24 10:12