#Centurylink small business services blank auto-pay info on their end in apparent #vig rollout fuckup, then shut service immediately.
Support is worse than useless: They can't escalate anything.
Sending this to neighbors also afflicted with #CenturyLumen for at least one of their providers.
#Lumen #monopsony #telco #isp #fail #incompetent #vigorish #JunkFees #CenturylinkSucks
In case it hits you too: #Centurylink/#Lumen is instituting an illegal $3 #vig on CC payments as of 14 Jul 2024, except for CO and MN where #JunkFees are more strictly prohibited. They screwed rollout, and broke autopay on the CC they've used before. They immediately shut down my net. Support could only go on about "check with your bank". Meanwhile, other CC purchases on the same card, including at #Centurylink LOL, work fine. #CenturylinkSucks

This was in the email whine they sent about their failure. Note missing #Centurylink account ID (two spaces) and missing last 4 of CC.

"Your xx/yy/2024 payment could not be processed using account ending in ; however, your service will remain active for three calendar days."

They clearly didn't process the payment (CC blanked by their code), and false-flagged it as "refused" by the "bank". Hey, a null bank can't process null cards! #CenturylinkSucks

The error is _technically_ correct, but is also entirely functionally wrong for seeing and solving the real problem. LOL. Maybe #Centurylink should have TESTED the code for addition of the #vig (and exempting no-junk-fees tariffed states) before deploying it against their customers? #CenturylinkSucks
Narrator: 3 days, my ass. Ports 80 and 443 (at minimum) were downed immediately in an incompetent manner (intercepts rather than connection failure). Had to manually switch to backup provider to chat with them. Uselessly, as it turns out. Support agents can't escalate anything, so #Centurylink have also set themselves up for systemic failure on system failure reports. #CenturylinkSucks