diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 4205c38..8c8a5bc 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -17,7 +17,7 @@ Carefully read and work through this check list in order to prevent the most com
 - [ ] I've updated `tubeup`, `yt-dlp` and `internetarchive` along with their associated dependencies to their latest versions as supported by each afformentioned package setup scripts.
 - [ ] I've included the full and unredacted URL and console output (with the exception of site usernames and passwords, or IP addresses of the machine doing the download). I understand hiding URLs will get issue closed on sight.
 - [ ] I've checked that all provided URLs are alive, playable in a browser and arguments with special characters are properly quoted or escaped.
-- [ ] I've searched the issues (closed or open) for similar bug reports, not just here on Tubeup, but yt-dlps issue tracker for download issues similar to mine and internetarchives issue tracker for upload issues similar to mine. YT-DLP has an issue up [listing known bugs](https://github.com/yt-dlp/yt-dlp/issues/3766).
+- [ ] I've searched the issues (closed or open) for similar bug reports, not just here on Tubeup, but [yt-dlps issue tracker](https://github.com/yt-dlp/yt-dlp/issues) for download issues similar to mine and [internetarchives issue tracker](https://github.com/jjjake/internetarchive/issues) for upload issues similar to mine. YT-DLP has an issue up [listing known bugs](https://github.com/yt-dlp/yt-dlp/issues/3766).
 - [ ] I'm not submitting a bug report about IA S3 timeouts (we have no control over Internet Archive outages or per-user throttling, and sometimes the site has maintence like hard disk swaps)
 - [ ] I've checked the Twitter account of Internet Archive (@internetarchive) for any announced outages or planned infrastructure maintenance that would affect performance of uploads.
 - [ ] I have properly indented [with triple backticks before and after the console output](https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf) full terminal terminal output from the line where the command was run to where I was returned to command prompt, and am not trying to obscure item identifiers or URLs used in the creation of the bug (we need this to recreate the bug or investigate what happened).