Our 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
Noteworthy Peering
Low Latency
Information
aut-num: AS393577
as-cone: AS-TRITAN-CONE
route-set: RS-TRITAN-DEVELOPMENT, RS-TRITAN-INTERNET
links: PeeringDB, bgp.tools, Blackhole Data
Network Statistics
Our network is constantly growing and evolving. Here are some of the statistics for our network.
Contact
We prefer to be contacted via our ticket system, but you can also reach us using a variety of methods.
Additionally, you can visit our contact us page for more information.
Compliance
We have commited to joining Mutually Agreed Norms for Routing Security (MANRS) to help secure the internet's routing infrastructure because we believe that a stable and secure network is essential for everyone. By participating in the MANRS initiative, we are committing to implement best practices that enhance the resilience of the global internet.
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.
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:
- 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.
- 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.
- 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.
- If no as-set name is found by the previous steps, use the ASN.
- 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. https://www.iana.org/assignments/as-numbers/as-numbers.xhtml
- 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.
BGP Communities
The following are our origin communities to express where routes are learned from:
| Community | Description |
|---|---|
| 393577:0:12 | Route originated from transit provider. |
| 393577:0:13 | Route originated from an internet exchange. |
| 393577:0:14 | Route originated from direct peer. |
| 393577:0:15 | Route originated from downstream. |
| 393577:0:16 | Route originated from internal router. |
| Do not announce to route servers | Request to be enabled. |
| Prepend 1x to tier 1 providers | Request to be enabled. |
| Blackhole Community | Request to be enabled. |
"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:
- Email Service
- Filtered DNS Over HTTPS (https://doh.tritan.host/dns-query)
- Conventional Filtered DNS (23.142.248.10, 2602:291::10)
- RPKI Cache Server (rtr.netops.tritan.host:8282)
- RIPE Atlas Anchor
- Tor Relay
- NLNOG Ring
- NLNOG Route Collector
- Ookla Speedtest Server (ID: 67649)
- NTP Servers (time.tritan.gg, time2.tritan.gg)
- Free IPv6 Transit
- Free IPv6 Subnet Allocations
- bgp.tools Collector Feeder
- MANRS Participant
- Linux Mirrors Cache
Internet Exchanges
We have a presence in the following Internet Exchanges, and will peer or provide transit over them.
| Name | Speed | IPv4 | IPv6 |
|---|
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 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.
Downstreams
Tritan Internet is proud to power the following networks:
| Name | ASN | PeeringDB |
|---|
Still not convinced?
Our team is here to help. Contact us today to learn more about our network.
Reach out