99.427%
Observed checks passed
Measured public evidence
Monthly reliability, including the failures.
This report is calculated from scheduled canaries and recorded execution outcomes. It does not turn demo tests or broker acknowledgements into invented performance claims.
2026-10
Month to date
Generated 10/22/2026, 7:29:33 PM
66.67%
Execution success · 4/6 terminal attempts
2.95 s
Median confirmation · N=4
3.61 s
P95 confirmation · N=4
Monitoring gaps are unknown—not uptime
2093 of 2093 completed 15-minute intervals contain a snapshot in this report. 0 intervals have no stored observation. Longest unobserved stretch: 0 minutes.
Passing and failing checks both count as observations. The current unfinished interval is excluded. These numbers measure evidence coverage, not continuous service availability.
Service availability
AI parser
2094/2094 successful checks
100.000%
Background worker
2093/2094 successful checks
99.952%
Cloud MT execution
2094/2094 successful checks
100.000%
Cloud trade reconciliation
2092/2094 successful checks
99.904%
Database
2091/2094 successful checks
99.857%
Desktop API
2094/2094 successful checks
100.000%
EA API
2093/2094 successful checks
99.952%
Email API
2087/2094 successful checks
99.666%
Email intake
2092/2094 successful checks
99.904%
Gumroad card payments
2094/2094 successful checks
100.000%
Paper trade lifecycle
2093/2094 successful checks
99.952%
Synthetic execution lifecycle
2093/2094 successful checks
99.952%
Telegram bot
2094/2094 successful checks
100.000%
Telegram intake
2092/2094 successful checks
99.904%
USDT verification
2094/2094 successful checks
100.000%
Webhook delivery
2092/2094 successful checks
99.904%
Recorded rejection causes
Symbol mapping
1196
Plan or allowance
191
Signal format
147
Other recorded cause
119
Incidents
No incidents are recorded for this month.
How the numbers are calculated
- • Availability is the share of recorded canary checks that passed, not time-weighted uptime. Missing checks are not assumed successful; unconfigured optional integrations are excluded.
- • Monitoring coverage counts completed 15-minute UTC intervals containing a valid platform snapshot, whether passing or failing. The current unfinished interval is excluded. Missing intervals are unknown, not outages or successes. A snapshot does not prove every service was checked or that the whole interval was healthy. At most the first 100 gaps are listed.
- • Execution, monitoring, and incident aggregates page through all stored records in the requested UTC calendar month. Coverage reports the collected and database-counted totals; current-month writes after the count appear on the next cached refresh.
- • Legacy Desktop history uploads without verified broker receipts are excluded from execution proof. A recorded execution status is receiver-reported evidence, not independent broker certification.
- • Execution success rate uses terminal attempted signals only: executed divided by executed plus failed.
- • Latency is reported by recorded source, parse, dispatch, broker-acceptance and confirmed-fill stages. Missing stages remain missing and are never inferred.
- • Broker rejection causes are grouped into public categories; private messages, account identifiers and credentials are never published.
Previous calendar month (2026-09), all stored rows: checks passed 96.720%; execution success 77.78%.