AZ Chandler - constant packet loss

Status tracking:

1. 03/21/20: initial packet loss issue reported to Cox CSR.  Also started posting on Cox Internet forum with PingPlot tracegraph showing issue started from Hop2.
   1. during the week of 3/16~3/21, multiple service outages (unplanned) experienced.  
   2. Replaced Arris SB6180 (which is capable to handle my 150/10 plan) with Motorola MB8600 (Gigablast approved).  No improvement.  Still seeing significant packet loss. 
2. 03/22/20: Cox Contractor on-site.  Measured Tx/Rx signal quality from tube (tap), Cox cable box, and coax outlet in my room where the cable modem is connected to.  The tech admitted that the signal is already weak at tube and there is not much he can do to fix it.  He added MOCA filter in the cable box and replaced the coax connector too; no improvement. 
3. 03/23/20: emailed cox.help with 24hr PingPlotter trace showing ~10% packet loss.
4. 03/24/20: received email response from Cox CSR
   "There is currently maintenance occurring in your area so we won't be able to do any testing right now."
5. During the week of 03/22~03/28, experiencing service outages on a daily basis.
6. 3/28/20: updated in both Cox CSR and Cox Internet forum with continued packet loss issue (7day PingPlotter trace attached).  
   1. KevinM2 responded 03/29 asking to reach out on Twitter, FB or cox.help @ Cox.net  (which I did already on cox.help email).  I went ahead and reached out to Twitter.  Twitter CSR apologized for the situation and offered credits for the inconvenience.  Again stated
      "There is currently maintenance occurring in your area so we won't be able to do any testing right now.".  When pressed for the schedule of node split, was given the typical answer 
      "As far as the upgrade does, there are multiple factors involved in the planning and scheduling of this type of work and we are unable to effect any change to the schedule."
7. 03/28/20  FCC informal complaint filed with 7-day PingPlotter traced attached; clearly indicating Hop2 ISP node being the problem.
8. 03/31/20  received a call from Cox Executive Office responding to FCC compliant.  During the call he agreed to node over-saturation issue (500+ people on the node while typically should only have 200~300).  Promised to get back to me on the infrastructure upgrade schedule.  Btw, it was not clear the infrastructure upgrade is a node split or fiber optical upgrade to the tube.