4 million requests
“the gateway processed more than 4 million requests across chat completions, responses, embeddings, and MCP calls”
As published on truefoundry.com. Captured by usedby on Oct 6, 2026.
What happened
FloQast routes all of its LLM traffic across multiple model providers and regions through the TrueFoundry AI Gateway. It also uses the gateway for MCP server and agent tool management, security guardrails, per-feature cost tracking, and storing prompts and traces in its own cloud infrastructure.
Summary written by usedby from the source page, in English. The figures are those of TrueFoundry and FloQast, not ours.
- 98.9%“maintaining a 98.9% success rate on model traffic”
- ~53ms“Over 90 days the gateway evaluated 80K+ guardrail checks while adding only ~53ms of average latency”
- 139K“The MCP gateway handled 139K tool calls across servers like playbook, transform, FDM, and JEM, at an average latency of 389ms”
- 3.73M“Intelligent routing directed 3.73M requests through virtual-model routing rules with a routing failure rate near 0.04%.”
By centralizing on TrueFoundry, FloQast turned a complex multi-provider, multi-region AI footprint into a single governed platform.
Most definitely it's been a huge game changer. Reliability was our key concern when looking for a gateway. The fact that everything can be stored within our own infrastructure, so we keep our own data-governance rules for traces and prompts, plus a centralized point for observability and pricing data and coverage on security best practices it's been really helpful.
What the story claims, and what we checked
We compared the story with its live page on Oct 6, 2026.
- The figure: 4 million requestsCheckedPrinted word for word on the page, near the name of FloQast.
- The passage quoted aboveCheckedCopied word for word from the page, near the name of FloQast.
- FloQast uses TrueFoundryCheckedConfirmed line. Latest check across sources: Oct 6, 2026.
- The result itselfNot checkedWe quote it; we did not measure it.




