Pushing fails periodically with `dial tcp: lookup github.com: no such host` error, disrupts network

Hello, good people of Git LFS!

My teammate has been experiencing some very strange, and consistently inconsistent, results when trying to push to our Git LFS repo. We've been trying to debug this for weeks and are out of ideas, but I've noticed a few similar issues on here so I figured maybe there's been some understanding gained recently, although I can't tell if these issues were resolved for others.

My colleague is on Windows 10, git-lfs 2.3.4, got version 2.15.0.windows.1

Sometimes, when she pushes (either from the command line or from the latest Github Desktop client), the push begins successfully, then fails while pushing files to LFS, she loses all network connectivity on her home network- Slack immediately goes yellow, websites fail to load, she can't ping google, etc. At first we thought it was just her network being flaky, but she has no problems uploading streaming video for hours, and the pattern has clearly emerged - I've seen her push, then immediately get disconnected from our screen-sharing session. Her network generally recovers in 2-5 minutes, and she is sometimes able to push successfully later in the day. This has been happening for weeks, and the basic stuff we can think to do (refresh DHCP, restart the computer, restart the router, disabling her firewall etc.) hasn't helped.

The errors tend to end with the error dial tcp: lookup lfs.github.com: no such host or dial tcp: lookup github.com: no such host, though this may be a symptom of the network already being taken down rather than the cause. I honestly have no clue how a git push could take down her overall internet connectivity, but it really does appear that this is what's happening. Any pointers on how to debug this further?

Thanks for all your great work on LFS!