Forum Discussion

SoManyProblems9's avatar
SoManyProblems9
New Contributor II
2 years ago
Solved

Cox Increases Fiber-Powered Internet Speeds for Most Customers

I saw this post on the Cox website and was excited: https://newsroom.cox.com/Cox-Increases-Fiber-powered-Internet-Speeds I checked my service speed on cox.com and it looks like I was upgraded to 50...
bad service
coxsupport
internet
  • SoManyProblems9's avatar
    SoManyProblems9
    2 years ago

    In Summary: If your Plan Speed In the Cox Wifi App when running a speedtest does not match your service speed on your Cox.com account. You will most likely need to have Cox Support "Fully" Reprovision your Modem.

    Fixed and working! Thanks Brian from Cox Support!

    Below From Cox Agent:

    I apologize for any interruption if you were actively online, but this should be working now. I was able to fully reprovision the modem and now it is showing the proper quality of service for 500 Mbps download.

    This link is proof of working system at correct speed from Cox Wifi App Speedtest: Link

orbops's avatar
orbops
New Contributor
2 years ago

I also am only getting 300Mbps down and 250Mbps up. I was originally getting around 250Mbps down and 150Mbps up. Personally I think it's more promotional, since they have so many qualifiers of why you may not be getting the desired speed.

  • WiderMouthOpen's avatar
    WiderMouthOpen
    Esteemed Contributor II
    2 years ago

    I think the speed increase was mostly for cable(HFC) customers. If your getting 250Mbps up, you must be fiber. Did you get notification of your speeds changing?

    • orbops's avatar
      orbops
      New Contributor
      2 years ago

      Yes, I received an email from Cox a few days ago. We are on fiber.

      • WiderMouthOpen's avatar
        WiderMouthOpen
        Esteemed Contributor II
        2 years ago

        Have you tested direct to the ONT? If so, I would email Cox at cox.help@cox.com and see if your circuit is rated for 500Mbps. Not sure how it works with fiber but maybe something on the backend has to be refreshed with the change.