Status
TREX OTT Service Status
Live checks on the services we run, how to place a fault before escalating, and why there is no uptime percentage on this page.
Everything we monitor is responding
| Component | Status | HTTP | Response |
|---|---|---|---|
| Website & database Checked from inside this WordPress install. | Healthy | — | internal check |
| Store & checkout Whether the checkout page and product catalogue are live. | Healthy | — | internal check |
| App activation service The service the player app contacts when a device is activated. | Healthy | 200 | 50 ms |
Checked 1 second ago — 24 Aug 2026, 06:45 UTC. Re-checked at most every 5 minutes.
What this page does not show. Two of the rows above are internal checks — this WordPress install answering about its own database and store — and one is a real HTTP request to another host we run. They are not uptime statistics, and we do not publish an uptime percentage because we do not retain the long-run measurement history that would make one honest. Individual streaming channels are not probed here — if one channel is failing for you, send its name and the time to support and we will look at it directly.
Incident log
No incidents have been recorded since this log was started on 22 August 2026. Entries are added by hand when something affects a noticeable number of customers.
Placing a fault
The checks above cover the services we run and can measure from here. Most reports do not belong to that list, so this is how to route them before escalating.
| What you are seeing | Almost certainly |
|---|---|
| One of your customers stalls; the rest are fine | That customer’s connection or device. Point them at the viewer guides on t-rextv.io. |
| All of your customers lose the same channel at once | That stream at source. Send us the channel name and the time. |
| All of your customers lose everything at once | Escalate immediately with the detail listed in support escalation. |
| You cannot create or renew lines | Check your credit balance first, then the panel row above. |
| WHMCS actions fail but the panel works | Your WHMCS host, not the panel — see the integration guide. |
Why there is no uptime percentage here. A published figure is only meaningful if something measures continuously and retains the history. We do not do that, so a number would be decoration rather than information. If you need an uptime commitment for your own customer contracts, get it from sales in writing — do not quote a figure from a web page. Full policy.
What to tell your customers
Say what you know, when you knew it, and what you are doing about it. Do not promise a restoration time you have not been given, and do not promise an uptime percentage at all. Suggested wording for the common situations is in service status and maintenance.