Sales (888) 902-8232 Support (307) 902-8233 Help & FAQ

Network management practices disclosure

Last revised 1 March 2026. Published by Net Inc. under the FCC's transparency rule. Written to be read rather than to be filed.

Summary

We do not cap data, we do not slow you down for using a lot of it, and we do not block, throttle or prioritise any application, protocol, service or website in exchange for payment. The only traffic management we perform is a queueing policy that runs during genuine congestion, applies to all customers on a link equally, and is described in full below.

1. Blocking

We do not block lawful content, applications, services or non-harmful devices.

Two exceptions, both narrow and both security measures rather than commercial ones:

  • Outbound TCP port 25 is blocked by default on residential connections, to stop compromised machines sending spam. We unblock it on request for any customer who asks.
  • Traffic identified as an active attack — a flood originating from a compromised device on a customer's line — may be filtered while the customer fixes it. We contact the customer, and we filter the specific traffic rather than disconnect the service. See the acceptable use policy.

We do not operate a filtered DNS resolver, do not redirect failed lookups to a search page, and do not intercept traffic to insert content of any kind.

2. Throttling

We do not throttle. There is no data cap, no soft cap, no monthly threshold past which your service is slowed, and no per-application rate limiting. A customer who transfers ten terabytes in a month is treated exactly as one who transfers ten gigabytes, and neither will hear from us about it.

Your connection is provisioned at the plan speed. That is a rate limit in the sense that every plan is, and it is the number printed on your bill.

3. Affiliated and paid prioritisation

We do not engage in either. No content provider pays us for preferential treatment, we do not favour our own services over anyone else's, and we do not exempt anything from any allowance — because there is no allowance to be exempted from.

4. Congestion management

Links occasionally carry more traffic than they can pass. When that happens on one of ours, this is what runs:

  • It is triggered by the link, not by the customer. The policy activates on an interface carrying sustained utilisation above 90% for more than five minutes. It applies to every customer on that interface identically.
  • It sorts by protocol class, not by identity. Four classes: network control, then real-time interactive traffic (voice, video calls, gaming), then general interactive traffic (web, email, streaming), then bulk transfer (large downloads, backups, updates, peer-to-peer file transfer). Under congestion the lower classes yield to the higher ones.
  • Classes are assigned by traffic behaviour and DSCP marking, not by inspecting content. We do not look at what you are sending. Encrypted traffic is classified by its shape, exactly like everything else, and is never penalised for being encrypted.
  • Bulk transfer is delayed, never dropped or capped. A large download slows for the duration of the congestion and returns to full rate afterwards. Nothing is disconnected and no charge results.
  • It stops when the congestion stops. Typically within minutes. There is no penalty period and nothing carries over.
  • No customer is singled out. There is no per-subscriber quota, no heavy-user register and no account flag that survives the event.

Congestion is a symptom of a link needing more capacity, and we treat it as an engineering problem rather than a customer problem. Any interface exceeding 70% peak utilisation for three consecutive months enters our upgrade plan. We will tell you the current utilisation of the fiber node, exchange or wireless sector serving you if you ask.

5. Expected performance

Typical performance by technology, measured to our network edge
Technology Speed against plan Latency Packet loss Contention
Fiber 95–100% of plan at peak 3–8 ms Under 0.1% Dedicated to the node
Fixed wireless 80–100% of plan at peak 15–35 ms Under 0.5% Engineered to 4:1 per sector
DSL Provisioned at the tested line rate 25–60 ms Under 1% Dedicated to the pair

Measured between your equipment and our edge router, hourly, from customer premises equipment across all three networks. Performance beyond our edge depends on the wider internet and on the service you are reaching, and we neither control nor claim it.

Things that legitimately reduce what you see

  • Wi-Fi, which is the single most common cause. Test wired before concluding the connection is at fault.
  • Weather on fixed wireless — heavy rain and wet snow reduce throughput on the highest tiers, though the link stays up.
  • Line length on DSL. We provision at what the pair tests, which is why DSL plans are sold after a line test rather than before.
  • Your own equipment. A gigabit plan through a 100 Mbps switch port delivers 100 Mbps, and it is not the circuit's fault.

6. Impact of non-broadband services

NET Digital Voice runs over the same access line and is placed in the real-time class. A concurrent telephone call consumes roughly 100 kbps in each direction — negligible against any plan we sell, and it does not reduce your provisioned speed. Voice is not exempt from any data allowance, because there is none.

7. Security

We filter traffic at the network edge only in these cases: spoofed source addresses (BCP 38 ingress filtering), routes we know to be hijacked, and active attack traffic as described above. We run no content filter, no age filter, no parental control at the network and no man-in-the-middle inspection. If you want filtering in your home, run it on your own router — we will help you configure it.

8. Commercial terms

Prices and fees
Published in full on the internet and business pages. There is no fee we can charge that is not listed there
Privacy
See the privacy policy. We do not sell or broker customer data
Redress
Support on (307) 902-8233, or write to the office. Complaints unresolved after fourteen days are escalated to a company officer
Regulatory complaint
You may complain to the FCC at fcc.gov/complaints, to your state consumer protection authority, or — in the United Kingdom and Europe — to Ofcom or your national regulator

9. Changes to this disclosure

Material changes are notified to customers by email at least thirty days before they take effect, and the revision date at the top of this page changes. Previous versions are available on request.


Related: terms of service · privacy policy · acceptable use policy · broadband facts