> For the complete documentation index, see [llms.txt](https://node1.gitbook.io/node1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node1.gitbook.io/node1-docs/robinhood/robinhood-landing/robinhood-landing-benchmark.md).

# Landing Benchmark

On September 14, 2026, **Node1 won 66% of on-chain races from Frankfurt and 61% from Ohio**, with 100 rounds per location.

| Submission path                                  | Frankfurt origin | Ohio origin |
| ------------------------------------------------ | ---------------: | ----------: |
| Node1 Ohio 2B                                    |              38% |         43% |
| Node1 Ohio 2C                                    |              28% |         18% |
| **Node1 combined — two endpoints**               |          **66%** |     **61%** |
| **Direct Robinhood sequencer — three endpoints** |          **34%** |     **39%** |

Each location used one host to simultaneously submit five distinct pre-signed zero-value self-transfers per round, sharing sender, nonce and gas settings. Connections were prewarmed, senders used busy-polling, and each round waited for the previous nonce’s inclusion.

Successful on-chain transaction hashes determined winners, not HTTP response times. All 100 rounds per location were included. Maximum application-level send-start skew was **18.889 µs in Frankfurt** and **0.700 µs in Ohio**.

These were separate test sessions. Node1 may fan out internally, and same-nonce admission rules can affect outcomes. Results are race win rates, not latency measurements or guarantees across regions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://node1.gitbook.io/node1-docs/robinhood/robinhood-landing/robinhood-landing-benchmark.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.