We've currently paused new orders due to recent demand while we catch up on the provisioning queue, please check back soon!Explore
MANRS compliant, RPKI validated, open to peering
AS393577

Tritan's
network.

AS393577 is a network created by us, whose purpose is to provide high quality routing to hobbyists, developers, and anyone else. Our network's quality is consistently rated as one of the best in our category of hosting providers.

Short AS Path
Optimized routing
Noteworthy Peering
Global connectivity
Low Latency
Fast performance
Network Overview

Real-time statistics and information about our global network infrastructure and peering relationships.

PeeringDB
View our peering information
BGP Tools
Analyze our network's BGP data
BGP Looking Glass
Check our global routing
MANRS compliant · RPKI validated
Registry

Network information.

Live Numbers

Network statistics.

Our network is constantly growing and evolving. Here are some current statistics:

loading
Loading
Reach Us

Get in contact.

We prefer to be contacted via our ticket system, but you can also reach us using the methods below.

Routing Security

Compliance.

MANRS

We have committed to joining Mutually Agreed Norms for Routing Security (MANRS) to help secure the internet's routing infrastructure. By participating in the MANRS initiative, we are committed to implementing best practices that enhance the resilience of the global internet.

Policy

Peering policy.

We are open to peering with anyone, anywhere. A list of physical IXPs we are present at can be found on our PeeringDB.

You will need to:
Have an ASN and publicly routable IP space of at least a /24 IPv4 and/or /48 IPv6.
Have an entry on PeeringDB and keep it up to date.
All routes must be filtered to only send routes that have valid RPKI records.
Only send routes that you are allowed to send or from your own network.
Only send traffic that is destined to routes that we announced to you.
You add our ASN to your AS-SET, and accept any routes from our upstream AS-SET.
You do not announce bogons.
Not point default or static routes at us without permission. You must only send us traffic for prefixes we advertise.
If you're interested, please contact our NOC.
Policy

Routing policy.

Listed below is our network's routing policy for all accepted routes, customers, and downstreams.

Attempt to find an as-set to use for this network:
1
In PeeringDB, for this ASN, check for an IRR as-set name. Validate the as-set name by retrieving it. If it exists, use it.
2
In IRR, query for an aut-num for this ASN. If it exists, inspect the aut-num for this ASN to see if we can extract from their IRR policy an as-set for what they will announce to Tritan by finding export or mp-export to AS393577, ANY, or AS-ANY. Precedence is as follows: The first match is used, "export" is checked before "mp-export", and "export: to AS393577" is checked before "export: to ANY" or "export: to AS-ANY". Validate the as-set name by retrieving it. If it exists, use it.
3
Check various internal lists maintained by Tritan Internet's NOC that map ASNs to as-set names where we discovered or were told of them. Validate the as-set name by retrieving it. If it exists, use it.
4
If no as-set name is found by the previous steps, use the ASN.
5
Collect the received routes for all BGP sessions with this ASN. This details both accepted and filtered routes.
For each route, perform the following rejection tests:
Reject default routes 0.0.0.0/0 and ::/0.
Reject AS paths that use BGP AS_SET notation (i.e. [1] or [1 2], etc).
Reject prefix lengths less than minimum and greater than maximum. For IPv4 this is 8 and 24. For IPv6 this is 16 and 48. Reject bogons (RFC1918, documentation prefix, etc).
Reject exchange prefixes for all exchanges Tritan Internet is connected to.
Reject AS paths that use unallocated ASNs between 64496 to 131071 and 1000000 to 4294967295. IANA AS Number Registry
Reject AS paths that use AS23456. AS23456 should not be encountered in the AS paths of BGP speakers that support 32-bit ASNs.
Reject AS paths that use AS0. As per RFC 7606, "A BGP speaker MUST NOT originate or propagate a route with an AS number of zero".
Reject routes that have RPKI status INVALID_ASN or INVALID_LENGTH based on the origin AS and prefix.
Reject AS paths that use known transit networks.
Reference

BGP communities.

The following are our origin communities to express where routes are learned from:

CommunityDescription
393577:0:12Route originated from transit provider.
393577:0:13Route originated from an internet exchange.
393577:0:14Route originated from direct peer.
393577:0:15Route originated from downstream.
393577:0:16Route originated from internal router.
Do not announce to route serversRequest to be enabled.
Prepend 1x to tier 1 providersRequest to be enabled.
Blackhole CommunityRequest to be enabled.
Community

"Good for the Internet"

Tritan Internet LLC hosts a variety of "good for the internet" projects to support the small community of ISPs around the globe.

Current projects:
Free email service for all Tritan customers.
Secure and private DNS.
Filtered DNS
23.142.248.10, 2602:291::10
Cache for RPKI data for use with routers.
Participate in active measurements of the Internet.
Help anonymize internet traffic.
Participate in the NLNOG Ring.
Share routing information.
Time synchronization for network devices.
Free IPv6 transit service.
Free IPv6 subnet allocations.
Feed BGP updates to bgp.tools.
Participate in the MANRS initiative.
Public torrent tracker.
Send and receive faxes via web.
Peering Fabric

Internet exchanges.

We have a presence in the following Internet Exchanges, and will peer or provide transit over them.

loading
Loading
Topology

Connectivity.

Our network is built on a foundation of frustration. We were tired of the lack of quality and high prices of other providers, so we decided to build our own. Our network is built with quality and reliability as core principles, ensuring optimal performance for all our customers.

Network connectivity
Customers

Downstreams.

Tritan Internet is proud to power the following networks:

loading
Loading
Peer With Us

Open to peering,
anywhere.

Read the policy, check our PeeringDB entry, and contact our NOC when you are ready to bring up a session.