LeafIPTV Service Status | Is IPTV Down or Is It You?
How to tell in five minutes whether an IPTV problem is the service or your own network, what a real outage looks like, and how to report one usefully.
This page does not show a live dashboard, and we are not going to fake one. Automated per-server monitoring is on the roadmap and not yet published; until it is, status is reported through support. What this page does instead is more useful than a green tick most of the time: it shows you how to tell, in about five minutes, whether a problem is ours or yours — because the honest answer is that it is usually yours, and that is fixable.
Why we do not publish an uptime figure
A '99.9% uptime' badge on a page nobody measures is decoration. Publishing one would take about ten minutes and would tell you nothing, because there would be no measurement behind it and no way for you to check.
When automated monitoring is live, this page will show what it actually measures, including the incidents. Until then, treat any provider's unverified uptime number — ours or anyone else's — as marketing rather than information.
Five minutes to find out whose problem it is
Work through these in order. Each step rules out a whole category of cause, and by the end you will either have fixed it or have something specific to report.
- Try a second channel, then a third. One dead channel is not an outage — it is one channel.
- Try a different device on the same connection. If the phone works and the television does not, the service is fine.
- Try the same device on mobile data instead of home Wi-Fi. If it works, the problem is your home network.
- Open the same playlist in VLC and watch the lost-buffer count. Rising numbers mean delivery, not decoding.
- Restart the router, then the streaming device. In that order, and give the router a full two minutes.
What an actual outage looks like
A real service-side problem is broad and abrupt: every channel fails at once, on every device, on more than one network, and the player reports an authentication or connection error rather than buffering. Buffering is almost never an outage — it is a capacity problem somewhere between the source and your screen, and most of that path is not ours.
If one category works and another does not, or if it fails only on one device, or only in the evening, that pattern rules an outage out. Those are the three most common reports we receive and none of them has ever been a server being down.
Reporting something usefully
The difference between a report we can act on in minutes and one that takes days is entirely in the detail. Tell us the channel name, the exact time, the device and player, whether other devices on the same connection are affected, and what the player's error message said — verbatim, not paraphrased.
Never send a screenshot with your username, password or server URL visible. Blank those fields first. We do not need them to investigate, and a screenshot posted in a public forum is the most common way subscriptions get taken over.
Planned work
Maintenance that we expect to interrupt service is announced by email to active subscribers before it happens, not after. If you received no notice and something is broadly broken, it was not planned.
Questions
Is the server down?
Usually not. Work through the five checks above — a second channel, a second device, a second network, VLC, a restart. If every channel fails on every device across two different networks, contact support with those details and we will tell you what we are seeing.
Why is there no live status dashboard?
Because there is no automated monitoring behind it yet, and a status page with nothing measuring it is worse than no status page. It is a genuine gap and it is being built; until it exists, this page tells you how to diagnose the problem yourself and how to reach a person.
Everything buffers between 8pm and 11pm. Is that an outage?
No — that pattern is peak congestion on your connection, particularly on shared cable. An outage does not keep office hours. Test the same content at midday: if it is clean then, the service is not the constraint.
How will I know about planned maintenance?
By email to the address on your account, before the work happens. If you have not had a notice and the service is broadly unavailable, treat it as unplanned and report it.