Status
Can signals reach a copier PC right now?
This page publishes the health of the Meridian service itself, measured by the same bridge that carries your signals — not a third-party ping of the website. Two things decide whether a copied trade actually happens: a copier PC connected and receiving, and a valid TLS certificate on the public endpoint. Both are watched continuously, sampled every minute, and reported here with their uptime history and every incident, open or closed. The values below refresh on their own; you never have to reload.
Component detail loads here — signal routing and the TLS certificate, each with the time it was last sampled.
The uptime table loads here: the trailing day, week and month for each component, computed from the recorded samples.
Recent incidents
An incident opens the moment a component leaves the operational state and closes when it returns, with both times in UTC. A component can pass through a degraded state on its way to a full outage, and that is one incident, not two — the entry tracks the current condition until it ends.
The incident list loads here once the feed answers.
The service
What the components mean
Signal intake — the public route your TradingView alerts post to is answering. Copier connections — copier PCs can connect to the service. Dashboard — the dashboard is answering. Each is checked every minute from the service itself.
This page is about the service, not any one account: whether your copier PC is connected is shown on your dashboard, and if you switch on copier alerts you are emailed or sent a push or Telegram message when it drops and again when it returns. A signal that arrives while your PC is away is held briefly and then refused with an explanation the sender can read — nothing is silently dropped.
TLS certificate
What the certificate component means
Every endpoint on this service — the dashboard, the signal intake, the pairing handshake — is served over TLS with a certificate that has to be renewed before it expires. The component reads the remaining life of the certificate actually on disk: comfortably far out is operational, inside the two-week window it turns degraded as an early warning, and inside three days it reports down, because a certificate that has expired makes browsers refuse the site and webhook senders fail their handshake. Renewal itself runs automatically on a nightly schedule and applies without restarting anything; the state here exists so a failed renewal is visible the same day it happens instead of when a customer cannot sign in. Both thresholds — the early warning and the critical one — are the same the nightly probe reports, so this page and the service's own logs never disagree about what counts as a problem.
Measurement
How the uptime figures are produced
The bridge writes one sample per component every minute: the observed state, a short reason, and the time. The percentages in the table are the share of those samples that were operational, over the trailing twenty-four hours, seven days and thirty days — each window computed from the samples it actually contains, never interpolated and never carried forward from a previous period. A window without enough samples yet says it is collecting rather than showing a figure it cannot back. Samples are kept for thirty-one days, so the month column is complete coverage and not an estimate. The clock is UTC throughout, which is why an incident time may sit a few hours from what your local calendar shows.
Trading impact
What a status here means for your trades
While signal routing is down, new signals are not being copied: the bridge accepts them for a short hold window in case the copier returns, then refuses them so a sender is never left wondering whether an alert vanished. Orders already at the broker are untouched — the copier's job at that moment is protective exits, and those run locally on the trading PC whether or not this page is green, because the risk guards live beside NinjaTrader rather than on the server. When the copier reconnects, it reconciles with the leader and resumes copying; nothing that was refused has to be resent by hand unless the sender's own strategy assumes delivery. If you are mid-evaluation and cannot afford an interruption, the dashboard's own copier alerts are the faster channel: they are per-account, and they fire the moment your PC is the one that dropped.
Contact
If this page says operational and your own signals still are not arriving, the problem is specific to your account rather than the service — start with the copier window's journal, which records every signal and why it was held, then email hello@meridiansignaldesk.com with the time of the attempt. State changes are also mailed to the operator addresses configured on this deployment, so an outage is communicated even when nobody has this page open.