Status
TREX IPTV Status
Live reachability checks on the services we run, an incident log, and how to work out whether a problem is on our side or yours.
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 | 52 ms |
Checked 1 minute ago — 31 Oct 2026, 14:59 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.
How to tell whether a problem is ours
The checks above cover the services we run and can measure. Most problems people report are not on that list, so here is how to place them.
| What you are seeing | Almost certainly |
|---|---|
| Every device in your house stalls on every channel | Your connection — see how much speed you need |
| One device stalls, another is fine | That device or its Wi-Fi — see the buffering fix |
| One channel fails, everything else plays | That stream. Send us its name and the time. |
| Nothing plays but the channel list loads | Your connection limit, or an expired line — see login failure |
| This website will not load at all | Would show as Website: not reachable above — if it does not, the problem is between you and us |
Why there is no uptime percentage here. A published uptime figure is only meaningful if somebody is measuring continuously and retaining the history. We are not doing that yet, so printing a number would be decoration rather than information. The live checks above and the incident log are what we can actually stand behind.
Reporting an outage
Send the channel name, the time, the device and whether a second device shows the same thing to WhatsApp or Telegram. Anything that affects a noticeable number of customers is added to the incident log above.
Is TREX IPTV down? Checks before reporting a problem
A failed stream does not by itself confirm a service-wide outage. Check the timestamp and scope of the monitoring above first. A responding website or activation endpoint does not establish that every channel is playing, and an empty incident log is not proof that nobody is experiencing a fault.
Separate a channel problem from an account problem
Try another channel and note whether the programme list loads. If you test another device, stop playback on the first one so you do not exceed your subscription's simultaneous-connection limit. A failure affecting one channel, one player or all playback gives support different evidence; none of these observations alone establishes the cause.
Check the connection without changing everything at once
Confirm whether other internet services work on the same device. Restart the player, then retest before changing another setting. Do not clear application data or reinstall until your login details are recoverable. See the safe cache-clearing guide and buffering checklist for the difference between playback interruptions and login failures.
What to send TREX support
Include the time and time zone, device model, app version, exact error, and whether one or several channels are affected. Say which checks you have already tried. Share account references only through a trusted support channel, never in public screenshots containing passwords or playlist URLs. Use the support page to continue troubleshooting; this checklist does not promise an outage resolution time.