The FXNet Routing Committee oversees the network topology, server links, and ensures stable, low-latency connectivity across all nodes.

The committee is responsible for:

• > Reviewing and approving new server link applications
• > Determining optimal network topology and hub assignments
• > Monitoring server performance and connectivity
• > Initiating delinks when servers fail to meet requirements
• > Mediating disputes between server administrators
• > Maintaining and updating this routing document

committee members

• [RC] Position open - apply if interested

Committee membership requires active participation and a linked server in good standing for 90+ days.

All servers wishing to link to FXNet must meet the following minimum requirements:

hardware & connectivity

BANDWIDTH ........ 100 Mbps minimum (unmetered preferred)
UPTIME ........... 95% minimum availability
LATENCY .......... <150ms to nearest hub
CONNECTION ....... Dedicated or VPS with static IP
IPV6 ............. Recommended but not required
            

software & security

IRCD ............. InspIRCd 3.x or 4.x (current stable)
TLS .............. Required for server-to-server links
CERTIFICATE ...... Valid TLS cert (Let's Encrypt accepted)
SERVICES ......... Must link to network Anope services
OS ............... Maintained, security-patched system
            

administrative

CONTACT .......... Responsive admin with valid email
RESPONSE TIME .... 48 hours maximum for critical issues
LOCATION ......... Physical server location must be disclosed
LEGAL ............ Must comply with local laws
LOGGING .......... No user message logging permitted
            

applying to link

1. JOIN #fxnet and speak with a network operator
2. SUBMIT application with the following:
   - Server hostname and IP
   - Physical location (city, country)
   - Hardware specs and bandwidth
   - Admin contact information
   - Reason for wanting to link
3. WAIT for committee review (typically 7-14 days)
4. TEST link to designated hub server
5. PROBATION period of 30 days
6. FULL link status granted after successful probation
            

probationary period

New servers are linked in probationary status for 30 days. During this time:

• > Server will be monitored for stability and uptime
• > Admin responsiveness will be evaluated
• > Link may be terminated without full committee vote
• > Server admin has no voting rights on network matters

delink procedure

VOLUNTARY DELINK:
  - Notify committee 7 days in advance when possible
  - Coordinate timing to minimize user disruption
  - Return any network credentials/keys

INVOLUNTARY DELINK:
  1. Issue documented to server admin
  2. 72 hours to respond/remediate (except emergencies)
  3. Committee vote (majority required)
  4. Delink executed with notice to network

EMERGENCY DELINK (immediate, no vote required):
  - Server compromised or actively harmful
  - Severe network disruption
  - Legal/law enforcement issues
  - Committee review within 48 hours post-delink
            

current structure

                    [ FXNet Network Map ]

                        core.fxnet.org
                        Ontario, Canada
                             [HUB]
                               |
                      (future links here)
            

topology guidelines

• > Hub servers must meet enhanced requirements (99% uptime, dedicated hardware)
• > Leaf servers connect to geographically optimal hub
• > Maximum 2 hops between any two servers
• > Redundant hub links where possible
• > Geographic diversity prioritized for resilience

hub requirements

Hub status is granted by committee vote and requires:

UPTIME ........... 99% minimum
BANDWIDTH ........ 1 Gbps minimum
HARDWARE ......... Dedicated server (no VPS)
TENURE ........... 6 months as stable leaf server
ADMIN ............ Proven track record, responsive
            

To apply for a server link or contact the routing committee:

• IRC /join #fxnet on irc.fxnet.org
• EMAIL routing [at] fxnet.org