All Systems Operational

Our core services are running normally. AI signals, .set updates, analytics, and deliveries are ready for you.

This page showcases our architecture and operational targets. Live status indicators are coming soon.

Components Overview

We run a multi-service architecture in the cloud. Each component has a clear responsibility and well-defined operational targets.

AI Model Service (Inference)

Operational

Generates real-time trade signals by matching learned patterns with live market data.

Typical target: p95 signal latency ≤ 300 ms (illustrative)

API Gateway / Backend

Operational

Secure delivery of signals, parameters, and service endpoints for bots and tools.

Typical target: p95 API latency ≤ 250 ms (illustrative)

Trade Intake (Order/Deal Collector)

Operational

Collects trades from connected accounts, normalizes logs, and forwards events for analysis.

Typical target: ingestion freshness ≤ 60 s (illustrative)

Accounts.Analyze (Metrics Compute)

Operational

Computes performance metrics and rankings used to surface top .set files.

Typical target: analytics lag ≤ 5 min (illustrative)

Broker Analytics & Log Harvester

Operational

Connectors for multiple MT5 brokers/servers to ingest execution stats and trade logs.

Typical target: connector health ≥ 99% (illustrative)

Optimization Cluster (MT5 Strategy Tester Automation)

Operational

Distributed optimisation on our 1024-core infrastructure to keep .set files fresh.

Typical target: new/updated .set files every ≤ 30 min (illustrative)

.set Delivery & Model Parameters (Cloud)

Operational

Cloud storage and CDN delivery of .set files and model parameters to your MT5.

Typical target: global delivery success ≥ 99.9% (illustrative)

Public Web & .setAnalyze

Operational

Public pages, knowledge base, and live rankings access.

Typical target: uptime ≥ 99.9% monthly (illustrative)

Notifications (Telegram Bot & Alerts)

Operational

Status updates, onboarding tips, and notifications.

Typical target: near real-time alerting (illustrative)

What We Monitor (Targets)

We define internal service level objectives (SLOs) to keep your trading experience smooth. Below are our core targets (illustrative).

Service Level Objectives

These are illustrative targets. Live dashboards and historical uptime will be added soon.

•
Signal latency (AI): p95 ≤ 300 ms
•
API latency: p95 ≤ 250 ms; low error rates
•
Trade ingestion freshness: ≤ 60 s
•
Analytics compute lag: ≤ 5 min
•
.set publication cadence: every ≤ 30 min
•
Public web uptime: ≥ 99.9% monthly

Reliability & Operations

Built for Continuity

Cloud-native services, redundancy across components, rolling updates, and continuous optimisation on 1024 cores.

No Single Point of Truth

We validate using multiple data sources: signals, trades, broker logs, and analytics.

Transparent by Design

We plan to publish live status, incidents, and maintenance windows on this page.

Roadmap to Live Status

What's next:

Coming Soon

We're working on bringing you live monitoring capabilities

Live component indicators with refresh
Incident feed and maintenance schedule
90-day uptime history and SLO adherence

[PLACEHOLDER: Live status widgets — coming soon]

Contact & Subscribe

Have a question or noticed something odd? We're quick to respond.

Get in Touch

Multiple ways to reach our support team

support@forexroboteasy.com

Telegram Bot

@forexroboteasybot

Telegram Channel (updates)

@fxroboteasy

Legal Notes

Telemetry Note

This page currently displays architecture and operational targets for illustration. Live telemetry will be introduced later.

Not Financial Advice

These operational details do not constitute trading advice. Markets can be moody — please manage risk responsibly.