Wednesday, July 15, 2026
[Incident Report #036][DC] Network Cabling Issues….
What are Incident Response Reports?
As a community‑operated and governed virtual internet exchange, FurrIX maintains
a commitment to open and honest communication with its members. During the normal
operations of the exchange, our network and its supporting systems may encounter
operational defects, bugs, failed changes or attacks on our infrastructure. When this
happens, the FurrIX volunteers publish an incident response report to ensure all members
and peers remain informed as to what happened, how it went down and what we did to
recover or resolve the issue. As a hobbyist‑rooted vIX, we aim to keep communication clear,
accessible and practical to the best of our ability.
What Happened?
On July 14th, 2026 at around 2045EST, the FurrIX vIX went offline for about thirty-five
minutes. The volunteers at FurrIX reached out to the data center for some insight after
doing our own troubleshooting. It was discovered that our secondary server was still
alive but our primary had no response.
We were seeing the following issues:
- vIX reachability — The virtual exchange was temporarily in a degraded state.
- NS1 Failure — Members were relying on NS2’s zone cache temporarily.
- MA BGP Failures — Our BGP sessions with members temporarily failed.
- Web/email Failures - These services stopped responding.
- Games-3P Failure - Game services went offline.
What did we do to fix this?
We contacted the data center to determine the scope of the event and were informed
that the techs at the upstream data center had found a loose network cable and that
was the cause of our server going offline. They have reseated the cable and the exchange
is now back online and services are reachable once again.
As of this post, all FurrIX vIX services have recovered.