diff --git a/libraries/networking/src/udt/SendQueue.cpp b/libraries/networking/src/udt/SendQueue.cpp
index 4642689eee..a84a0b35d2 100644
--- a/libraries/networking/src/udt/SendQueue.cpp
+++ b/libraries/networking/src/udt/SendQueue.cpp
@@ -337,8 +337,14 @@ void SendQueue::run() {
         // which can lock the NodeList if it's attempting to clear connections
         // for now we guard this by capping the time this thread and sleep for
 
-        const microseconds MAX_SEND_QUEUE_SLEEP_USECS { 5000000 };
+        const microseconds MAX_SEND_QUEUE_SLEEP_USECS { 2000000 };
         if (timeToSleep > MAX_SEND_QUEUE_SLEEP_USECS) {
+            qWarning() << "udt::SendQueue wanted to sleep for" << timeToSleep.count() << "microseconds";
+            qWarning() << "Capping sleep to" << MAX_SEND_QUEUE_SLEEP_USECS.count();
+            qWarning() << "PSP:" << _packetSendPeriod << "NPD:" << nextPacketDelta
+                << "NPT:" << nextPacketTimestamp.time_since_epoch().count()
+                << "NOW:" << now.time_since_epoch().count();
+
             // alright, we're in a weird state
             // we want to know why this is happening so we can implement a better fix than this guard
             // send some details up to the API (if the user allows us) that indicate how we could such a large timeToSleep