Here are 2 trace routes to google if that helps identify where the issue is originating
#1:
Tracing route to www.google.com [2607:f8b0:4007:804::2004]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 2600:8800:3b80:11ea:5aef:68ff:fe25:4896
2 68 ms 13 ms 14 ms 2600:8800:3bff:ffff::1111
3 71 ms 8 ms 11 ms 2001:578:801:fffc:600::2e
4 18 ms 10 ms 12 ms 2001:578:900:4::8
5 21 ms 25 ms 98 ms 2001:578:1:0:172:17:249:33
6 111 ms 36 ms 24 ms 2001:4860:1:1:0:58f5::
7 28 ms 25 ms 99 ms 2001:4860:0:110e::1
8 72 ms 25 ms 21 ms 2001:4860:0:1::2419
9 49 ms 59 ms 54 ms lax28s15-in-x04.1e100.net [2607:f8b0:4007:804::2004]
Trace complete.
#2:
Tracing route to www.google.com [2607:f8b0:4007:804::2004]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 2600:8800:3b80:11ea:5aef:68ff:fe25:4896
2 98 ms 100 ms 113 ms 2600:8800:3bff:ffff::1111
3 * 9 ms 41 ms 2001:578:801:fffc:600::2e
4 56 ms 91 ms 21 ms 2001:578:900:4::8
5 21 ms 91 ms 25 ms 2001:578:1:0:172:17:249:33
6 26 ms 21 ms 54 ms 2001:4860:1:1:0:58f5::
7 31 ms 35 ms 28 ms 2001:4860:0:110e::1
8 94 ms 29 ms 107 ms 2001:4860:0:1::2419
9 * 31 ms 85 ms lax28s15-in-x04.1e100.net [2607:f8b0:4007:804::2004]
Trace complete.