*FINAL UPDATE*
Despite the most recent snapshot being unavailable, the previous one was, so data within two hours was restored. Any new accounts or password changes (few if any) will need to be redone. No payments appear to have been missed, but an automated check should be pick them up later today.
If you got an unexpected email about a payment being applied twice, it can be ignored.
Thankfully, normality is restored!
]]>2025-11-18 03:46:00 UTC: we’ve rebuilt all the lineups that we can.
Our systems detected an issue where our upstream provider began deleting channels; while this is a normal occurrence as part of lineup maintenance, the number of channels which were deleted exceeded a threshold. We immediately began taking action to mitigate the issue and alerted them via P1 tickets that their data feeds were incorrect, and that they were deleting active channels.
From the subscriber perspective, your application may have provided a notification that a channel has been deleted, or that a schedule is unavailable. You may see a lineup appearing to have a channel in a position, but there is no callsign.
Our immediate action will be to restore lineups and schedules. You may notice anomalies, such as missing channel icons. Once our upstream has stabilized their data feeds, we will rebuild the lineups; this will make channel icons and other secondary data available.
]]>It appears that on Sept-26 Amazon changed the way they notifiy us of payment, breaking our processing!
Amazon payments are currently disabled, while we figure out how to proceed.
Here's a rant with details and status
RobertE
]]>HERE is a NextPVR forum thread about it.
]]>This appears to be unrelated to the BOT issue, and has never happened before.
Yesterday, we switched to using Cloudfare bot defenses on the forum and it is helping. I've turned the SD forum back on.
]]>All versions (including v10.10.7) have SchedulesDirect bugs in them. Click HERE for more info
In Jellyfin, this will appear as "Country/Region" appearing as undefined, or errors in the Jellyfin log files.
Please see these threads for more information:
In order to use Jellyfin with SchedulesDirect, you will need to disable the native SchedulesDirect grabber and use another program, like EPG123 or one of the tv_grab_zz grabbers from the xmltv.org project to download schedules, convert to XML, and then import the XML into Jellyfin.
Please use the Jellyfin support forum for any additional troubleshooting: https://forum.jellyfin.org/f-troubleshooting
SageTV now has an active developer; all versions of SageTV prior to v9.2.13 are deprecated / non-API compliant.
Please see this thread: For instructions on how to install a supported version of SageTV.
Once you're running a supported version of an application, please open a lineup support ticket to have your account unblocked.
]]>The SD-DD service isn't affected
I don't know the details on the SageTV issues, but it's similar.
12/18 Update: The block occurs after 5000 login failures in a few minutes.. basically a denial of service attack. If you disable Jellyfin's grabber and switch to XMLTV source, open a lineup support ticket, request a ban remove and include your ip address (you can get it here).
02/04 Update: The issue with Jellyfin wasn't fixed in 10.10.4 (or 10.10.5). JellyFin is still ignoring the "back pressure" responses that we send once they've hit a limit and just keep going at 20-100 requests per second.
02/21 Update: Reports show both Jellyfin and SageTV are still triggering denial of service attack defenses. To remove a block open a lineup support ticket, request a ban remove and include your ip address (you can get it here). It's a good idea to disable what's causing the problem and switch to a good data source (probably XMLTV based) while the issues are being worked.
Here's the Jellyfin github issue
Please resubmit any tickets submitted in the past few days
]]>When you signed up with a Microsoft email we warned you that they often accept mail for delivery and then drop them. Now they're not even accepting them, which is more honest, but still bad. Of course we never send marketing emails.
If you're not receiving emails from us, now you know why!
We have tickets open with the vendor to resolve the issue. They already moved us to another IP, but it got blocked too!]]>