Как найти причину моей потери пакета?

Question

Я использую Интернет из моего университета. Все помещения и офисы соединены кабелем Ethernet через множество коммутаторов. Много раз я терял пакет, я думаю, что один коммутатор или модем проблематичны. Как определить причину? (Я знаю, что многие сведения отсутствуют, но скажите мне, что вам нужно знать, и я обновлю вопрос)

ping -t google.com
Reply from 216.58.211.46: bytes=32 time=92ms TTL=48
Request timed out.
Reply from 216.58.211.46: bytes=32 time=86ms TTL=48
Reply from 216.58.211.46: bytes=32 time=77ms TTL=48
Reply from 216.58.211.46: bytes=32 time=93ms TTL=48
Reply from 216.58.211.46: bytes=32 time=92ms TTL=48
Reply from 216.58.211.46: bytes=32 time=70ms TTL=48
Reply from 216.58.211.46: bytes=32 time=77ms TTL=48
Reply from 216.58.211.46: bytes=32 time=99ms TTL=48
Reply from 216.58.211.46: bytes=32 time=92ms TTL=48
Reply from 216.58.211.46: bytes=32 time=93ms TTL=48
Reply from 216.58.211.46: bytes=32 time=93ms TTL=48
Reply from 216.58.211.46: bytes=32 time=87ms TTL=48
Reply from 216.58.211.46: bytes=32 time=98ms TTL=48
Reply from 216.58.211.46: bytes=32 time=93ms TTL=48
Reply from 216.58.211.46: bytes=32 time=108ms TTL=48
Reply from 216.58.211.46: bytes=32 time=98ms TTL=48
Reply from 216.58.211.46: bytes=32 time=83ms TTL=48
Reply from 216.58.211.46: bytes=32 time=70ms TTL=48
Reply from 216.58.211.46: bytes=32 time=101ms TTL=48
Reply from 216.58.211.46: bytes=32 time=101ms TTL=48
Reply from 216.58.211.46: bytes=32 time=96ms TTL=48
Reply from 216.58.211.46: bytes=32 time=98ms TTL=48
Reply from 216.58.211.46: bytes=32 time=101ms TTL=48
Request timed out.
Reply from 216.58.211.46: bytes=32 time=96ms TTL=48
Request timed out.
Reply from 216.58.211.46: bytes=32 time=99ms TTL=48
Reply from 216.58.211.46: bytes=32 time=122ms TTL=48
Reply from 216.58.211.46: bytes=32 time=97ms TTL=48
Reply from 216.58.211.46: bytes=32 time=98ms TTL=48
Reply from 216.58.211.46: bytes=32 time=96ms TTL=48
Reply from 216.58.211.46: bytes=32 time=98ms TTL=48
Reply from 216.58.211.46: bytes=32 time=102ms TTL=48
Reply from 216.58.211.46: bytes=32 time=97ms TTL=48
Reply from 216.58.211.46: bytes=32 time=94ms TTL=48
Reply from 216.58.211.46: bytes=32 time=92ms TTL=48
Reply from 216.58.211.46: bytes=32 time=96ms TTL=48
Reply from 216.58.211.46: bytes=32 time=88ms TTL=48
Reply from 216.58.211.46: bytes=32 time=97ms TTL=48
Reply from 216.58.211.46: bytes=32 time=95ms TTL=48
Reply from 216.58.211.46: bytes=32 time=122ms TTL=48
Reply from 216.58.211.46: bytes=32 time=88ms TTL=48
Reply from 216.58.211.46: bytes=32 time=100ms TTL=48
Reply from 216.58.211.46: bytes=32 time=99ms TTL=48
Reply from 216.58.211.46: bytes=32 time=94ms TTL=48
Reply from 216.58.211.46: bytes=32 time=95ms TTL=48
Reply from 216.58.211.46: bytes=32 time=97ms TTL=48
Reply from 216.58.211.46: bytes=32 time=101ms TTL=48
Reply from 216.58.211.46: bytes=32 time=88ms TTL=48
Reply from 216.58.211.46: bytes=32 time=94ms TTL=48
Reply from 216.58.211.46: bytes=32 time=78ms TTL=48
Reply from 216.58.211.46: bytes=32 time=94ms TTL=48
Reply from 216.58.211.46: bytes=32 time=100ms TTL=48
Request timed out.
Reply from 216.58.211.46: bytes=32 time=86ms TTL=48
Reply from 216.58.211.46: bytes=32 time=102ms TTL=48
Reply from 216.58.211.46: bytes=32 time=95ms TTL=48
Reply from 216.58.211.46: bytes=32 time=99ms TTL=48
Reply from 216.58.211.46: bytes=32 time=94ms TTL=48
Reply from 216.58.211.46: bytes=32 time=96ms TTL=48
Reply from 216.58.211.46: bytes=32 time=101ms TTL=48
Reply from 216.58.211.46: bytes=32 time=96ms TTL=48
Reply from 216.58.211.46: bytes=32 time=95ms TTL=48
Reply from 216.58.211.46: bytes=32 time=97ms TTL=48
Reply from 216.58.211.46: bytes=32 time=74ms TTL=48
Reply from 216.58.211.46: bytes=32 time=90ms TTL=48
Reply from 216.58.211.46: bytes=32 time=87ms TTL=48

Ping statistics for 216.58.211.46:
    Packets: Sent = 128, Received = 123, Lost = 5 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 131ms, Average = 94ms