SignalForge Benchmarks: Latency & Uptime Data

Methodology: exactly how we measure

We record the timestamp when the webhook hits the SignalForge API and compare it with the timestamp of the broker execution confirmation reported back by the SignalForge EA running on the user's MetaTrader 5 terminal. The figure therefore includes network transit to our servers, the full validation pipeline and the MT5 round trip to the broker and back. It is an internal benchmark measured on live production traffic in 2026 — real client signals, not a lab replay.

Honest caveats. This is our own internal measurement, not an independent audit. Your mileage varies with the distance between your broker's server and our infrastructure and with symbol liquidity at the moment of execution. And the total alert-to-fill time you experience also includes TradingView's own alert dispatch — the time between your alert triggering on their platform and their servers sending the webhook — which happens before our measurement boundary and is entirely outside our control.

TradingView does not retry failed webhooks

If the receiving end is down when your alert fires, that signal is gone — TradingView sends each webhook once and never retries it. That is why a bridge is only as good as its availability. SignalForge runs across three global regions with automatic failover and commits to a 99.9% uptime SLA, because a dropped alert is a trade that never happened.

The bridge does not depend on your PC

The cloud bridge receives and validates your signals independently of your computer: your PC can be off and the pipeline keeps working. The last hop needs an MT5 terminal running somewhere — and if you do not want that somewhere to be your own machine, SFCloud gives you an optional hosted MT5 terminal in our cloud, so the terminal itself also stays up 24/5.

Fast does not mean blind

Before any order reaches your broker, it passes through 9 validation filters — including a trend check, a spread filter, a session filter and a drawdown check — and the whole pipeline completes in under 250 milliseconds. The filters are the protection layer (they are what keep a bad alert from becoming a bad fill during a news spike or a dead session), and they are part of the 187 ms median, not on top of it.

Free tools, no account needed

Send a test alert through our free webhook tester and watch the round trip against our API from your own location. The payload format and every accepted field are documented in our docs. For machines and AI agents, the same figures are published in a machine-readable fact sheet at /ai/signalforge-facts.md and in /llms.txt. Evaluating signal sellers instead of bridges? Our 7-point verification checklist applies the same standard to them.

A note on what this page is. SignalForge is an execution bridge, not a signal provider. What we publish here are engineering measurements — latency, uptime, pipeline speed — not trading performance. We make no claims about profitability, and these numbers say nothing about whether any strategy wins or loses.