Z3's here and a MX250 Hub.  18.107 caused major issues.  See this ping response!   Pinging 10.59.97.249 with 32 bytes of data: Reply from 10.59.97.249: bytes=32 time=1682ms TTL=60 Reply from 10.59.97.249: bytes=32 time=3423ms TTL=60 Reply from 10.59.97.249: bytes=32 time=3168ms TTL=60 Reply from 10.59.97.249: bytes=32 time=2440ms TTL=60 Request timed out. Reply from 10.59.97.249: bytes=32 time=1823ms TTL=60 Reply from 10.59.97.249: bytes=32 time=2578ms TTL=60 Request timed out. Ping statistics for 10.59.97.249: Packets: Sent = 8, Received = 6, Lost = 2 (25% loss), Approximate round trip times in milli-seconds: Minimum = 1682ms, Maximum = 3423ms, Average = 2519ms   Rolling back to 17.10.2 fixed issue for most, but didn't work on all.  Seems the rollback fails often. ... View more

Exactly the same issue in our organization!!  Upgraded 300 clients to 18.107 and the network degraded to unusable! Opened a support case but they have no reports of issues as it's new.  I rolled back all 300 to 17.10.2 and most seemed to resolve while a handful failed the rollback and still have super high ping responses and timeouts.  I really hope a fix if determined soon. ... View more