Monday, April 20, 2026
[Transparency Report #001][UPSTREAM CONTACT][EXT CONTACT] SSL based abuse complaint?
What are Transparency Reports?
As a community operated and governed virtual internet exchange, FurrIX has
to maintain and foster open and honest communication with our exchange
members. This means that from time to time, there will be items that come
up during our operations that could or do affect the exchange and our team
will publish notices in order to keep everyone in the know. As a community
internet exchange, FurrIX aims to have fully open communication standards
as best as possible.
What Happened?
Today at 1610EST, we received notification of an abuse complain from the data
center that FurrIX’s network is hosted within. Upon logging in to their customer
portal, we were greeted with an email to their abuse department specifying a
notice about SSL certs expiring on our primary web host. Oddly enough, this
email list a phone number from another state and a link to the KCPD website.
We are also verifying whether the external contact was legitimate through a bit
of research and external guidance, as we have been told that fusion centers
typically do not issue SSL‑expiry notices and we have not seen this interaction
before.
Honestly, this seems off and like a bogus report, but the FurrIX vIX did respond
with the following information:
- Our SSL certs are manually updated by hand and not automated
- The domain in question has been renewed before the email arrived
because of DoH and DoT requirements
What this means for members of the exchange:
- FurrIX RX’d a fishy looking abuse complaint
- FurrIX is reaching out to our datacenter for assistance
Are exchange operations affected?
At this time, we do not expect our exchange operations to be affected in
any meaningful way and will be keeping an eye on the situation. We will post
updates to this page as we gain more information. Something to keep in the
back of our member’s mind, for clarity, is that SSL certificate expiration is not
considered an abuse category under our network‑operations practice and that
we do run into SSL issues here and there due to the human operator stance
of the vIX. Members do not need to worry about this, we will get certs renewed
ASAP and we have internal alerting just for this.
Report Status: Worked with data center to mark issue as resolved.
Saturday, March 28, 2026
Ongoing Name Server Attacks
FurrIX is seeing attacks on our name servers that have not let
up for a few hours now and as a result we have had to tighten
our rate limits and start dropping excessive traffic.
The way things are going, we will not be letting up on our rate
limits any time soon.
If you are being affected by these changes, you can send an
email off to ‘nameservers at marbledfennec dot net’ and request
a whitelisting that will bypass the limits. We will require knowing
you use case, however.
Wednesday, March 25, 2026
Agreement Reached with MFN
We’ve been working on our agreement with Marbled Fennec Networks
in the background and have reached what we deem to be an acceptable
way of moving forward and ensuring the survival of both projects, as
well as allowing us both to do our own thing on the same hardware.
This new version is what is being used to govern interactions and
responsibilities between both of our projects as of March 25th, 2026.
You can review the agreement at:
This page…
Tuesday, March 24, 2026
[Incident Report #031][NET] Connectivity Issues with 2602:F992:EC::/46
Update:
Appears our static route did not get migrated to the new hardware
at the data center. This has been resolved and our services should
be back online momentarily!
What Happened?
Our upstream provider performed some upkeep on the data center on
Mar 20th and since then our routed subnet has not be working properly.
We are looking into this as it affect our IPAM, NMS, PBS and a few other
services that assist us with managing our network.
This is also affects our secondary name server, as it currently does not
have IPv6 service.
We are seeing the following issues:
- No IPv6 connectivity for NS2, affecting private and public resolution request
- No PBS backups for either MFN, FurrIX or Maows.Gay
- No NMS accounting or error tracking
- No status graphs on our website are updating
What are we doing to work on this?
- We have performed internal and external networking checks
- We have reached out to our upstream provider with our findings
At the moment, we will have to wait to hear back from the data center.
Sunday, February 22, 2026
Releasing Domains and Ongoing Amplification Attacks
FurrIX has chosen not to renew the domains ‘birb.rest’ and ‘avali.rest’ for cost reasons.
These domains are not a core part of our network stack and were only used for personal
splash pages and a handful of user subdomains that have not seen lookups in some time.
This should not affect our operations, or that our members, in any meaningful way.
We are also dealing with a DNS amplification attack that is abusing ANY queries and will be
temporarily dropping any IP address that cross over 40 request per second until the incoming
traffic targeting the domains starts to ease up. This has been going on for several hours and
we are working to limit the amount of traffic crossing or originating from our network.