Anycast Not Working Properly

Hello - Who do I need to escalate this with to get Anycast working correctly for our area?  The last few months it has been thinking Chicago is the closest area to us, but our connection is in Idaho/Utah.  It had been working fine and always selecting Denver as the closest, or areas in California were always the next closest.  Chicago shouldn't be getting the traffic at all.  I have waited for it to perhaps sort itself out, but it appears to be getting worse rather than better, as even google.com is now heading all the way to Chicago.  Here are a few examples to help:

google.com
(first hops deleted for privacy)
  6    11 ms    17 ms    13 ms  be-501-ar01.saltlakecity.ut.utah.comcast.net [24.124.175.214]
  7     *        *        *     Request timed out.
  8    20 ms     8 ms     9 ms  216.239.62.187
  9    11 ms    12 ms    13 ms  142.250.212.26
 10    24 ms   124 ms    16 ms  142.251.241.220
 11    40 ms    43 ms    31 ms  108.170.252.152
 12    34 ms     *       34 ms  209.85.249.128
 13    43 ms    41 ms    43 ms  192.178.255.11
 14    43 ms    44 ms    43 ms  209.85.249.137
 15    40 ms    41 ms    38 ms  192.178.249.209
 16    42 ms     *       45 ms  142.251.60.11
 17    42 ms    39 ms    39 ms  ord38s30-in-f14.1e100.net [142.250.191.174]

doh.xfinity.com
(first hops deleted for privacy)

 7    20 ms    17 ms    17 ms  be-501-ar01.saltlakecity.ut.utah.comcast.net [24.124.175.214]
  8    25 ms    33 ms    22 ms  be-36721-cs02.champa.co.ibone.comcast.net [96.110.43.229]
  9    54 ms    44 ms    52 ms  be-1224-cs22.northlake.il.ibone.comcast.net [96.110.35.53]
 10     *       47 ms    44 ms  96.110.41.54
 11    45 ms    54 ms     *     et-0-0-1-sas02-d.northlake.il.ndcchgo.comcast.net [69.139.239.122]
 12    51 ms    54 ms    62 ms  lo0-t1s8016-d.northlake.il.ndcchgo.comcast.net [96.109.108.90]
 13     *       44 ms    48 ms  lo0-t2s8006-d.northlake.il.ndcchgo.comcast.net [96.109.108.64]
 14    51 ms    43 ms    50 ms  lo0-t1s8009-d.northlake.il.ndcchgo.comcast.net [96.109.108.83]
 15     *        *        *     Request timed out.
 16    44 ms    43 ms    44 ms  10.60.164.131

dns.nextdns.io (Major DNS provider)
(first hops deleted for privacy)

 6    12 ms    13 ms    12 ms  be-501-ar01.saltlakecity.ut.utah.comcast.net [24.124.175.214]
  7    19 ms    22 ms    21 ms  be-36741-cs04.champa.co.ibone.comcast.net [96.110.43.237]
  8    46 ms    43 ms    54 ms  be-2311-pe11.350ecermak.il.ibone.comcast.net [96.110.33.202]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    43 ms    44 ms    43 ms  dns.nextdns.io [45.76.21.53]

dns.controld.com (Major DNS provider)
(first hops deleted for privacy)

 7     7 ms    12 ms    13 ms  be-501-ar01.saltlakecity.ut.utah.comcast.net [24.124.175.214]
  8    23 ms    30 ms    22 ms  be-36741-cs04.champa.co.ibone.comcast.net [96.110.43.237]
  9    18 ms    26 ms    21 ms  be-3412-pe12.910fifteenth.co.ibone.comcast.net [96.110.33.142]
 10    23 ms    26 ms    21 ms  ae-3.a00.dnvrco04.us.bb.gin.ntt.net [129.250.9.132]
 11     *        *        *     Request timed out.
 12    42 ms    46 ms    39 ms  ae-5.r25.chcgil09.us.bb.gin.ntt.net [129.250.3.160]
 13    55 ms    48 ms    43 ms  ae-13.a05.chcgil09.us.bb.gin.ntt.net [129.250.4.23]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18    43 ms    41 ms    51 ms  dns.controld.com [76.76.2.22]

You can see traffic now just goes right through Denver/Colorado and straight to Chicago/Illinois.  I am using my own modem, and have forced it to grab a different IP and that didn't change anything.  I can't be the only one in the area having this issue.  Thanks for any help in getting this escalated to a network engineer who can sort it out.