| aut-num | AS268797 |
| as-name | SETE_CONNECT |
| descr | SETE CONNECT |
| admin-c | SCTIN10-NICBR |
| tech-c | SCTIN10-NICBR |
| import | from AS61618 accept ANY |
| import | from AS52871 accept ANY |
| mp-import | afi ipv6.unicast from AS61618 accept ANY |
| mp-import | afi ipv6.unicast from AS52871 accept ANY |
| export | to AS61618 announce AS268797:AS-SETE-CONNECT-ALL |
| export | to AS52871 announce AS268797:AS-SETE-CONNECT-ALL |
| mp-export | afi ipv6.unicast to AS61618 announce AS268797:AS-SETE-CONNECT-ALL |
| mp-export | afi ipv6.unicast to AS52871 announce AS268797:AS-SETE-CONNECT-ALL |
| remarks | *************************************************************** |
| remarks | Abuse/UCE: noc@7neconnect.com.br |
| remarks | Network: noc@7neconnect.com.br |
| remarks | Peering: noc@7neconnect.com.br |
| remarks | Website: https://www.7neconnect.com.br/ |
| remarks | Looking Glass: http://lg.7neconnect.com.br/ |
| remarks | Peering and Routing Policy: http://as268797.peeringdb.com/ |
| remarks | *************************************************************** |
| remarks | *************************************************************** |
| remarks | 24 x 7 technical support regarding our BGP routing |
| remarks | policies or any inquiries concerning AS268797's |
| remarks | security and routing policies please reach out to us |
| remarks | at the following channels: |
| remarks | Network issues / requests: noc@7neconnect.com.br |
| remarks | Peering issues / requests: noc@7neconnect.com.br |
| remarks | Abuse and SPAM : noc@7neconnect.com.br or |
| remarks | dial +55 (75) 2102-9210 |
| remarks | *************************************************************** |
| remarks | *************************************************************** |
| remarks | AS268797 Basic Interconnection Requirements |
| remarks | *************************************************************** |
| remarks | The following is required from your organization in order to |
| remarks | establish a BGP session with Sete Connect at ASN 268797: |
| remarks | - The customer must use a RIR assigned ASN. |
| remarks | - The customer must have a route/route6 object for each prefix |
| remarks | it intends to announce to us, which might include its own |
| remarks | prefixes and, if desired, its customers' prefixes as well |
| remarks | (customer cone). |
| remarks | - Each route/route6 object corresponding to a customer prefix |
| remarks | (yours or a prefix from your customer cone) must inform the |
| remarks | correct ASN in its 'origin' field. |
| remarks | - The ASN mentioned in the 'origin' field of each |
| remarks | route and route6 |
| remarks | object must have its proper and corresponding |
| remarks | aut-num object. |
| remarks | - The aforementioned aut-num objects must have a clear routing |
| remarks | policy stating what as-sets are to be announced to us. |
| remarks | - This as-set MUST be informed on PeeringDB |
| remarks | ("IRR as-set/route-set") |
| remarks | Sete Connect strongly encourages you to use two |
| remarks | simultaneous methods to |
| remarks | validate the origin of the prefixes you announce |
| remarks | to us: IRR and ROA |
| remarks | (published in your RPKI regime). This is highly |
| remarks | recommended because |
| remarks | some of our direct upstreams and also indirect |
| remarks | upstreams may reject |
| remarks | any routes where there is a failure in the origin |
| remarks | validation process. |
| remarks | You can start this process by "cleaning up your |
| remarks | own house first", then |
| remarks | working directly with your customers so they can |
| remarks | do their homework too, |
| remarks | and, by doing that, we can all prevent route leaks |
| remarks | and prefix hijacking from happening. :-) |
| remarks | Last but not least, please feel free to contact us |
| remarks | if you have any questions |
| remarks | or need our assistance in working these best |
| remarks | practices with you! |
| remarks | We will definitely make ourselves available to |
| remarks | increase the security of the |
| remarks | Internet, your experience as our customer/partner, |
| remarks | and in the best |
| remarks | interest of our mutual agreement! |
| remarks | *************************************************************** |
| mnt-by | MAINT-AS268797 |
| changed | noc@7neconnect.com.br 20250902 |
| source | TC |
| last-modified | 2025-09-02T21:42:46Z |
| aut-num | AS268797 |
| as-name | SETE-CONNECT |
| descr | =============================================== |
| descr | AS268797 SETE CONNECT TECNOLOGIA DA INFORMACAO |
| descr | =============================================== |
| import | from AS266003 accept ANY |
| import | from AS52871 accept ANY |
| mp-import | afi ipv6.unicast from AS266003 accept ANY |
| mp-import | afi ipv6.unicast from AS52871 accept ANY |
| export | to AS266003 announce AS268797:AS-SETE-CONNECT-ALL |
| export | to AS52871 announce AS268797:AS-SETE-CONNECT-ALL |
| mp-export | afi ipv6.unicast to AS266003 announce AS268797:AS-SETE-CONNECT-ALL |
| mp-export | afi ipv6.unicast to AS52871 announce AS268797:AS-SETE-CONNECT-ALL |
| admin-c | Vagner Brasileiro |
| tech-c | Rudson Costa |
| tech-c | Darlecio Almeida |
| remarks | ================================================================================= |
| remarks | This is a Proxy-registered aut-num object. |
| remarks | This aut-num object was created because no existing object for this ASN was found |
| remarks | and, since some Brasileiro peers filter based on these objects, any route associated |
| remarks | with this ASN may be rejected if this aut-num object is not created, and the |
| remarks | same condition also applies to route and as-set objects belonging to this ASN. |
| remarks | Please contact noc@brasileirotelecom.com.br if you have any questions regarding this object |
| remarks | or, in case you own this ASN, please contact us so we can transfer the authority |
| remarks | of these aut-num, as-set and any route objects we maintain on your behalf to you on RADb. |
| remarks | ================================================================================= |
| remarks | ********************************************************************************* |
| remarks | Any inquiries concerning security incidents from source IP addresses from this ASN |
| remarks | MUST be addressed directly to them at their respective support channels. |
| remarks | Please search for their relevant contact information at either PeeringDB or |
| remarks | issue the proper whois at their aut-num. |
| remarks | Brasileiro (AS266003) is responsible for NEITHER routing policies nor security issues |
| remarks | of this direct or indirect customers Autonomous System Number. |
| remarks | In case of abuse/UCE and you failed to hearing from the support personnel |
| remarks | of this ASN, please let us know at: |
| remarks | Abuse/UCE: abuse@brasileirotelecom.com.br |
| remarks | ********************************************************************************* |
| mnt-by | MAINT-AS266003 |
| changed | noc@brasileirotelecom.com.br 20210703 |
| source | RADB |
| last-modified | 2024-01-09T17:00:05Z |