I checked and those two channels plus a few others weren't working for me either. I re-scanned my TVE source (DirecTV Stream) and now they're working again.
I got multiple (15) disconnects on a Discovery channel recording this morning.
I think the Discovery Networks CDN had an issue.
Failed to download segment... https://go-prod-vz.akamaized.net/... 503 Service Unavailable
The "503 Service Unavailable" error means that the server is temporarily unable to handle the request, often due to being overloaded or undergoing maintenance. This is a common issue that can resolve itself after some time.
Sure looks that way, something is not right with their CDN.
I did rescans, re-auth YTTV, delete Channels and reinstall. These only seemed to clear the issue for a few minutes, which I now think is a placebo because the issue seems to be on the CDN.
now seeing in Sources. akamai token not found
Probably best to wait it out and not remove the source.
When my recording was getting disconnected this morning, CDVR even tried to re-auth the channel and got an error, before it finally recovered 1 minute before the recording ended.
2026/03/14 05:00:31.609307 [TVE] action=science_stream error={[{access.denied.missingpackage 403 {[Discovery] }}] {{[]}}}
2026/03/14 05:00:31.614031 [ERR] Failed to start stream on channel 6101 via TVE-YouTubeTV: TVE: playback info: access.denied.missingpackage: Discovery
Sure hope this is not the beginning of Discovery ending TVE like Paramount, Disney, NBC.
I got lucky and was able to record it directly from tv.YTTV using PrismCast.
My TVE feed is Eastern and my tv.YTTV feed is Western in PrismCast.
Ok, I have noticed something, this seems to happen when local ads are getting inserted over the national feed. So some kind of issue with the switch to the local ad server. Since HLS feed in chunks, the switch over fails while the remaining buffering is playing out. At least that is what it looks like to me,
I think the ads show up like this in the url
&oid=...&is_ad=1
I'm guessing here that oid= is pointing to the program stream id to go back to after the ad. Original ID?
For me it has been the Travel Channel and Science Channel (probably due to I watch these channels live the most)..
I noticed last evening that Science Channel would connect for a few minutes, then stop or freeze, then start up few a few minutes, then freeze again.
Been doing the same today.
Didn't have problems going directly to The Science Channel website - using provider link to sign-in.
Discovery not working for me either.
Error during live stream for ch6101 DISCOVERY: Failed to download segment 5: https ://go-prod-vz.akamaized.net/ausw2....
Animal Planet working fine
HGTV, Discovery Turbo(MotorTrend) not working
. Last night gold rush and freddy mine rescue on Discovery had issues with dropped portion of shows.
Will retest tomorrow morning with the sunday am rerun of the corrupted gold rush episode.
It's hit and miss trying to play each Discovery Networks channel (I'm using the web UI player and another browser tab open with the DVR logs).
Seeing this error sometimes (that I haven't seen in a long time)
[ERR] ULK invalid: {"next_time": -1, "error": "The pt received must be greater than the last …d less than or equal to the returned next_time (24.0). We received 0.0."}
same. I caught it early enough last night to record the replay of mine rescue, but it's corrupted too. I havn't watched either to see if its the same spots.
think i'll remove the tve source for the night to catch the gold rush replay on ah4c/ospreys
Im getting the same failed to download segment error this morning from Discovery
Error running job 1773568740-ch6101 Gold Rush: Failed to download segment 51: https://go-prod-vz.akamaized.net/ausw2/slices/f73/e6cf0c55d
I have been getting the same error since at least yesterday.
Hopefully something that cures itself.
Seeing the same issue since March 13th and have been trying everything I can to resolve but I'm still getting the same errors as others here.
Hoping we see something soon.
Below is a snippet from my logs:
2026/03/15 15:22:03.268388 [TNR] Opened connection to TVE-buc020 for ch6102 FOOD
2026/03/15 15:22:03.268388 [HLS] Starting live stream for channel 6102 from 192.168.0.194 (bitrate=5553kbps)
2026/03/15 15:22:04.292566 [ERR] ULK invalid: {"next_time": -1, "error": "The pt received must be greater than the last …d less than or equal to the returned next_time (20.0). We received 0.0."}
2026/03/15 15:22:13.289095 [ERR] Probe failed for live stream after 10.020158s and 0 bytes
2026/03/15 15:22:15.114473 [HLS] Couldn't generate stream playlist for ch6102-dTVE-buc020-ip192.168.0.194: HLS: 901 Tuner Unreachable: Could not tune to ch6102 after 12s
2026/03/15 15:22:15.114473 [HLS] Stopping transcoder session ch6102-dTVE-buc020-ip192.168.0.194 (out=0s finished=false first_seq=0 last_seq=-1)
2026/03/15 15:22:15.115611 [TNR] Closed connection to TVE-buc020 for ch6102 FOOD
2026/03/15 15:22:15.119437 [SNR] Buffer statistics for ch6102 FOOD: buf=0% drop=0%
2026/03/15 15:22:15.119437 [SNR] Streaming statistics for ch6102 FOOD: timeouts=0 segment_timeouts=0 playlist_timeouts=0
2026/03/15 15:22:15.353357 [TVE] stream timestamps: food: start_at=2026-03-15T15:21:16-04:00 end_at=2026-03-15T15:21:46-04:00 live_delay=26.4983576s
It's hit or miss even when it's happening! Last night, one recording failed on HGTV, one ran for 4 minutes at some point on Discovery. This morning, everything is working 100% as far as I can see. So, I'll just blame David Zaslav because it's generally his fault for everything 