as393577.net Open in urlscan Pro
2606:4700:3031::6815:5b6  Public Scan

Form analysis
0 forms found in the DOM

Text Content

About Contact Peering Routing Communities Preferences Good for the Internet
Connectivity


TRITAN INTERNET LLC


aut-num: AS393577

as-cone: AS-TRITAN-CONE

route-set: RS-TRITAN-DEVELOPMENT, RS-TRITAN-INTERNET

links: PeeringDB, bgp.tools, Looking Glass

NOC

noc@as393577.net



ABOUT

AS393577 is a network created by Tritan Internet LLC, whose purpose is to
provide high quality routing to people in hard to reach areas around the globe.

Transit / IP Sponsoring Cloud Compute Colocation IP Leasing



CONTACT

Our contact information is located on our website, at https://tritan.gg/contact.
We prefer contact via our NOC email, but you can also reach us using a variety
of methods.



PEERING

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). See
   draft-ietf-idr-deprecate-as-set-confed-set.
 * 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.



COMMUNITIES

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

 * 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 our internal routers.
 * 393577:0:17, Route originated from GPC.
 * 393577:0:18, Route originated from STLIX.
 * 393577:0:19, Route originated from HOUIX.
 * 393577:0:20, Route originated from KCIX.
 * 393577:0:21, Route originated from iFog.
 * 393577:0:22, Route originated from NL-IX.
 * 393577:0:23, Route originated from SIX.
 * 393577:0:24, Route originated from MICE.



PATH PREFERENCES

The following order is how routes are preferred for outgoing traffic on our
network. The higher the number, the higher the preference. Generally speaking,
these are the routes we prefer to send traffic to due to either port speeds or
distance.

 * 100: Routes learned from TPA transit.
 * 101: Routes learned from MCI transit.
 * 102: Routes learned virtual internet exchanges.
 * 103: Routes learned from SJ.
 * 104: Routes learned from AMS.
 * 105: Routes learned from ONT.
 * 106: Routes learned from FRE.
 * 109: Routes learned from MCI.
 * 110: Routes learned from SEA.
 * 111: Routes learned from MSP.



"GOOD FOR THE INTERNET" PROJECTS

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

 * RIPE Atlas Probe
 * RIPE Atlas Anchor
 * NLNOG Ring
 * NLNOG Route Collector
 * Speedtest Server
 * BGP.Exchange Sponsor
 * Free IP Transit
 * Free IPv6 Sponsoring



CONNECTIVITY

The following map outlines the connectivity of AS393577 to Tier 1 ISPs.




Tritan Internet LLC © 2024