Login

AS268829 ZUTTEL ZUTTEL FIBRA



Loading

AS MEMBERSHIP

AS268829 is a member of the following AS sets:

AUTONOMOUS SYSTEM

AS268829 ZUTTEL source:RADB

aut-numAS268829
as-nameZUTTEL
descrZUTTEL FIBRA
importfrom AS53062 accept ANY
importfrom AS263998 accept ANY
importfrom AS53013 accept ANY
mp-importafi ipv6.unicast from AS53062 accept ANY
mp-importafi ipv6.unicast from AS263998 accept ANY
mp-importafi ipv6.unicast from AS53013 accept ANY
exportto AS53062 announce AS268829:AS-ZUTTEL-ALL
exportto AS263998 announce AS268829:AS-ZUTTEL-ALL
exportto AS53013 announce AS268829:AS-ZUTTEL-ALL
mp-exportafi ipv6.unicast to AS53062 announce AS268829:AS-ZUTTEL-ALL
mp-exportafi ipv6.unicast to AS263998 announce AS268829:AS-ZUTTEL-ALL
mp-exportafi ipv6.unicast to AS53013 announce AS268829:AS-ZUTTEL-ALL
admin-cRafael Leite
tech-cRudson Costa
remarks===============================================
remarks24 x 7 technical support regarding our BGP routing
remarkspolicies or any inquiries concerning AS268829's
remarkssecurity and routing policies please reach out to us
remarksat the following channels:
remarks============================================================
remarksAS268829 Basic Interconnection Requirements
remarks============================================================
remarks============================================================
remarksThe following is required from your organization in order to
remarksestablish a BGP session with ZUTTEL at ASN 268829:
remarks- The customer must use a RIR assigned ASN.
remarks- The customer must have a route/route6 object for each prefix
remarksit intends to announce to us, which might include its own
remarksprefixes and, if desired, its customers' prefixes as well (customer cone).
remarks- Each route/route6 object corresponding to a customer prefix
remarks(yours or a prefix from your customer cone) must inform the
remarkscorrect ASN in its 'origin' field.
remarks- The ASN mentioned in the 'origin' field of each route and route6
remarksobject must have its proper and corresponding aut-num object.
remarks- The aforementioned aut-num objects must have a clear routing
remarkspolicy stating what as-sets are to be announced to us.
remarks- This as-set MUST be informed on PeeringDB ("IRR as-set/route-set")
remarksZUTTEL strongly encourages you to use two simultaneous methods to
remarksvalidate the origin of the prefixes you announce to us: IRR and ROA
remarks(published in your RPKI regime). This is highly recommended because
remarkssome of our direct upstreams and also indirect upstreams may reject
remarksany routes where there is a failure in the origin validation process.
remarksYou can start this process by "cleaning up your own house first", then
remarksworking directly with your customers so they can do their homework too,
remarksand, by doing that, we can all prevent route leaks and prefix hijacking
remarksfrom happening. :-)
remarksLast but not least, please feel free to contact us if you have any questions
remarksor need our assistance in working these best practices with you!
remarksWe will definitely make ourselves available to increase the security of the
remarksInternet, your experience as our customer/partner, and in the best
remarksinterest of our mutual agreement!
remarks============================================================
mnt-byMAINT-AS268829
changedrudsoncosta@3rsolution.com.br 20220912
sourceRADB
last-modified2023-11-13T16:12:28Z

REGISTERED ROUTES

45.173.220.0/22 This is a Commcorp Telecom customer proxy route object that was created because no existing route object with the same origin was found. Please contact noc@commcorp.com.br if you have any questions regarding this object. source:RADB

route45.173.220.0/22
originAS268829
descrThis is a Commcorp Telecom customer proxy route object that was created because no existing route object with the same origin was found. Please contact noc@commcorp.com.br if you have any questions regarding this object.
mnt-byMAINT-AS14840
changedfpgosch@commcorp.com.br 20200322
sourceRADB
last-modified2023-11-13T16:00:16Z
rpki-ov-statenot_found

45.173.220.0/24 Proxy Object source:ALTDB

route45.173.220.0/24
descrProxy Object
originAS268829
mnt-byMAINT-AS60503
admin-cFNX-AR
tech-cFNX-TR
notifyadmin@fnxtec.com
changedadmin@fnxtec.com 20200322
sourceALTDB
rpki-ov-statenot_found

45.173.221.0/24 Proxy Object source:ALTDB

route45.173.221.0/24
descrProxy Object
originAS268829
mnt-byMAINT-AS60503
admin-cFNX-AR
tech-cFNX-TR
notifyadmin@fnxtec.com
changedadmin@fnxtec.com 20200322
sourceALTDB
rpki-ov-statenot_found

45.173.222.0/24 Proxy Object source:ALTDB

route45.173.222.0/24
descrProxy Object
originAS268829
mnt-byMAINT-AS60503
admin-cFNX-AR
tech-cFNX-TR
notifyadmin@fnxtec.com
changedadmin@fnxtec.com 20200322
sourceALTDB
rpki-ov-statenot_found

45.173.223.0/24 Proxy Object source:ALTDB

route45.173.223.0/24
descrProxy Object
originAS268829
mnt-byMAINT-AS60503
admin-cFNX-AR
tech-cFNX-TR
notifyadmin@fnxtec.com
changedadmin@fnxtec.com 20200322
sourceALTDB
rpki-ov-statenot_found

2804:5b40::/32 This is a Commcorp Telecom customer proxy route object that was created because no existing route object with the same origin was found. Please contact noc@commcorp.com.br if you have any questions regarding this object. source:RADB

route62804:5b40::/32
originAS268829
descrThis is a Commcorp Telecom customer proxy route object that was created because no existing route object with the same origin was found. Please contact noc@commcorp.com.br if you have any questions regarding this object.
mnt-byMAINT-AS14840
changedfpgosch@commcorp.com.br 20200321
sourceRADB
last-modified2023-11-13T16:00:16Z
rpki-ov-statenot_found

Latest updates: totalpuss.induckduckgo.comnxnxnx.comxxnnxx.comwww.xxnxx.org69xxxx.comxnxnxn.comprounhub.comyouzjizz.comxvibro.com
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.