Skip to main content
Cathrix Network

Abuse Report

How to Report Abuse Involving Cathrix

This page explains how to submit an actionable report concerning suspected abuse that originates from, is hosted on, is routed through, or otherwise involves services operated by Cathrix Network Inc. (“Cathrix,” “we,” “us,” or “our”).

Abuse includes suspected unlawful activity, security threats, and activity prohibited under our General Terms of Service. As an infrastructure provider, Cathrix may not own the reported content or control the person responsible for it.

Caution

If there is an imminent risk of death, serious physical harm, or another emergency, contact local emergency services or law enforcement first. Email must not be relied upon as a real-time emergency channel.

1. How and Where to Report

1.1 Contact Channels

Please direct your reports to the appropriate channel to ensure prompt routing:

  • Network Abuse: For spam, malware, phishing, and IP or resource abuse, email [email protected].
  • Routing Incidents: For live BGP routing, reachability, or peering incidents, email [email protected].
  • Customer Support: For existing customers requesting remediation assistance, email [email protected].

Please use the following subject line format:
[Abuse Report] <Category> - <IP, domain, or resource> - <YYYY-MM-DD>

1.2 Required Information

To allow us to attribute, verify, and reproduce the activity, every report must include:

  • Reporter Information: your name, organization, role, and contact email.
  • Reported Resource: the exact IP address, autonomous system number (ASN), hostname, or complete URL.
  • Precise Timestamp: the exact date and time (ISO 8601 in UTC preferred, e.g., 2026-07-19T00:33:32Z) when the activity occurred.
  • Evidence: plain text logs, headers, routing observations, or safe hashes.

Do not send live malware samples, executable files, or illegal content. Redact passwords and sensitive personal information from your logs.

2. Category-Specific Guidelines

2.1 Network and Routing Abuse

For scanning, denial-of-service (DoS) attacks, prefix hijacks, or route leaks, you must include source and destination IPs, relevant ports, protocols, the affected AS path, and RPKI status where applicable. Please distinguish a suspected hijack from a route leak or normal upstream-path change.

2.2 Spam, Malware, and Phishing

Provide complete original email headers (including all Received lines), landing-page URLs, and a concise description of the deceptive behaviour. Screenshots are helpful but cannot replace machine-readable text logs.

2.3 Intellectual Property and Rights Complaints

To report copyright or trademark infringement, your notice must include:

  • the rights holder’s legal name and your authority to act;
  • a specific description of the protected work;
  • the exact URL of the allegedly infringing item (do not submit blanket requests for entire domains);
  • a good-faith statement that the use is unauthorized; and
  • your physical or valid electronic signature.

3. Report Handling and Remediation

3.1 Investigation and Actions

Upon receiving an actionable report, Cathrix will assess the evidence. Depending on the severity and contractual terms, Cathrix may:

  • forward the report to the responsible customer for remediation;
  • require content removal or credential resets;
  • apply filtering, rate-limiting, null-routing, or isolation to the affected traffic; or
  • suspend or terminate the affected account or service.

3.2 Confidentiality and Disclosure

Reports are not guaranteed to be anonymous. To resolve an incident, Cathrix may share relevant portions of your report (including evidence and contact information) with the affected customer, upstream providers, or competent authorities as permitted by our Privacy Policy.

3.3 Response Times and Service Levels

Cathrix reviews all reports, but we do not guarantee specific response times or outcomes for third-party abuse reports. Acknowledgment of receipt does not confirm the validity of the allegation. Abuse ticket processing is exempt from any applicable customer Service Level Agreement.

4. Customer Obligations

4.1 Responding to Notices

If you are a Cathrix customer and receive an abuse notice from us, you must:

  • reply to the existing ticket thread promptly;
  • contain any continuing harm immediately;
  • identify the root cause and provide a concrete completion time for remediation; and
  • provide technical evidence if you believe the report is misattributed or false.

Failure to respond or incomplete remediation may result in network restrictions or account suspension.

4.2 Requesting a Review

An affected customer may appeal a restriction by replying to the notice with factual technical evidence proving the action was mistaken, along with details of safeguards implemented against recurrence. Urgent protective measures will remain in place during the review.

5.1 Misuse of the Reporting Process

Do not submit knowingly false allegations, forged authorizations, or malicious attachments. Cathrix may filter, reject, or block senders who repeatedly misuse the abuse reporting channel.

An ordinary email to our abuse addresses does not constitute formal service of a subpoena, warrant, or court order. Law enforcement agencies and legal representatives must submit formal legal demands in accordance with applicable Alberta and Canadian law. Submitting a demand via email does not waive any legal objections or constitute acceptance of service.

Last Updated on August 26, 2026

Effective as of August 26, 2026