Resolved Network Interruption ACS 1/20/2026

[KH-DanielP]

We experienced a brief service interruption tonight and sincerely apologize for the disruption.

TL;DR: An upstream link began causing routing issues affecting parts of Asia and Australia. While deprioritizing that link to shift traffic elsewhere, the core routing stack reacted unexpectedly, resulting in a short outage.

This should not have occurred. We transitioned to emergency access and restored service as quickly as possible. Think of it like turning a faucet and having a pipe burst unexpected, fast, and disruptive, but contained and resolved.

All services are stable at this time.

 

[JasonW]

**Update: It is back online ... not sure if it was related or not, but it stopped responding not long after the other servers went offline.

I think this may still be an ongoing issue. I have at least one down right now.

 

[Shawn-09]

Hi Mr. Pearson,
First, we're a new (1 month) customer. So far, we are very pleased, and love your support team.
But, I feel compelled to offer a friendly suggestion:
Move this forum to a subdomain (ex: forums dot knownhost dot com) , hosted elsewhere, with separate name servers, and
, when an incident occurs, take one minute to create a post saying: "we see a problem with ___ , we're aware, and investigating."

It would save both Knownhost Support, and your users a lot of time:
- time spent testing our own networks, ISP, Internet.
- opening tickets after concluding, yes, it might be a knownhost issue.
- Support having to respond to said tickets.

Anyone who's been around a bit knows, every host experiences some issues.
For me, and I would argue, for the customers you most want as customers, transparency is a selling point.
For a great example check out fastmailstatus dot com.