Our Network

Additionally, you can visit our contact us page for more information.

• 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.

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. 3.4 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.

• 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.
• Route originated from internal router.
• Do not announce to route servers.
• Prepend 1x to our tier 1 providers
• Remote triggered blackhole (request to be enabled).

• Disposable 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)
• BGP.Exchange Sponsor
• Free IPv6 Transit
• Free IPv6 Subnet Allocations
• bgp.tools Route Collector Feeder
• MANRS Participant