A Jackson, Mississippi web host has cut off a customer of 15 years, days after a cyberattack knocked his website and email offline for over a week. The case, first reported by WLBT on October 15, 2026 and separately covered by WTVA, puts a face on a problem that security researchers have flagged for years: when a web hosting company gets breached, the fallout often lands hardest on the small businesses that can least afford to absorb it.
The host is U.S.NEXT, based in Jackson. The customer is Dennis Fett, who runs what WLBT describes as a global peacock information center, a 30-year-old business that depends on its website for orders and consulting work. Fett’s site and email went dark after an October 8 cyberattack and stayed down for eight days. Then, according to Fett, the company’s owner called with different news: not a timeline for restoring service, but a recommendation to find a new host entirely.
What WLBT Confirmed About the Jackson Web Host Cyberattack
WLBT’s 3 On Your Side consumer desk pieced together the account directly from Fett, and the station noted that U.S.NEXT did not respond to its request for an explanation about the outage. That gap matters. It means the public record on this cyberattack currently consists of one customer’s experience and a hosting company’s silence, not a technical breach disclosure from U.S.NEXT itself.
What is confirmed: the outage began October 8, Fett’s site and email were unreachable for eight days, and the owner of U.S.NEXT personally called Fett to tell him the company would not continue hosting his site after more than 15 years as a customer. What is not confirmed is just as important. WLBT’s report does not identify how attackers got in, who they were, whether any data was accessed, or whether a ransom was demanded. It also does not establish that Fett was the only client dropped, only that he was at least one confirmed case.
That distinction is worth holding onto as the story spreads. A single-client anecdote and a sector-wide hosting failure are very different stories, and right now the verified facts support only the former, with hints the latter may also be true.
Who Is Dennis Fett and Why a Peacock Website Matters
Fett’s business is not a Fortune 500 account. It is a 30-year-old operation built around being, in his own description, the go-to resource for peacock information worldwide. That kind of niche authority site is exactly the type of small, high-trust web presence that rarely makes headlines until something breaks it. Fett told WLBT his business generates orders and consulting income through the site, and that the outage cost him both.
The business model is a reminder that “small business website” covers an enormous range of operations, from local restaurants to single-owner specialty consultancies that have quietly served a global customer base for decades. For Fett, 15 years with the same host was not a casual vendor relationship. It was infrastructure he built a consulting practice on top of.
Timeline of the U.S.NEXT Cyberattack and Its Aftermath
The sequence of events, drawn from WLBT’s reporting, is short but telling. Here is what happened and when, based only on what has been confirmed publicly so far.
| Date / Period | Event | Source |
|---|---|---|
| October 8, 2026 | Cyberattack hits U.S.NEXT, disrupting hosted websites and email | WLBT |
| October 8–15, 2026 | Dennis Fett’s site and email offline for eight consecutive days | WLBT |
| During the outage | Fett says he lost orders and consulting work tied to his site | WLBT |
| After the outage | U.S.NEXT’s owner calls Fett, declines to restore service, advises him to find a new host | WLBT |
| October 15, 2026 | WLBT publishes its report; U.S.NEXT does not respond to a request for comment | WLBT |
Eight Days of Downtime, Then a Phone Call
Fett described the experience to WLBT in blunt terms. “I was kind of left hanging here in limbo for eight days, and then the first phone call I get is to tell me they’re not going to provide my web services anymore after 15 plus years,” he said, according to the station’s reporting. That quote captures the core grievance here: it is not just that the outage happened, but that the resolution was a severed relationship rather than a restored one.
“Dead in the Water”
WLBT also reported that Fett described his business as effectively dead in the water until he could find a new home for his website. For a consulting operation that runs on inbound inquiries, even a short gap in visibility can mean missed clients who simply move on to the next search result. Eight days is long enough for that kind of leakage, and a severed host relationship extends the uncertainty indefinitely until a migration is complete.
Signs the Outage Reached Beyond One Client
Fett is the only named, on-the-record customer in the WLBT story, but separate Mississippi local news coverage of the same U.S.NEXT disruption suggests the impact was not limited to one peacock website. Multiple Mississippi municipal and small-business sites reportedly experienced email and web outages tied to the same incident window, pointing to a hosting-infrastructure failure rather than an isolated, single-account problem.
A City’s Bill-Pay Portal Goes Dark
Roy Cox, IT director for the city of West Point, Mississippi, described disruption to his city’s online services during the same period, saying the outage affecting the water and electric department’s ability to let residents pay bills online had been the most problematic issue for the city, and apologizing for the inconvenience. His account, which names U.S.NEXT-linked disruption as the cause, supports the idea that this cyberattack rippled through multiple Mississippi organizations that relied on the same host, not just one hobbyist business.
That broader pattern is unconfirmed in scope and scale, since no public tally of affected U.S.NEXT customers exists yet. But it reframes the story from “a host dropped one angry customer” to “a regional hosting provider had an incident serious enough to disrupt municipal bill payment systems and a global niche business at the same time.”
Why Web Hosts Sometimes Cut Ties After a Breach
From the outside, dropping a 15-year customer right after they were harmed by your own outage looks like the opposite of good service. But hosting providers that suffer intrusions sometimes do exactly this, and the underlying logic, while unpopular with affected customers, is not irrational.
- Rebuilding compromised infrastructure can be cheaper than restoring every account to its prior configuration, especially on older shared-hosting environments.
- Smaller, older accounts are frequently running outdated software stacks that a host does not want to re-expose to the same risk.
- Liability concerns can push a provider toward severing a relationship rather than guaranteeing a security posture it can no longer vouch for.
- Legacy pricing on decade-plus contracts may no longer cover the provider’s actual support and security costs, making a breach a convenient point to exit unprofitable accounts.
None of these explanations were offered by U.S.NEXT, which WLBT says did not respond to requests for comment. That silence leaves Fett, and anyone else affected, without a clear account of why the company chose termination over restoration.
Competitive Comparison: How Hosting Providers Typically Handle Breach Fallout
Industry incident-response norms generally call for three things after a hosting-level breach: a public disclosure of what happened, a restoration timeline for affected customers, and a path for customers to leave gracefully if they choose, including data export support. Judged against that baseline, the U.S.NEXT response as reported stands out mainly for what is missing. There is no public disclosure of the attack’s nature. There is no restoration timeline, because restoration was declined. And the exit path, per Fett’s account, amounted to a phone call telling him to find somewhere else to go.
Larger hosting providers with dedicated security and communications teams tend to treat customer retention after an incident as part of damage control, since a public, one-sided account from an angry customer is reputationally costly. Smaller, regional hosts like U.S.NEXT often lack that infrastructure, which can turn a technical failure into a public relations one almost overnight, as this story illustrates.
How This Incident Compares to 2026’s Other Breach Disclosures
The U.S.NEXT story is small in raw numbers compared to many of the breaches that have made headlines this year, but its direct impact on one named small-business owner is unusually concrete. The table below places it alongside other 2026 breach disclosures by reported scale, for context on how incidents of very different sizes get handled.
| Incident | Reported Scale | Outcome for Those Affected |
|---|---|---|
| U.S.NEXT (Jackson, MS) | At least 1 confirmed client; signs of broader municipal disruption | Client’s hosting terminated after 15 years, no restoration offered |
| UK Legal Aid Agency hack | 250,000+ records, some dating to 1978 | Investigation ongoing, widening scope reported |
| Denmark CPR database breach | 8.8 million people | Weak password implicated in initial access |
| Meta GitHub breach | 1,500 people’s code and data exposed | Disclosed by Meta, scope confirmed |
| Zizzl LLC breach | 519 people, Social Security numbers exposed | Breach disclosed to affected individuals |
The contrast is instructive. Large breaches tend to generate formal disclosure processes, regulatory notices, and credit-monitoring offers, however imperfect. A small regional hosting incident like U.S.NEXT’s can leave an affected customer with essentially none of that, just a phone call and an unanswered media request.
Historical Context: Small Hosts, Outsized Consequences
Hosting-level breaches that ripple into small-business and municipal customers are not new, but they rarely get the same scrutiny as attacks on major platforms. Security researchers have long warned that regional hosting providers, data centers, and managed-service companies represent a soft middle layer of the internet: too small to attract the security investment of hyperscale cloud providers, yet responsible for infrastructure that local governments, nonprofits, and small businesses depend on daily.
A regional incident-response write-up from Vertical Consulting on the same U.S.NEXT disruption underscores how quickly a single infrastructure failure at a regional host can cascade into outages for multiple unrelated organizations that happen to share the same provider. What makes the U.S.NEXT case notable within that pattern is the human specificity of it. Most hosting-breach stories surface as aggregate numbers, records exposed, accounts affected, dollars demanded. This one surfaced because a single business owner picked up the phone, told a local TV reporter what happened, and that reporter published it. It is a reminder that behind every infrastructure failure statistic sits an individual business owner working out how to keep operating.
What the Public Record Shows, and What It Doesn’t
It is worth being precise about the limits of what is known here, both to avoid overstating the story and to flag where follow-up reporting is needed.
- Confirmed: an October 8 cyberattack hit U.S.NEXT and took Fett’s site and email offline for eight days.
- Confirmed: U.S.NEXT’s owner called Fett and declined to restore his hosting after 15-plus years as a customer.
- Confirmed: WLBT reached out to U.S.NEXT for comment and received no response.
- Not confirmed: the attack method, the attackers’ identity, whether a ransom was involved, or whether any customer data was accessed or stolen.
- Not confirmed: the total number of U.S.NEXT customers affected, though separate reporting on disrupted Mississippi municipal services suggests the impact extended beyond Fett alone.
Market Impact for Small-Business Website Owners
For small businesses that rely on a single regional web host, this story is a case study in concentration risk. A business that has used the same provider for 15 years, as Fett had, builds up configuration, email history, and search ranking that is painful to rebuild from scratch. That stability is also exactly what makes a sudden termination so disruptive: there is no backup host on standby, no recent export of email records, and no guarantee the next provider will be any more resilient.
The incident also raises questions for other U.S.NEXT customers who have not yet been contacted. If the company is making case-by-case decisions about which accounts to restore and which to terminate, business owners hosted there have an immediate incentive to back up their own data and confirm their account status rather than wait for a call.
On-the-Record Voices on the Outage
Beyond Fett’s account of the phone call that ended his hosting relationship, he also described the disruption to his email specifically. “So, I have no idea who emailed us, and we’re the lone support around the world when there’s information needed on peacocks,” Fett said, as reported by Yahoo Tech. For a business built on being the only global resource in its niche, losing inbound email for over a week means losing contact with people who may not try reaching out a second time. A separate account from DysruptionHub similarly described the outage as disrupting both websites and email for multiple Mississippi organizations tied to U.S.NEXT, not a single customer’s account in isolation.
Roy Cox, IT director for the city of West Point, Mississippi, offered a municipal-side view of the same type of disruption, saying the outage’s effect on the water and electric department’s online bill-pay system had been the most problematic part of the incident for the city, and apologizing to residents for the inconvenience, according to WLOX’s reporting. Taken together, Fett’s and Cox’s accounts describe a single infrastructure failure landing on two very different kinds of organizations, a global information resource and a municipal utility, within the same window of time.
Predictions: Where the U.S.NEXT Story Goes Next
Several outcomes look likely as this story develops over the coming weeks.
- More affected U.S.NEXT customers, including other Mississippi municipalities or small businesses, are likely to come forward once local coverage spreads, given the Roy Cox account already points to disruption beyond Fett.
- U.S.NEXT faces growing pressure to issue a public statement, especially if additional local outlets or state regulators start asking questions it has so far declined to answer.
- Fett’s case will likely become a reference point for other small businesses negotiating with hosts after an outage, since a named, on-the-record account carries more weight than anonymous complaints.
- Expect renewed attention on how little regulatory protection exists for small-business customers of regional hosting providers, compared to the breach-notification rules that apply to larger data handlers.
- If the underlying cyberattack is confirmed as ransomware or a broader intrusion, affected customers may eventually get a more detailed disclosure than U.S.NEXT has provided so far, likely only after media or legal pressure mounts.
What to Do If Your Host Drops You After a Breach
Fett’s situation offers a practical lesson for any small-business owner relying on a single hosting provider. A few steps can reduce the damage if the same thing happens to you.
- Keep an independent, current backup of your website files and database, not just a copy stored with your host.
- Export your email contact list and recent messages periodically, so a sudden loss of access does not sever customer communication entirely.
- Register your domain name with a separate registrar from your hosting provider, so you retain control of it regardless of what happens to your hosting account.
- Ask your host directly, before any incident, what its breach notification and restoration policy actually is.
- If you are told to leave, request your data export in writing and get a specific timeline for when your site can be considered fully migrated.
Frequently Asked Questions
What happened to Dennis Fett’s website?
His website and email, hosted by U.S.NEXT in Jackson, Mississippi, went offline for eight days following an October 8, 2026 cyberattack. U.S.NEXT’s owner later told him the company would not continue hosting his site after more than 15 years as a customer.
What is U.S.NEXT?
U.S.NEXT is a web hosting company based in Jackson, Mississippi. Beyond its role in this incident, WLBT’s reporting does not detail the company’s size, client base, or ownership structure, and U.S.NEXT has not publicly responded to requests for comment.
What kind of business did Dennis Fett run?
WLBT describes it as a global peacock information center, a 30-year-old business that Fett said generates orders and consulting work through its website.
Was Dennis Fett the only customer affected by the U.S.NEXT cyberattack?
That is not confirmed. WLBT’s report names Fett as one confirmed case, but separate Mississippi coverage describes disruption to a city government’s online bill-pay services during the same period, suggesting other U.S.NEXT customers may have been affected too.
Has U.S.NEXT explained what caused the cyberattack?
No. WLBT reported that U.S.NEXT did not respond to its request for an explanation about the outage. The attack method, perpetrators, and whether any data was accessed remain unconfirmed publicly.
Can a web host legally drop a customer after a breach?
Generally yes, subject to the terms of the customer’s hosting contract. Hosting agreements typically allow either party to terminate service, though the lack of a restoration timeline or data-export support in a case like this can still generate significant reputational and customer-relations fallout for the provider.
What should small businesses do to protect themselves from a similar situation?
Maintain independent backups of website files, databases, and email records, keep domain registration separate from hosting, and ask any hosting provider in advance what its breach-response and account-restoration policy looks like.
Where was this story first reported?
WLBT’s 3 On Your Side consumer desk in Jackson, Mississippi, published the initial account on October 15, 2026, with wire and syndication pickup following from outlets including Yahoo Tech and others.