Xfinity issue connecting to my work VPN

I'm having problems connecting to gpcloud.connect.boeing.com and gpcloud.connect.boeing.com.
I called my work IT and they say Xfinity is blocking their URLs. It is working when I use the hotspot on my phone, so the problem is in Xfinity side.

I run through the steps mentioned here: https://forums.xfinity.com/conversations/your-home-network/unable-to-connect-to-internet-with-my-work-laptop/697e54a8bef17951d874fce6?commentId=697e570fbef17951d87543bb and it is not solving the problem.

As a note, this was working on Thursday 02/12 and has been working for the past weeks. I noticed the problem Friday 02/13 in the Morning.

See ping/traceroutes below to the two endpoints, showing it is not reaching out destination but it is pass the home internet gateway.

I need a solution to this, otherwise I cannot work, if I cannot work this internet connection is useless to me.

Also, the xfinity assistant/chat is completely useless and frustrating for this. How can I open an actual ticket/complain or talk to a human?

% traceroute gpcloud.connect.boeing.com
traceroute to tbc.fed.prismaaccess.com (3.221.142.193), 64 hops max, 40 byte packets
 1  10.0.0.1 (10.0.0.1)  12.219 ms  4.635 ms  5.392 ms
 2  10.60.129.43 (10.60.129.43)  14.670 ms
    10.60.129.42 (10.60.129.42)  39.557 ms  103.862 ms
 3  po-60-rur302.bellevue.wa.seattle.comcast.net (96.217.132.25)  15.975 ms
    po-60-rur301.bellevue.wa.seattle.comcast.net (96.217.132.21)  18.033 ms
    po-60-rur302.bellevue.wa.seattle.comcast.net (96.217.132.25)  14.409 ms
 4  po-2-rur302.bellevue.wa.seattle.comcast.net (69.139.161.118)  15.963 ms
    po-300-xar02.bellevue.wa.seattle.comcast.net (68.86.96.157)  31.732 ms
    po-2-rur302.bellevue.wa.seattle.comcast.net (69.139.161.118)  17.781 ms
 5  be-300-arsc1.seattle.wa.seattle.comcast.net (24.124.128.89)  16.384 ms  19.938 ms
    po-300-xar02.bellevue.wa.seattle.comcast.net (68.86.96.157)  15.395 ms
 6  be-36141-cs04.seattle.wa.ibone.comcast.net (68.86.93.13)  39.409 ms
    be-300-arsc1.seattle.wa.seattle.comcast.net (24.124.128.89)  19.495 ms
    be-36121-cs02.seattle.wa.ibone.comcast.net (68.86.93.5)  18.249 ms
 7  be-36131-cs03.seattle.wa.ibone.comcast.net (68.86.93.9)  36.111 ms
    be-2401-pe01.seattle.wa.ibone.comcast.net (96.110.39.230)  14.262 ms
    be-36131-cs03.seattle.wa.ibone.comcast.net (68.86.93.9)  14.488 ms
 8  * be-2201-pe01.seattle.wa.ibone.comcast.net (96.110.39.206)  26.799 ms *
 9  * * *
10  * * *

% ping -c 5 gpcloud.connect.boeing.com
PING tbc.fed.prismaaccess.com (3.221.142.193): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3

--- tbc.fed.prismaaccess.com ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

---

% traceroute gp.connect.boeing.com 
traceroute to gp-connect.lb.boeing.com (130.76.179.240), 64 hops max, 40 byte packets
 1  10.0.0.1 (10.0.0.1)  6.014 ms  3.421 ms  3.997 ms
 2  10.60.129.43 (10.60.129.43)  13.379 ms
    10.60.129.42 (10.60.129.42)  15.912 ms  13.909 ms
 3  po-60-rur302.bellevue.wa.seattle.comcast.net (96.217.132.25)  13.337 ms
    po-60-rur301.bellevue.wa.seattle.comcast.net (96.217.132.21)  17.216 ms
    po-60-rur302.bellevue.wa.seattle.comcast.net (96.217.132.25)  106.948 ms
 4  po-2-rur302.bellevue.wa.seattle.comcast.net (69.139.161.118)  16.137 ms
    po-300-xar02.bellevue.wa.seattle.comcast.net (68.86.96.157)  18.224 ms
    po-2-rur302.bellevue.wa.seattle.comcast.net (69.139.161.118)  18.509 ms
 5  be-300-arsc1.seattle.wa.seattle.comcast.net (24.124.128.89)  15.468 ms  13.324 ms
    po-300-xar02.bellevue.wa.seattle.comcast.net (68.86.96.157)  16.415 ms
 6  ae13.edge6.sea1.sp.lumen.tech (4.68.37.129)  11.674 ms
    be-300-arsc1.seattle.wa.seattle.comcast.net (24.124.128.89)  17.466 ms
    ae13.edge6.sea1.sp.lumen.tech (4.68.37.129)  18.117 ms
 7  ae13.edge6.sea1.sp.lumen.tech (4.68.37.129)  16.888 ms
    ae1.3618.ear1.lasvegas1.net.lumen.tech (4.69.209.50)  47.810 ms
    ae13.edge6.sea1.sp.lumen.tech (4.68.37.129)  18.108 ms
 8  the-boeing.ear1.lasvegas1.level3.net (4.25.9.138)  51.313 ms
    ae1.3618.ear1.lasvegas1.net.lumen.tech (4.69.209.50)  46.611 ms
    the-boeing.ear1.lasvegas1.level3.net (4.25.9.138)  52.531 ms
 9  the-boeing.ear1.lasvegas1.level3.net (4.25.9.138)  46.807 ms *  58.219 ms
10  * * *
11  * * *
12  * * *


% ping -c 5 gp.connect.boeing.com
PING gp-connect.lb.boeing.com (130.76.150.17): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3

--- gp-connect.lb.boeing.com ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss