Error determining whether HTTP request was canceled

I am getting this error non-stop:

[6bc1d3a9-c3d7-4852-98fc-bf10863c7f60] 2020-11-05T08:54:33-05:00 ERROR metabase.async.streaming-response Error determining whether HTTP request was canceled
java.lang.ClassCastException: org.eclipse.jetty.io.SocketChannelEndPoint cannot be cast to java.nio.channels.SocketChannel
at metabase.async.streaming_response$canceled_QMARK_.invokeStatic(streaming_response.clj:140)
at metabase.async.streaming_response$canceled_QMARK_.invoke(streaming_response.clj:131)
at metabase.async.streaming_response$start_async_cancel_loop_BANG_$fn__24762$state_machine__15982__auto____24769$fn__24771$inst_24711__24786.invoke(streaming_response.clj:166)
at metabase.async.util$cancelable_thread_call$fn__24417$fn__24418.invoke(util.clj:51)
at metabase.async.util$cancelable_thread_call$fn__24417.invoke(util.clj:50)
at clojure.lang.AFn.applyToHelper(AFn.java:152)
at clojure.lang.AFn.applyTo(AFn.java:144)
at clojure.core$apply.invokeStatic(core.clj:665)
at clojure.core$with_bindings_STAR_.invokeStatic(core.clj:1973)
at clojure.core$with_bindings_STAR_.doInvoke(core.clj:1973)
at clojure.lang.RestFn.invoke(RestFn.java:425)
at clojure.lang.AFn.applyToHelper(AFn.java:156)
at clojure.lang.RestFn.applyTo(RestFn.java:132)
at clojure.core$apply.invokeStatic(core.clj:669)
at clojure.core$bound_fn_STAR_$fn__5749.doInvoke(core.clj:2003)
at clojure.lang.RestFn.invoke(RestFn.java:397)
at clojure.lang.AFn.run(AFn.java:22)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

To the best of my knowledge nothing has changed. We are running the latest version but verified the same error shows when rolling back to the previous.

Restarting the server or service results in the same thing as soon as it starts back up. Any way I can determine what is running and stop it?

Figured it out, DNS problem on the server.