Incredibly slow Internet bandwidth

So download bandwidth from Xfinity where I am in Chicago has gone from bad to worse. The Xfinity speedtest tool clocks in at 17.1 Mbps for downloads (even uploads are a bit faster). I've restarted everything multiple times. Called Xfinity last night and of course was told that everything looks good to my modem and that I should reach out to the modem vendor for support. This is not a modem issue - it is an Xfitnity issue and only got worse after the hour plus outage yesterday in the area.

Traceroutes to Google's DNS are slow. There always seems to be an issue after 24.153.88.109:

traceroute to 8.8.4.4 (8.8.4.4), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  4.567 ms  4.680 ms  3.238 ms
 2  * 96.120.28.137 (96.120.28.137)  14.110 ms  17.599 ms
 3  po-313-1294-rur202.area4.il.chicago.comcast.net (96.110.167.141)  12.170 ms  15.894 ms  13.319 ms
 4  * po-2-rur201.area4.il.chicago.comcast.net (162.151.44.1)  11.918 ms  10.152 ms
 5  po-200-xar01.area4.il.chicago.comcast.net (24.153.88.109)  10.494 ms  16.513 ms  17.757 ms
 6  * * *
 7  be-501-ar01.area4.il.chicago.comcast.net (96.216.150.114)  18.012 ms  16.758 ms
    be-502-ar01.area4.il.chicago.comcast.net (96.216.150.118)  14.067 ms
 8  c-50-171-101-226.unallocated.comcastbusiness.net (50.171.101.226)  16.430 ms
    c-50-171-101-230.unallocated.comcastbusiness.net (50.171.101.230)  19.668 ms
    c-50-171-101-226.unallocated.comcastbusiness.net (50.171.101.226)  17.304 ms
 9  * * *
10  dns.google (8.8.4.4)  15.944 ms  17.529 ms  19.573 ms

Here is the traceroute just trying to get to comcast.net:

traceroute to comcast.net (96.99.227.0), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  4.718 ms  4.178 ms  6.990 ms
 2  96.120.28.137 (96.120.28.137)  18.031 ms  15.908 ms  22.134 ms
 3  po-313-1294-rur202.area4.il.chicago.comcast.net (96.110.167.141)  13.061 ms  15.263 ms  14.020 ms
 4  po-2-rur201.area4.il.chicago.comcast.net (162.151.44.1)  15.658 ms  11.297 ms  14.763 ms
 5  po-200-xar01.area4.il.chicago.comcast.net (24.153.88.109)  15.328 ms  9.874 ms  19.826 ms
 6  be-314-arsc1.area4.il.chicago.comcast.net (96.108.34.137)  28.828 ms * *
 7  be-502-ar01.area4.il.chicago.comcast.net (96.216.150.118)  14.288 ms
    be-501-ar01.area4.il.chicago.comcast.net (96.216.150.114)  12.816 ms  13.966 ms
 8  be-32211-cs21.350ecermak.il.ibone.comcast.net (96.110.40.49)  17.602 ms
    be-32231-cs23.350ecermak.il.ibone.comcast.net (96.110.40.57)  21.858 ms
    be-32221-cs22.350ecermak.il.ibone.comcast.net (96.110.40.53)  16.310 ms
 9  ae31-0-ar01-d.ashburn.va.ndcasbn.comcast.net (68.86.93.210)  31.607 ms *
    ae31-0-ar02-d.ashburn.va.ndcasbn.comcast.net (68.86.93.178)  51.814 ms
10  et-3-36-1-sas04-d.ashburn.va.ndcasbn.comcast.net (96.108.75.118)  29.392 ms
    et-3-36-1-sas02-d.ashburn.va.ndcasbn.comcast.net (96.108.75.102)  35.983 ms
    et-4-36-1-sas03-d.ashburn.va.ndcasbn.comcast.net (96.108.75.122)  28.562 ms
11  et-0-0-59-1-ss09b-d.ashburn.va.ndcasbn.comcast.net (96.108.96.6)  44.140 ms
    et-0-0-71-1-ss09b-d.ashburn.va.ndcasbn.comcast.net (162.151.179.166)  34.476 ms  46.584 ms
12  * * *
13  * * *
14  * * *
15  * * *

This is not a local issue. Hard to guess if it is a larger routing issue from Comcast or something else, but this is not something that I need a tech sent to my home to resolve.