bill001g :
Run a tracert to the server or to 8.8.8.8.
What you are looking for is what node in the path you get most the increase. If it is not in the first one it is not inside your house. Hop2 represent the delay between your house and the ISP and farther hops are other routers in the ISP network and other ISP networks.
It would have been nice to have a trace when it was lower so you could compare.
If it is not in the first 2 hops it will be hard to get fixed. I could be something like your ISP or another ISP had a failure and moved to a backup connection that connects in a different city so the data must go a longer path.
Ok so I ran it again and got this, this is second time running it and 1.1.1.1
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.domain.actdsltmp [192.168.0.1]
2 41 ms 41 ms 41 ms tukw-dsl-gw11-75.tukw.qwest.net [63.231.10.75]
3 41 ms 41 ms 41 ms tukw-agw1.inet.qwest.net [63.226.198.81]
4 42 ms 41 ms 41 ms sea-brdr-02.inet.qwest.net [67.14.41.190]
5 46 ms 45 ms 43 ms sea-b2-link.telia.net [62.115.45.14]
6 42 ms 42 ms 42 ms cloudflare-ic-328262-sea-b1.c.telia.net [62.115.63.55]
7 43 ms 43 ms 43 ms one.one.one.one [1.1.1.1]
Trace complete.
C:\Users\Nick>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.domain.actdsltmp [192.168.0.1]
2 41 ms 40 ms 41 ms tukw-dsl-gw11-75.tukw.qwest.net [63.231.10.75]
3 41 ms 41 ms 41 ms tukw-agw1.inet.qwest.net [63.226.198.81]
4 41 ms 41 ms 42 ms sea-edge-12.inet.qwest.net [67.14.41.58]
5 42 ms 41 ms 41 ms 63-158-222-114.dia.static.qwest.net [63.158.222.114]
6 42 ms 42 ms 42 ms 108.170.245.113
7 42 ms 42 ms 42 ms 108.170.237.203
8 43 ms 42 ms 42 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.