It can be anything from russkies, red chinese, hackers etc
to a service outage due to solar flares, fire, flood, earthquake, or other major bad juju
example of small outage
http://www.chinookobserver.com/co/free/20180716/internet-fiber-cut-resulting-in-lengthy-internet-outageexample of BIG outages
http://www.cnn.com/2008/WORLD/meast/02/01/internet.outage/https://www.wsj.com/articles/SB10001424052748704893604576199952421569210example of REALLY LARGE outage (took out much of Asia )
https://www.nytimes.com/2006/12/28/business/worldbusiness/28quake.html----------------------------------------------------------------------------
you can use ping and tracert to see what is happening and where the bottleneck is.
here is an example of a "good" ping
C:>ping
www.cascity.comPinging
www.cascity.com [64.182.121.182] with 32 bytes of data:
Reply from 64.182.121.182: bytes=32 time=39ms TTL=51
Reply from 64.182.121.182: bytes=32 time=40ms TTL=51
Reply from 64.182.121.182: bytes=32 time=37ms TTL=51
Reply from 64.182.121.182: bytes=32 time=39ms TTL=51
Ping statistics for 64.182.121.182:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 40ms, Average = 38ms
here is an example of a good tracert
C:>tracert
www.cascity.comTracing route to
www.cascity.com [64.182.121.182]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms "your computer's IP"
2 10 ms 11 ms 12 ms "your local ISP first hop- usually a neighborhood router"
3 12 ms 11 ms 11 ms "your local ISP 2nd hop"
4 14 ms 19 ms 14 ms "your local ISP 3rd hop"
5 11 ms 12 ms 13 ms "your local ISP 4th hop"
6 22 ms 21 ms 22 ms be-33654-cr02.1601milehigh.co.ibone.comcast.net[68.86.95.237]
7 20 ms 20 ms 19 ms be-12176-pe02.910fifteenth.co.ibone.comcast.net[68.86.83.94]
8 21 ms 21 ms 19 ms 96-87-8-46-static.hfc.comcastbusiness.net [96.87.8.46]
9 22 ms 21 ms 23 ms be3415.ccr22.den01.atlas.cogentco.com [154.54.30.241]
10 38 ms 36 ms 37 ms be3036.ccr22.mci01.atlas.cogentco.com [154.54.31.90]
11 39 ms 39 ms 38 ms be2433.ccr32.dfw01.atlas.cogentco.com [154.54.3.213]
12 39 ms 39 ms 38 ms be2764.ccr41.dfw03.atlas.cogentco.com [154.54.47.214]
13 38 ms 39 ms 39 ms be3235.rcr21.dfw05.atlas.cogentco.com [154.54.7.178]
14 40 ms 42 ms 37 ms te0-0-2-0.nr11.b000326-4.dfw05.atlas.cogentco.com [154.24.22.6]
15 39 ms 38 ms 39 ms e-10-1.edge1.dal.corespace.com [38.122.56.38]
16 41 ms 39 ms 38 ms e-10-6.core2.dal.corespace.com [64.182.161.83]
17 38 ms 39 ms 37 ms 64-182-121-182.static.dal01.corespace.com [64.182.121.182]
Trace complete.
ping tells us if there is a problem. all 4 transmits should go thru, and typically less than 50 ms.
but bear in mind that some servers have disabled the "pingback"
tracert will show "where" things bog down down the line.
here is an example of a sever that is "down"
C:>ping
www.limabeads.comPinging
www.limabeads.com [35.169.58.18] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 35.169.58.18:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:>tracert
www.limabeads.comTracing route to
www.limabeads.com [35.169.58.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms your pc
2 11 ms 11 ms 11 ms your local ISP first hop
3 11 ms 11 ms 11 ms "your local ISP 2nd hop
4 13 ms 11 ms 11 ms "your local ISP 3rd hop
5 11 ms 11 ms 12 ms "your local ISP 4th hop
6 36 ms 34 ms 33 ms be-33654-cr02.losangeles.ca.ibone.comcast.net [68.86.166.65]
7 51 ms 51 ms 50 ms be-11524-cr02.dallas.tx.ibone.comcast.net [68.86.87.174]
8 58 ms 49 ms 49 ms be-12495-pe03.1950stemmons.tx.ibone.comcast.net[68.86.85.194]
9 48 ms 49 ms 51 ms 50.248.118.202
10 66 ms 58 ms 55 ms 54.239.105.117
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * ^C
C:\Users\angel>
here are some details
https://en.wikipedia.org/wiki/Traceroutehttps://support.microsoft.com/en-us/help/314868/how-to-use-tracert-to-troubleshoot-tcp-ip-problems-in-windowshttps://support.microsoft.com/en-us/help/814155/how-to-use-ping-exe-to-check-your-microsoft-broadband-network-adapterhope this helps
prof marvel