Benchmark
Polygon MEV Endpoint Benchmarks
Real-world latency, success rates, and inclusion figures from FRB nodes running on Polygon — updated from live telemetry.
Data sourced from the FRB Ecosystem Research hub and cross-validated against live block data.
Linkable summary
What this benchmark covers
We measured WSS endpoint latency, bundle inclusion rates, and gas-per-tx for four major Polygon RPC providers across EU, US, and APAC regions. Figures represent 30-day rolling averages from FRB relay nodes.
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
FRB relay nodes record timing and inclusion data on every submitted bundle. Here is what goes into each metric:
- 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?
A 1% improvement in inclusion rate compounds significantly over thousands of daily submissions. Even a 10 ms latency edge on Polygon can shift which sequencer slot your bundle lands in — particularly during high-throughput NFT or DeFi events.
Gas cost is a direct deduction from profit. The figures here reflect FRB-optimized bundles; generic bot tooling typically runs 15–25% higher gas per tx without relay-side optimization.
Limitations & methodology notes
- Latency values are from FRB-operated nodes. Run the WSS Latency Test.
- Success rates vary with network congestion. Figures are 30-day P50/P95 from stable trading periods.
- Provider tiers change. Always verify current rate limits and regional availability before committing.
These benchmarks are updated quarterly. If you spot an anomaly, file a report through the support channel.
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
Across EU/US/APAC POPs
Gas / tx
With private bundle preference
How FRB collects this data
Every FRB relay node submits bundles with a timing header. Our metrics pipeline records:
- Submission timestamp and block height target.
- Builder acknowledgment latency.
- Inclusion block vs. target block (filled, late, or missed).
Data is aggregated server-side and exported to the public API on a 15-minute delay.
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 Edge | 95 ms | 88% | Best for EU/US, includes burst quotas. |
| Alchemy Turbo | 110 ms | 86% | Pair with Polygon Builder for higher privacy. |
| Polygon Labs Public | 180 ms | 72% | Use as backup; FRB detects throttling automatically. |
| Ankr Premium | 140 ms | 79% | Good for APAC geos with moderate load. |
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.
Download benchmark JSON
Get the raw data for your own analysis, backtesting, or investor reporting.
Frequently asked questions
Why is Polygon latency so important?
Polygon slots finalize quickly. FRB's WSS rotation keeps jitter <150 ms so bundles do not land a block late.
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?
Yes. Cite this page and download the JSON export for audit trails.
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.