Screenshot?

i updated it

Might be worth it to hit WIN + R to bring up the Run window, type in cmd, then type in "ping 8.8.8.8 -n 50" to send 50 packets to one of google's servers and see what info you recieve

If you're experiencing heavy packet loss then I would probably check with people on your network to see if they're doing something or call your ISP; you'll also be able to see what your latency is looking like.

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=12ms TTL=58
Reply from 8.8.8.8: bytes=32 time=11ms TTL=58
Reply from 8.8.8.8: bytes=32 time=11ms TTL=58
Reply from 8.8.8.8: bytes=32 time=9ms TTL=58
Reply from 8.8.8.8: bytes=32 time=7ms TTL=58
Reply from 8.8.8.8: bytes=32 time=9ms TTL=58
Reply from 8.8.8.8: bytes=32 time=9ms TTL=58
Reply from 8.8.8.8: bytes=32 time=9ms TTL=58
Reply from 8.8.8.8: bytes=32 time=12ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=13ms TTL=58
Reply from 8.8.8.8: bytes=32 time=9ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=21ms TTL=58
Reply from 8.8.8.8: bytes=32 time=16ms TTL=58
Reply from 8.8.8.8: bytes=32 time=30ms TTL=58
Reply from 8.8.8.8: bytes=32 time=11ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=8ms TTL=58
Reply from 8.8.8.8: bytes=32 time=8ms TTL=58
Reply from 8.8.8.8: bytes=32 time=15ms TTL=58
Reply from 8.8.8.8: bytes=32 time=13ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=15ms TTL=58
Reply from 8.8.8.8: bytes=32 time=8ms TTL=58
Reply from 8.8.8.8: bytes=32 time=16ms TTL=58
Reply from 8.8.8.8: bytes=32 time=9ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=7ms TTL=58
Reply from 8.8.8.8: bytes=32 time=14ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=9ms TTL=58
Reply from 8.8.8.8: bytes=32 time=17ms TTL=58
Reply from 8.8.8.8: bytes=32 time=14ms TTL=58
Reply from 8.8.8.8: bytes=32 time=8ms TTL=58
Reply from 8.8.8.8: bytes=32 time=8ms TTL=58
Reply from 8.8.8.8: bytes=32 time=33ms TTL=58
Reply from 8.8.8.8: bytes=32 time=11ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=8ms TTL=58
Reply from 8.8.8.8: bytes=32 time=9ms TTL=58
Reply from 8.8.8.8: bytes=32 time=8ms TTL=58
Reply from 8.8.8.8: bytes=32 time=8ms TTL=58
Reply from 8.8.8.8: bytes=32 time=9ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=7ms TTL=58
Reply from 8.8.8.8: bytes=32 time=7ms TTL=58
Reply from 8.8.8.8: bytes=32 time=11ms TTL=58

Ping statistics for 8.8.8.8:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 33ms, Average = 11ms

So I pinged the tf2 server that i'm on through my router panel and it said average is 73 ping but I'm getting an average of 90-110 ping in game
Packets: 20/20 transmitted, 20/20 received, 0% loss
Round Trip Time:
Minimum = 72.26 ms
Maximum = 76.38 ms
Average = 73.09 ms

Have you done an internet speed test

hmm, my speed test is looking fine, it appears to be a problem only in tf2
I tried switching to my 5G network and the exact same problem happened

Download and run WinMTR or Pingplotter. Let it make a trace to 8.8.8.8 while you're playing.

If the ping is already spiking towards the first hop (your router), it's probably just a case of congested wifi. Use a wire.
If the ping starts to spike after the router, your internet line might be congested. Because you're sharing the connection with other people or devices.

I took those tests while connected to a tf2 server, the packet loss only happens in tf2, my internet line isn’t congested because even when I’m alone in the house I get bad internet.
I was thinking that’s it’s an issue with my net settings I need to fix

Well, what are your net settings?

looks more like packet choke than packet loss. even looking at your google ping results it looks like you have some packet choke. has there been any recent changes either hardware or software associated with your network?

Is there anything you can do about that?

I know some routers have traffic shaping and that kind of thing, would this help? My connection is quite often like that.

Just FYI most ISP's will never guarantee anything (High internet DL/UL, consistently low ping, etc) over wifi, because there's just no way to be able to offer any sort of consistency for wireless, it just has that many factors and outliers that it'd be impossible to get a consistent anything over wifi.

I wrote a "little" post about that just now: http://www.teamfortress.tv/44322/shared-home-internet-without-lag-and-ping-spikes

cl_cmdrate 128
cl_interp .007 // this will likely have to be user defined .007 should be roughly the lowest interp, hit scan might do well at .0152 for this
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 128
rate 90000 // With higher tick rates you have more bandwidth being used

Could you also share your speedtest results?

My speed test results are how they always are 7 ping 60 down 70 up

It probably is heavy network usage, or shitty wifi coverage. My internet only gives me 3-4 bars max where my desk is set up, and whenever other people in my house start using the internet my ping in tf2 starts to shoot up to thousands in net_graph 2. I haven't done it, but 100% recommend ethernet if its possible

cl_cmdrate 66 // Send to server at this many times per second
cl_updaterate 66 // Get from server at this many times per seconds
cl_interp_ratio 1 // Reduce entity interpolation times to minimum
net_queued_packet_thread 1 // Work around bad Windows networking
cl_interp 0 // Use cl_interp_ratio for a more accurate value
net_compresspackets 1 // Compress packets to prevent split packets
net_compresspackets_minsize 1260 // Only compress packets if we would send a splitpacket
rate 170016 // High rate to reduce choke and scale to packet rate
            // Might want to lower rate if you have <1.4Mbps stable upload
net_maxcleartime 0.015 // Balance between reducing network delay and choke
net_maxpacketdrop 5000 // Use default packet drop threshold
net_splitrate 4 // Split 4 packets per frame, reduces choke but is more CPU intensive
net_splitpacket_maxrate 170016 // Scale splitpacket to rate
                               // Might want to lower rate if you have <1.4Mbps stable upload
cl_timeout 70 // Wait the maximum time before automatically timing out on client
cl_pred_optimize 2 // Skip repredicting if we do not need to do it
cl_lagcompensation 1 // Ensure lag compensation is turned on
cl_predictweapons 1 // Ensure weapon firing prediction is turned on
cl_smooth 1 // Smooth out prediction errors
cl_smoothtime 0.1 // Smooth out view for 0.1 seconds

try these net settings

rate 170016 is pointless because virtually every server limits it to a max of 100000
cl_smooth is preference and makes no difference on network performance

on another note, I notice some servers lately blocking cl_interp_ratio 2 (always stays at 1 when you try to change it) so I've had to go back to using cl_interp when I want to change lerp, can anybody else confirm this?

How is it pointless if it works? The default is unlimited, so on a lot of servers, it will use 170016. If a server does happen to limit it, then it will be set to 100000. I don't see the problem.

It still affects network feel and gets rid of some stutters/jumping view from incorrect client prediction.