Benchmark
Polygon MEV Endpoint Benchmarks
A reproducible method for measuring Polygon endpoint latency, errors, throttling, fees, and submission outcomes from your operating region.
Data sourced from the FRB Ecosystem Research hub and cross-validated against live block data.
Linkable summary
What this benchmark covers
Use identical requests and pinned test conditions across providers. This page supplies the template, not universal provider rankings or FRB production results.
Track live numbers on the FRB metrics dashboard or read the Polygon MEV ecosystem page for strategy context.
Download raw data from the Polygon metrics export for use in your own models.
Strategy & tools checklist
Before diving into the numbers, confirm you have the right reference points.
Strategy guides
- Polygon MEV ecosystem page — chain-specific routing and timing.
- MEV Strategies Guide — full playbook for sandwich, backrun, and arb.
- MEV 101 — fundamentals of MEV for new operators.
Live tools
- WSS Latency Test — test your current endpoint live.
- Gas Calculator — model gas cost before committing.
- Network Status — check for known Polygon incidents.
How we measure
Your measurement run should record the following fields for every submitted request or bundle:
- Latency: time from WSS submission to first block builder acknowledgment (p95, 30-day rolling).
- Success rate: percentage of bundles that landed in the target block or within one block of it.
- Gas / tx: actual on-chain gas cost of executed bundles, not simulation estimates.
What do these numbers mean?
Latency and errors vary by region, provider tier, transport, request mix, and network load. Compare p50 and p95 using the same sample and time window.
Gas is a direct cost. Compare confirmed transactions after priority fees, failed attempts, refunds, and the same conversion source.
Limitations & methodology notes
- Latency values are from FRB-operated nodes. Run the WSS Latency Test.
- Success rates vary with congestion. State the exact test dates, p50/p95, errors, and sample size.
- Provider tiers change. Always verify current rate limits and regional availability before committing.
Provider behavior changes. Rerun the test before operational or purchasing decisions.
Video
Latency recovery playbook
See how FRB operators diagnose and resolve high-latency events on Polygon in under 15 minutes.
Median inclusion
FRB nodes with relay rotation
Avg latency
Record region and endpoint
Gas / tx
With private bundle preference
How FRB collects this data
For a reproducible local run, record:
- Submission timestamp and block height target.
- Builder acknowledgment latency.
- Inclusion block vs. target block (filled, late, or missed).
Keep the raw local export with the report; no public aggregate performance dataset is asserted here.
How to apply these benchmarks
- Set latency SLOs using the P95 column — not the mean — since tail latency determines worst-case fills.
- Route primary traffic through QuickNode Edge or Alchemy Turbo; keep a secondary on Ankr for APAC coverage.
- Alert if your observed P95 rises 20% above the baseline here — that usually signals a regional incident.
Use these KPIs in your reports
Analysts and ops teams can cite this page directly. The JSON export includes all fields needed for:
- Internal P&L attribution (per-provider latency vs. inclusion profit).
- Investor reporting (median inclusion and gas benchmarks).
- Audit trails (bundle hash, timestamp, inclusion block).
Next steps
Ready to improve your Polygon MEV performance?
- Docs quickstart — connect FRB to your Polygon RPC in under 10 minutes.
- Pricing — compare tiers and relay quotas.
- Support — get help from the FRB ops team.
- Knowledge Base — runbooks, FAQs, and advanced configuration.
Endpoint leaderboard
| Provider | Latency | Success | Notes |
|---|---|---|---|
| QuickNode | Measure p50/p95 | Record success | Test from your region and record plan, quotas, transport, and window. |
| Alchemy | Measure p50/p95 | Record success | Use the same request mix, sample size, region, and time window. |
| Polygon public RPC | Measure p50/p95 | Record success | Record throttling, errors, and endpoint changes during the run. |
| Ankr | Measure p50/p95 | Record success | Run the same test from each target operating region. |
Ops notes for your team
Copy these checkpoints into your runbook when onboarding a new Polygon route:
- Verify WSS endpoint is in the same region as your primary FRB node.
- Set a latency alert at P95 + 20 ms as the rotation trigger.
- Log every relay rotation with reason, timestamp, and observed latency before and after.
Run a local measurement
Use the WSS latency test, then retain your own raw output for analysis and review.
Open latency testFrequently asked questions
Why is Polygon latency so important?
Latency affects how much time remains for simulation and submission. Measure p50 and p95 from your region because endpoint and network conditions vary.
Do I need special RPC keys?
We recommend premium endpoints (Alchemy Turbo, QuickNode Edge) but FRB works with public RPCs and rotates when rate limits kick in.
Can I reuse these KPIs in investor decks?
Only reuse results measured in your own environment, with the method, date, sample size, raw logs, and limitations attached.
Explore the Polygon MEV ecosystem page, compare bots on the MEV bot comparison, or install FRB and connect your Polygon RPC today.
Download the agent from the download page, then review the MEV 101 hub and MEV Strategies Guide to hit the ground running.