Skip to main content
Trellis Internet

DRAFT — Pending attorney review

This document is a working draft prepared by Trellis Internet staff for review by counsel. It is not a final policy and should not be relied upon as a binding agreement until it is published in non-draft form.

Network Management Disclosure

Last updated:

This disclosure describes the network management practices, performance characteristics, and commercial terms of Trellis Internet’s broadband service. It is published pursuant to the FCC’s transparency rule at 47 C.F.R. § 8.1 and the California Internet Consumer Protection and Net Neutrality Act of 2018 (SB 822).

1. Overview

Trellis Internet (“Trellis”) is a fixed wireless internet service provider serving Sonoma and Napa Counties, California. We operate a licensed and unlicensed wireless access network with fiber backhaul. This page tells you how we manage that network, what performance you can expect, and what the service costs.

Trellis does not block lawful content, applications, services, or non-harmful devices. Trellis does not throttle lawful traffic on the basis of application, content, source, or destination. Trellis does not engage in paid prioritization. Trellis does not enter into zero-rating arrangements that favor specific edge providers. Reasonable network management practices used to maintain the security and reliability of the network are described in the sections below.

2. Network Management Practices

We deploy the following operational practices to keep the network reliable, secure, and fair for every customer:

  • Capacity planning: We monitor utilization at each access point, backhaul link, and upstream peering point. When sustained utilization approaches engineered capacity, we add capacity (additional radios, channels, or backhaul) rather than throttle.
  • Outage and incident response: We monitor link quality, signal levels, and equipment health on a 24x7 basis. We publish status updates for incidents that affect more than a single customer.
  • Configuration management: Customer-premise equipment is provisioned with standard, documented configurations. We do not block specific ports or protocols on customer connections except as described in Section 5.

3. Congestion Management

Trellis does not currently use protocol-specific or application-specific congestion controls. When transient congestion occurs at an access point, individual customer throughput may be reduced in proportion to overall demand, but no customer’s traffic is preferentially throttled relative to another customer’s on the same access point.

When sustained congestion is observed, we either (i) add capacity to the affected segment, or (ii) work with affected customers to relocate them to a less-loaded access point if line-of-sight allows. We do not bill customers for “congestion-clearing” services or sell prioritization on residential plans.

4. Application-Specific Behavior

Trellis does not inspect, manipulate, or rewrite the content of customer traffic. We do not interfere with video streaming, file-sharing, gaming, voice-over-IP, or any other lawful application. We do not require special agreements with edge providers as a condition of customers reaching them.

We do not block any specific TCP or UDP ports for residential customers by default. Customers running services that require inbound connectivity should ensure they comply with our Acceptable Use Policy (in particular, residential plans are not intended for high-traffic commercial services).

5. Security Practices

To protect customers and the network, we maintain the following security practices:

  • Spoofing protection: We perform source-address validation (BCP 38 / RFC 2827) to prevent customers from sending traffic with forged source IP addresses. This is a widely deployed anti-abuse practice and does not affect legitimate traffic.
  • DDoS mitigation: We deploy automated scrubbing for large-scale denial-of-service attacks targeting customers or our infrastructure. Mitigation does not inspect packet contents and is engaged only during active attack.
  • Compromised-device handling: When we identify a customer device participating in a botnet or actively attacking other networks, we contact the customer and may temporarily quarantine the device until it is remediated.
  • Abuse reports: We respond to abuse complaints submitted to abuse@trellisinternet.com and copyright notices submitted under the DMCA per our Acceptable Use Policy.

6. Performance Characteristics

Each Trellis plan publishes a typical download speed, typical upload speed, and typical round-trip latency on the FCC Broadband Facts label that accompanies the plan. Speeds shown on the labels are not guarantees; actual performance depends on line-of-sight, weather, in-home wiring, customer equipment, and conditions on the broader internet beyond Trellis’s control.

Trellis measures performance using:

  • Continuous synthetic testing from access points to representative internet destinations.
  • Periodic on-customer-premise speed tests, anonymized and aggregated.
  • Public reference servers operated by Measurement Lab (M-Lab) and equivalent neutral test infrastructure.

The Broadband Facts labels are available on every plan page and a machine-readable copy is hosted at /fcc/labels.csv for compliance with FCC requirements.

7. Commercial Terms

7.1 Pricing

Monthly service prices are published on the Plans page and itemized on the corresponding Broadband Facts label. Mandatory one-time fees, including standard installation, are disclosed at the time of sale. Taxes and government fees vary by location and are itemized on each invoice.

7.2 Service term

Residential plans are offered on a month-to-month basis. There are no required service contracts and no early-termination fees for residential customers. Business plans may have different terms, which are disclosed at the time of sale.

7.3 Data allowance

All Trellis residential plans include unlimited monthly data. There are no overage charges. If the FCC’s definition of a data allowance changes or if we introduce metered plans, this disclosure will be updated to reflect the change.

7.4 Equipment

The wireless receiver and indoor router used to deliver Trellis service are owned by Trellis and provided to you as part of the service. If service is terminated, the equipment must be returned or a non-return fee may apply. Customers may, with our prior approval, use their own router behind the Trellis equipment.

7.5 Privacy policy

Customer information is handled in accordance with our Privacy Policy.

8. California Net Neutrality (SB 822)

Trellis operates in compliance with the California Internet Consumer Protection and Net Neutrality Act of 2018 (Cal. Civ. Code §§ 3100–3104). Specifically, we do not:

  • Block lawful internet content, applications, services, or non-harmful devices.
  • Impair or degrade lawful internet traffic on the basis of content, application, service, or use of a non-harmful device.
  • Engage in paid prioritization (preferential treatment of traffic in exchange for consideration, monetary or otherwise).
  • Unreasonably interfere with or unreasonably disadvantage end users’ ability to select, access, and use broadband, or edge providers’ ability to make lawful content, applications, services, or devices available to end users.
  • Engage in zero-rating arrangements that exempt specific edge providers from a data allowance. (As stated above, our plans do not have data allowances.)

9. Privacy of Customer Information

See the Trellis Privacy Policy for a full description of how we collect, use, share, and protect customer information, including Customer Proprietary Network Information (CPNI) under FCC rules.

10. Complaints and FCC Process

We try to resolve every customer concern directly. If you believe an issue has not been resolved to your satisfaction, you may file an informal complaint with the FCC at consumercomplaints.fcc.gov or with the California Public Utilities Commission at cpuc.ca.gov/complaints. Filing with the FCC or CPUC does not waive any other rights you may have under law.

11. Changes to This Disclosure

We update this disclosure when our practices materially change. The “Last updated” date at the top of the page reflects the most recent revision. We retain prior versions of this disclosure on request.

12. Contact

Questions about this disclosure or about our network management practices: