Services
AS30265 provides Internet connectivity for organisations, households, and network operators. Our services combine static addressing, visibility through the Subscriber Portal, and optional BGP sessions or SLAAC over a shared backbone.
IP transit
IP transit is available via Tunnel Connectivity, IDC Connectivity, and Residential Connectivity.
Tunnel Connectivity and FTTN Residential Connectivity are flat-rate. IDC Connectivity and FTTP Residential Connectivity are charged on the traffic an Access Method carries, by one method set out in How billable Bandwidth is charged.
For a plain-language explanation of how residential throughput is shaped across the access loop, regional aggregation, and upstream IP transit, see the FAQ performance notes.
Tunnel Connectivity
IP transit over GRE, L2TP, or IPSec tunnels with self-service provisioning. Connect from anywhere with an existing Internet connection.
IDC Connectivity
Switch port access at our PoPs with integration into subscriber Allocations, BGP sessions, and SLAAC.
Residential Connectivity
Wholesale FTTP and FTTN in Ontario, with bring your own equipment.
Wholesale services
Wholesale aggregation for Canadian ISPs through resale and routing handoff. Additional LNS and transport options are subject to regulatory proceedings.
➡️ Learn moreLIR services
Each subscriber receives a static IPv6 Allocation from AS30265's provider-aggregatable (PA) IPv6 address space that remains associated with them for the duration of their relationship with AS30265. The same Prefix is used across all of the subscriber's Access records and supports multi-homing via BGP sessions where required.
LIR services are free for anyone with an active subscription.
- Static IPv6 Prefix from AS30265's provider-aggregatable (PA) IPv6 address space per subscriber, typically a /48
- Prefix retained across all active subscriptions
- Support for announcing subscriber Allocations and AS30265-assigned Prefixes via BGP sessions, or through SLAAC without a session
Network
Points of Presence
- Cogent Toronto Data Centre (245 Consumers Road, Toronto, ON M2J 1R3, Canada)
Performance
We employ segment routing for intelligent path selection, establish wavelength-based backbone connectivity across our PoPs, and maintain extensive BGP sessions with networks worldwide. Wherever practical, traffic remains on our own infrastructure until it is close to its destination.
All subscribers may apply their own traffic engineering policies, design resilient connectivity paths, and optimise routing behaviour through community-based policy controls.
Routing security
Prefixes a subscriber announces over a BGP session are accepted only from a verified ASN, and only while they match Internet Routing Registry (IRR) route objects and Resource Public Key Infrastructure (RPKI) ROAs. Unicast Reverse Path Forwarding (uRPF) is enabled on all subscriber ports for source address validation.
IPv6 and IPv4 addressing
AS30265 runs as an IPv6-first network. Every Access Method is addressed from your IPv6 Allocation, BGP sessions are established as dual-address-family over IPv6-only transport, and non-BGP subscribers without SLAAC connect via IPv6-only PPPoE or IPoE.
Public IPv4 addressing is available in two ways. Announce an IPv4 Prefix you already hold over your BGP session with Bring-your-own-IP (BYOIP). Without a BGP session, SLAAC on a Connection Profile routes IPv4 to your Access Methods, using a /32 from AS30265, subject to approval, or a Prefix you hold with BYOIP. A BYOIP Allocation must be internet eligible.
Outbound traffic keeps working with the IPv4 Internet. Sessions from your IPv6 addresses to IPv4-only destinations pass through our NAT64 translators, and 464XLAT (CLAT) on your side covers applications that expect a local IPv4 socket. Browsing, package updates, and API calls to legacy hosts behave the way they always have.
Inbound IPv4 connections reach any Prefix routed to you through BYOIP or SLAAC. Without one, inbound connections arrive over IPv6. When a service you publish is web-based and should also answer IPv4 clients, route the hostname through Cloudflare in proxy mode: Cloudflare terminates the client connection on IPv4 and fetches from your origin over IPv6. We recommend that route for a second reason - AS30265 peers directly with Cloudflare, so proxied traffic reaches your origin over a short, well-controlled path.
BGP sessions
BGP sessions are available for all subscribers who require them. Sessions are carried over IPv6 transport and can be dual-address-family where required.
Session capabilities
- Direct BGP sessions over IPv6 transport
- Dual-address-family sessions
- DFZ full table support
- Default route
Peering policy
AS30265 operates an open peering policy and welcomes interconnection with networks of all sizes, including educational and research networks.
Downstream ASNs are treated as stub ASNs by design. We only allow announcements from verified ASNs, and we enforce prefix filters so only prefixes authorised by the ASN are accepted.
Additional services
Network consulting
Assistance with IPv6 deployment planning, routing design, and BGP configuration.
Educational support
Training and technical guidance for network operators and organisations.
Getting started
Ready to get connected? Our quick start guides walk you through everything step by step.