Fastest SEC Filings Websocket Alpha Day One Results

I released the Fastest Websocket on Monday 9/21/26. On Day 2 it detected 25% of filings on average 15s early. This should be the fastest by far of any commercially available websocket.

Table comparing fastest websocket to the normal websocket. Positive numbers mean faster. Note that some filings were detected slower.

Future improvements

I am disappointed at only detecting 25% of filings early. I was hoping for 50%. I am working on a better approach using machine learning. I aim to get 50%+ coverage soon.

Discrepancies in the SEC RSS feed.

Websocket runs on AWS. Fastest SEC Filings Websocket runs on GCP. Both poll the RSS to detect filings. This is the standard way by which most providers detect new filings (fastest sec filing's method is much more clever). However, sometimes the RSS feed on GCP detects filings ~2-7s faster than AWS, and vice versa.

Why might this be?

1. I made a mistake in my infrastructure, leading to wild variation in speed.
2. Something weird is going on with sec.gov

I believe it is (2). The table below shows the AWS RSS poller winning about 2/3rds of the time. This is suspicious, because the RSS poller is actually two pollers. So winning 2/3rds of the time implies to me that sec.gov is likely caching responses. I will test this, then likely implement cache busting to fix this.