IP Transit in Adelaide
BGP transit from NetOz, AS142205, an Australian-owned network based in Adelaide, South Australia. Register your ASNs, AS-SETs and prefixes yourself in the NetOz Portal, see their RPKI status every day, and deal directly with the engineers who approve your routes.
BGP Transit for South Australian Networks
If you run your own autonomous system and announce your own address space, NetOz can carry your routes from Adelaide. Our network is built on multiple upstream providers and redundant network paths, and our infrastructure sits in a NextDC Tier IV facility in Adelaide.
Networks With Their Own ASN
Businesses, ISPs and hosting providers that hold an ASN and IPv4 or IPv6 space and want an Adelaide upstream with a clear, documented route approval process.
Transit Resellers
Providers with customers of their own. Register downstream ASNs behind your network and publish an AS-SET that we expand and check for route-leak risks.
Colocation Customers
Running your own routers or servers in our Adelaide colocation? Talk to us about announcing your own space alongside your rack.
How Route Registration Works
NetOz only accepts routes from ASNs you control and builds its BGP filters from the prefixes approved on your account. Everything is done in the IP transit area of the NetOz Portal, with every step reviewed by our network team.
Register your ASN
Add your ASN and the portal looks it up in the registry, APNIC first and then the other RIRs, showing the holder and contacts on file.
Read the guide →Prove you hold it
Use a registry contact link, an IRR remark on your aut-num object, or a signed letter of authority. Any one is enough to start the review.
Read the guide →Register your prefixes
Add each IPv4 or IPv6 prefix with its origin ASN and max length. We check it against the registry and the global RPKI straight away.
Read the guide →Approval and daily checks
Once our team approves a prefix, NetOz accepts the route and checks it against the global RPKI every day.
Read the guide →What You Get With NetOz IP Transit
Daily RPKI Monitoring
Every approved prefix is checked against the global RPKI once a day, and the result sits next to the prefix in the portal: RPKI valid, No ROA or RPKI invalid.
- ✓See every ROA covering a prefix and whether it matches
- ✓Email and a portal review if a route becomes RPKI invalid
- ✓Our team follows up if a route stays invalid for 3 days
- ✓A reminder if a prefix has had no ROA for 30 days
- ✓Nothing is switched off automatically: we contact you first
Seeing an invalid? Fix an RPKI invalid prefix.
AS-SET Expansion and Route-Leak Checks
Register the IRR AS-SET that describes your network and its customers. We look it up (APNIC first, also sources such as RADB), expand nested sets and flag anything that could cause trouble.
- ✓Full expansion tree, including nested AS-SETs
- ✓Members not approved on your account are flagged
- ✓Oversized sets and large carrier sets flagged as route-leak risks
- ✓Refresh after an IRR change to re-expand straight away
Downstream Customer ASNs
If you provide transit to other networks, register them as downstream ASNs behind one of your verified ASNs. The holder confirms you are their upstream, so their routes are accepted through your session.
- ✓Holder confirms by registry contact link or signed LOA
- ✓Register prefixes with the downstream ASN as origin
- ✓Keep your AS-SET in step with your customer list
A Network Team You Can Talk To
Every ASN, AS-SET and prefix gets a review from the NetOz network team. Questions and answers live in one thread per item in the portal, with documents such as LOAs and ROA exports attached where they belong.
- ✓Email when a review needs your reply
- ✓Uploaded documents visible only to NetOz staff
- ✓View or Manage access per team member
- ✓24/7 Australian support on 1800 134 656
IP Transit Pricing
IP transit is quoted to your requirements. Tell us your ASN, the prefixes you plan to announce and where you need to connect, and we will put together a quote.
Free Network Tools
Check your routing and address plans before you connect. These tools are free to use from our Australian network.
IP Transit FAQ
What is NetOz's ASN?
NetOz operates AS142205 from Adelaide, South Australia. You can look us up on bgp.tools and PeeringDB, and reach our network team at networks@netoz.au.
What do I need before NetOz can accept my routes?
Your ASN must be registered and verified on your NetOz account, and every prefix you announce must be registered with its origin ASN and approved by our network team. NetOz builds its BGP filters from the prefixes approved on your account.
How do I prove I hold my ASN?
You only need one of three options: we email a one-time link to a contact on the ASN's registry record, you add a token we generate as a remark on your aut-num object in the IRR, or you upload a signed letter of authority from the holder.
What prefix sizes are accepted?
IPv4 prefixes between /8 and /24 and IPv6 prefixes between /16 and /48. Private and reserved space is not accepted. You can set a max length if you also announce more specific routes, up to /24 for IPv4 or /48 for IPv6.
How does NetOz use RPKI?
Every approved prefix is checked against the global RPKI once a day. If a route becomes RPKI invalid we email you and open a review in the portal. If it stays invalid for 3 days our team follows up. Nothing is switched off automatically.
Can I resell transit to my own customers?
Yes. Register each customer network as a downstream ASN behind one of your verified ASNs. The holder confirms you are their upstream through a registry contact link or a signed letter, and you can then register prefixes that originate from it.
How much does IP transit cost?
IP transit is quoted to suit your requirements. Send us your ASN, the prefixes you plan to announce and where you need to connect, and we will come back with a quote.
Ready to Announce Your Routes From Adelaide?
Get a quote for IP transit from AS142205, or call our Adelaide team on 1800 134 656.
Request an IP Transit Quote