FAQ

AS30265 is a Canadian ISP providing Residential Connectivity, IDC Connectivity, and Tunnel Connectivity. Our network supports IPv6, direct peering, and flexible routing for homes, businesses, and network operators.

We offer Residential Connectivity for premises, IDC Connectivity through physical ports in our facilities, and Tunnel Connectivity over an existing Internet connection. We also provide Wholesale services for ISPs.

The service model is the same. IDC Connectivity, Residential Connectivity, and Tunnel Connectivity are all ways to reach the same network, with the same overall philosophy around IPv6, addressing, routing, and optional BGP sessions.

The main difference is the handoff. IDC Connectivity gives you a port in a facility, Tunnel Connectivity gives you a remote overlay, and Residential Connectivity gives you the same core service over a wholesale FTTP last-mile.

Subscribers receive a permanent IPv6 Allocation, service configuration and visibility through the Subscriber Portal, and the ability to use their own router. Our network combines direct peering with managed routing policies, and optional BGP sessions provide additional control for subscribers who operate their own network.

Subscribers with their own ASN and IP Prefixes can use Bring-your-own-IP (BYOIP) and establish a BGP session. Both address families are carried over a single IPv6 session. Without a BGP session, SLAAC routes your IPv6 and IPv4 Prefixes to your Access Methods. A BYOIP Allocation must be internet eligible. Connection Profiles in the Subscriber Portal let you manage routing configuration as your requirements develop. See the Advanced guide for setup details.

We use direct peering, routing policies, and infrastructure planning to improve paths to other networks. Direct connections to major services can reduce latency and unnecessary hops. Performance varies by destination and network conditions.

Our services support homes, businesses, and network operators that value control over addressing, routing, and equipment. Subscribers configure their own router using our guides. BGP knowledge is only needed when using BGP features.

We do not offer seasonal or introductory promotions. Published rates apply throughout the year. See Residential Connectivity pricing for current charges.

Your connection uses the provisioned Bandwidth of the wholesale access profile without an additional speed cap from AS30265. Pricing reflects wholesale access and network capacity costs.

The Bandwidth shown on your Access Method is a burst ceiling, not a guaranteed sustained throughput. See our fair use policy for how capacity is shared.

Residential throughput depends on three separate segments, and each segment is run by a different part of the ecosystem.

flowchart TB
  A[Home router] -->|Segment 1: Access loop| B[Incumbent CO or aggregation edge]
  B -->|Segment 2: Regional aggregation| C[AS30265 edge router]
  C -->|Segment 3: Peers and upstream transit| D[Public Internet]

Segment 1 is the access loop from your premises to the incumbent network edge. This is where the wholesale access profile is provisioned; it is the Bandwidth shown on your Access Method.

Segment 2 is the incumbent aggregation domain that carries many subscribers across the region to our interconnection handoff. This is the most expensive part where capacity-based billing lives.

Segment 3 is our own external connectivity to other networks through peering and upstream transit.

A single speed test usually traverses all three segments, so the result reflects the narrowest point on that end-to-end path at that moment.

Almost always because of the port it leaves your home through. Most routers have a 1 GbE WAN port, so nothing beyond about 1 Gbps can reach the test however wide the access is, and a speed test that opens a single stream rarely fills more than that on its own.

About 1 Gbps on GPON or XGS-PON is a normal result and not a fault. To see past it you need a router with a WAN port faster than 1 GbE, a test that opens several streams, and a test server able to serve them.

No. The access loop is a PON: the premises served by the same fibre share its capacity, and the wholesale provider operates and dimensions it. The provisioned Bandwidth is the widest burst the access technology can carry, not a rate reserved for you, and when the PON or the aggregation behind it is busy your throughput falls. AS30265 cannot lift it, because that segment is not ours to run.

It costs you nothing when it happens. We charge on the traffic your Access Method actually carried, through its p95 and its Mean Bandwidth, and never on the Bandwidth provisioned for it. Congestion cannot raise your bill. Every FTTP Access Method is billed on at least 1 Gbps of billable Bandwidth, and above that floor carrying less means paying less.

Compare the ongoing monthly price, installation charges, equipment requirements, contract terms, addressing, and routing features. AS30265 provides service month to month without a required term contract or introductory pricing. Our pricing page lists the applicable charges.

Building agreements may include different pricing, equipment, and service terms. AS30265 Residential Connectivity includes a permanent IPv6 Allocation, service management through the Subscriber Portal, and support for your own equipment. Compare those features and the full ongoing cost against your building's offer. Our pricing page provides a breakdown.

Installation charges reflect the applicable wholesale tariff. AS30265 applies a $120 credit to FTTP installations that require a technician visit. See pricing and billing details for the charges and credit terms.

No. You would have to try.

The multiplier only moves once your Mean Bandwidth passes the reference Load Factor, which is 5% of your Measured Bandwidth, so for a household that is roughly 50 Mbps sustained, about 16 TB a month, every month. Three 4K streams running six hours a day is about 19 Mbps. Four smart home cameras uploading continuously is about 8 Mbps. A house doing both, all day, every day, is still nowhere near.

What does reach it is traffic that never stops:

• seeding around the clock, which is the common one and is deliberate
• running something public from home, such as a relay, a public mirror or a blockchain node, which scales with strangers' demand rather than yours
• routing other people out through your line, as a VPN or tunnel egress
• a sync or backup job that never finishes, because a client is misconfigured and re-uploading the same data for ever
• a device that has been compromised and is sending continuously

The last two nobody chooses. If your Access Method starts sustaining traffic it has not before, we would rather tell you than bill you for it.

What you buy is a share of capacity: the wholesale aggregation that carries your traffic to our edge, and our own connectivity beyond it. A burst borrows capacity that other subscribers are not using at that instant. Sustained traffic reserves it.

Two Access Methods behind the same provisioned Bandwidth can differ manyfold in the capacity they oblige us to hold. Your p95 cannot tell them apart, because it sets aside the busiest 5% of records and says nothing about the other 95%. Your Mean Bandwidth is the figure that does, and your Load Factor is the two compared.

They do. You just never see it as a line on the invoice.

Every provider faces the same arithmetic, because the cost of a shared capacity pool moves with sustained traffic rather than with a headline speed. What differs is where that cost is put:

• selling the same capacity many times over, and accepting that evenings run slower
• an "excessive use" clause in the acceptable use policy, invoked case by case
• a data cap with overage, which is billed on how many bytes moved rather than on when they moved

Each of those is the cost of sustained traffic, collected in service quality or in a clause instead of in a number. We put it in a number, and wherever we can we tell you before that number changes what you pay.

If your traffic is bursty, which nearly all residential traffic is, you pay less here than under a flat rate, because a flat rate has to price in the heaviest subscriber on the segment.

Yes, and we could advertise it that way. There is no byte cap, no overage, and no throttling. Nothing about the service you receive changes with how much you move.

We do not lead with the word because it carries almost no information. "Unlimited" constrains bytes, and bytes were never the scarce thing; capacity at a moment in time is. Two providers can both say "unlimited" and mean opposite things by it.

What actually differs is which of the two is allowed to vary. On a flat-rate unlimited service the price is fixed and the service varies, so the evening slows or a clause appears. Here the service is fixed and the price varies with the capacity you hold.

Yes, on FTTP, at the same 5% whichever access technology carries it. FTTN is flat-rate. How billable Bandwidth is charged sets both services out side by side.

The reference Load Factor on FTTP is lower than the one on IDC Connectivity because a substantial share of what you pay goes to the wholesale provider for the access loop and the aggregation behind it, so a Residential Access Method carries far more cost than an IDC one before any of our own capacity is counted. On an FTTP invoice that share is not buried in the rate: Wholesale Access is the tariff for your loop, Capacity covers the aggregation behind it, and both are listed separately from the Service Fee.

Set one IDC Connectivity Access Method on a 10 Gbps optic beside an illustrative flat-rate port of the same width at $1,500 a month. IDC Connectivity charges $120.00 for each Gbps of billable Bandwidth, and your billable Bandwidth is your Measured Bandwidth multiplied by your Load Factor divided by 25%, rounded up to a whole number. Hold the Measured Bandwidth at 10 Gbps and walk the Load Factor upward.

Up to a 25% Load Factor your Measured Bandwidth sets the charge, and $1,200 sits $300 under the flat figure. Past 25% the multiplier rises to 2 and the charge to $2,400, and an Access Method held at 10 Gbps right across the Measurement Period reaches $4,800, which is 3.2 times the flat figure. That factor of 3.2 measures capacity, and the entries below work through it.

The charge is $120.00 multiplied by your Measured Bandwidth and by your multiplier, which is your Load Factor divided by 25%, rounded up to a whole number. Your Load Factor multiplied by your Measured Bandwidth is your Mean Bandwidth by definition, so at a Load Factor of exactly 25%, 50%, 75% or 100% the charge works out to $120.00 multiplied by four: $480 for each Gbps of Mean Bandwidth.

Between those points the multiplier has already stepped up, so each Gbps of Mean Bandwidth costs more. On a 10 Gbps Measured Bandwidth, a Mean Bandwidth of 2.6 Gbps is a 26% Load Factor and bills 20 Gbps for $2,400, and a Mean Bandwidth of 5.3 Gbps is a 53% Load Factor and bills 30 Gbps for $3,600.

Up to a 25% Load Factor your Measured Bandwidth alone sets the charge at $120.00 for each Gbps of it, so an Access Method that carries its traffic in surges prices on how wide those surges run: $1,200 a month across a 10 Gbps optic, $600 at a 5 Gbps Measured Bandwidth, $240 at 2 Gbps.

Sustained traffic requires more aggregation capacity than occasional bursts at the same provisioned Bandwidth. Redundancy also affects capacity planning when each upstream must be able to carry the traffic independently.

The following example divides an illustrative $1,500 monthly invoice by three capacity commitments. These figures illustrate capacity planning assumptions and do not describe any particular provider's costs.

In the second row, provisioning two upstreams to carry the full 10 Gbps independently doubles the committed capacity to 20 Gbps. The third row assumes 5 Gbps of sustained traffic, with each upstream provisioned to carry that amount independently.

AS30265 IDC Connectivity accounts for sustained traffic through the multiplier. Above a 25% Load Factor, the charge comes to at least $480 for each Gbps of Mean Bandwidth. At or below 25%, Measured Bandwidth determines the charge.

A blended upstream rate combines peering, exchange capacity, and paid IP transit into an overall rate. Its effective cost depends on the mix of traffic and capacity commitments.

AS30265 calculates billable Bandwidth separately for each Access Method using its Measured Bandwidth and Mean Bandwidth on the Measured Direction. On IDC Connectivity it sets the whole charge; on FTTP Residential Connectivity it sets the Capacity and Service Fee components, and Wholesale Access is charged once whatever it is. When your billable Bandwidth changes significantly, or in a consistent pattern, we may notify you and adjust your billing.

Residential Connectivity is available in areas including Ottawa, Hamilton, Toronto, and surrounding GTA municipalities. Existing Bell fibre service at your premises or nearby can indicate eligibility. Contact us through Discord to check your address.

Yes. AS30265 delivers Residential Connectivity (FTTP) over CRTC-mandated wholesale access in Ontario. You get fibre to your home without being a Bell or Rogers retail subscriber. See the coverage table for eligible areas.

Yes. AS30265 Residential Connectivity is month-to-month with no term contract required. Pricing is straightforward and does not rely on promotional or introductory rates. See pricing for current rates.

If you just want Residential Connectivity, start with the Residential Connectivity guide. If you already have your own ASN and IP prefixes and want to run a BGP session (BYOIP), use the Advanced guide. The same guide covers SLAAC, for routing your Prefixes to your Access Methods without a BGP session.

Residential Connectivity lets you bring your own equipment and manage your network configuration. Your router must support PPPoE and DHCPv6-PD and have the physical interface required by your access technology. See CPE requirements before selecting equipment.

GPON subscribers need an SFP port, with the SFP-based ONT provided on loan by the wholesale provider. XGS-PON subscribers need an RJ45 Ethernet port, with the standalone ONT provided on loan by the wholesale provider.

Beyond that, your router needs PPPoE and DHCPv6-PD support. See CPE requirements for the full details.

Adding your card does not charge you immediately. You are charged when your installation date is set.

New Subscriptions start in Trial until installation is complete. You will not be charged during Trial.

Click Refresh on your subscription. The Subscriber Portal does not update automatically.

Yes. The Access Method username and password used by your router can be viewed again later on the Access Methods page, so you do not need to keep a separate copy unless you want one.

Installation is the wholesale provider's process for connecting the service to your home. In practice, this usually means a technician visit rather than a remote completion.

Even if you already have incumbent fibre service and are switching to us, the wholesale provider will still require an on-site install in most cases. See the Residential Connectivity pricing for installation fees and the installation policy for how charges work.

Rarely. In most cases, expect a technician visit even if you already have service from the incumbent and are just switching providers. Remote completion can happen, but it is the exception rather than the norm, and the wholesale provider decides.

Yes, within the policy window. Delete the service before the installation deadline if you want to cancel. If you need to reschedule, ask on Discord.

Scheduling is controlled by the wholesale provider, so we can request a change but cannot promise a specific date or time. See installation policy for the formal deadlines.

For billing, installation, fair use, and Allocation terms, read the Acceptable Use Policy. For service-specific details, start with Services and Residential Connectivity.

AS30265 uses IPv6 as its primary addressing model. Each subscriber receives an IPv6 Allocation for their network, with native IPv6 connectivity and NAT64 access to IPv4 destinations.

Our NAT64 service provides outbound connectivity from your IPv6 network to IPv4 destinations. See IPv6 and IPv4 addressing for details about addressing and IPv4 compatibility.

Yes. SLAAC on a Connection Profile routes a public IPv4 Prefix to your Access Methods without a BGP session. The Prefix can be a /32 from AS30265, subject to approval, or one you already hold with BYOIP. A BYOIP Allocation must be internet eligible. You can also announce a Prefix you hold over a BGP session.

Without either, your Access Method uses your IPv6 Allocation, and outbound traffic reaches IPv4-only destinations through our NAT64 translators. Full details are on IPv6 and IPv4 addressing.

Yes. A server with a public IPv4 address, routed to it with SLAAC or announced over a BGP session, answers IPv4 clients directly, and every server is reachable over IPv6. When the service is web-based and has no IPv4 address of its own, point the hostname at Cloudflare in proxy mode: Cloudflare terminates the client connection on IPv4 and fetches from your origin over IPv6.

That route suits this network especially well, because AS30265 peers directly with Cloudflare, so proxied traffic takes a short path back to your origin.

No. Most subscribers do not need to touch BGP at all. The service works as a normal Internet connection, and the advanced routing features are there if and when you want them.

Yes. Most people should start simple and get the basic service working first. If you later want to bring your own Prefix (BYOIP) and run a BGP session, use the Advanced guide.

Your IPv6 Allocation stays with you while you remain a subscriber and does not change when you reconnect. See the Allocation policy for the applicable terms.

A Subnet is a portion of your Allocation. You create one to tell the system "this is for my home network". Think of it as labelling a section of an Allocation for a specific purpose.

Because the setup is describing three different things: the Allocation delegated to you, the Subnet you reserve for a specific home network, and the Connection Profile that tells the Access Method which Subnet to use.

They are related, but they are not the same object, so they are configured separately in the Subscriber Portal.

Yes. If you have more than one location on our service, create a separate Subnet for each. One Allocation is usually enough - you just divide it up as needed.

Telephone support is not available. Our support channels are email at [email protected] and our Discord community, where you can share setup details and discuss technical questions with our team.

Email [email protected] or contact our team in the Discord community. Include the relevant setup step, router model, exact error text, and troubleshooting you have completed so we can assess the issue.

Subscribers are responsible for configuring their own equipment using our setup guides. We provide technical support for questions and issues that arise during setup, but do not provide a fully managed installation or configuration service for your router.

Follow the relevant setup guide and compare your equipment configuration with the documented settings. Check the service page and any linked policy for requirements that apply to your connection. If the issue continues, send the results of those checks to [email protected] or bring them to the Discord community.

Include your router model, the setup step you are working on, exact error text, service status, and the checks you have completed. A relevant screenshot can help illustrate the issue.

Double-check the Access Method username and password on the Access Methods page. No extra spaces. If the password field there is empty, leave it empty on your router too.

Yes. By default the WAN interface itself will usually only show a link-local IPv6 address, even when DHCPv6-PD is enabled and working normally.

The routed IPv6 Prefix is delegated to you and then used behind your router. If your LAN is not receiving the expected Prefix, follow the Allocation and Connection Profile setup steps in the Residential Connectivity guide, and confirm DHCPv6-PD is enabled on both the WAN and LAN sides.

Usually at 192.168.1.1 or 192.168.0.1. Check your router manual or the sticker on the router.

Write to [email protected] or ask in the Discord community, with a short description of the issue, any relevant screenshots, and the checks you have completed.

Yes. AS30265 holds the aggregated wholesale HSA agreement with the ILEC, operates the NNI where subscriber sessions are handed over, and terminates those sessions on our LNS. Wholesale partners can offer residential service using this infrastructure, with either a managed service or routed IP traffic delivered to their network. See Wholesale services for the integration options.

Depending on the integration option, AS30265 provides the ILEC wholesale relationship, NNI infrastructure, L2TP session termination, subscriber authentication, IP addressing, IP transit, AHSSPI transport, and the Subscriber Portal. We also design CPE that wholesale partners can supply under their own brand. You can select the services that complement the infrastructure your organisation operates.

Yes. Option A on the Wholesale services page supports service under your own brand. You manage sales, billing, and the subscriber relationship while AS30265 manages the ILEC relationship, NNI, LNS, routing, and IP transit. Subscriber disclosures identify AS30265 as the Internet service provider.

Option C is intended for ISPs that operate their own LNS. AS30265 would provide the ILEC relationship, NNI, and transport from the AHSSPI to your equipment. Availability is subject to the outcome of the current regulatory proceedings. LNS equipment can be hosted in our PoPs through IDC Connectivity, at the rates on its pricing section.

For ISPs that want to manage addressing and routing while AS30265 terminates subscriber sessions, Option B delivers routed IP traffic from our LNS to your network.

The Aggregated HSA Service Point of Interconnection (AHSSPI) is where the ILEC hands over aggregated subscriber traffic. Transport connects that point to the ISP's LNS. AS30265 provides infrastructure across this segment with pricing per subscriber. The transport options described on the Wholesale services page remain subject to the outcome of the current regulatory proceedings.

Wholesale services are priced per subscriber, so charges scale with your subscriber count. Separately purchased IDC Connectivity, IP transit, and related infrastructure may involve fixed commitments.

Registration requirements depend on your organisation's role and service model. Under Options A and B, AS30265 manages the wholesale HSA relationship with the ILEC. Under Option D, your organisation establishes its own wholesale HSA relationship with the ILEC, and AS30265 provides consulting for the filings, negotiations, and infrastructure development involved.

Residential Connectivity is currently available over wholesale access in Ontario. Option C is planned to launch in Toronto, with the wholesale partner operating its own LNS. Option D is planned to launch in Toronto and St. John's, Newfoundland for ISPs that establish their own wholesale HSA relationship. Both options are subject to the outcome of the current regulatory proceedings.

Contact us with your intended markets, operating model, and preferred integration option. Our team will review your requirements and discuss the technical and commercial arrangements.