aut-num: AS263008
as-name: UNSPECIFIED
descr: UNIREDES TELECOMUNICACOES E INFORMATICA LTDA ME
admin-c: LDS111-NICBR
tech-c: WIOLI2-NICBR
mnt-by: MAINT-AS263008
notify: db-admin[at]bgp.net.br
changed: db-admin[at]bgp.net.br 20160721 #23:07:36(BRT)
source: TC
aut-num: AS263008
as-name: UniFibra
descr: UNI TELECOMUNICACOES
import: from AS263047 accept ANY
mp-import: afi ipv6.unicast from AS263047 accept ANY
export: to AS263047 announce AS263008:AS-UNIREDES-ALL
mp-export: afi ipv6.unicast to AS263047 announce AS263008:AS-UNIREDES-ALL
admin-c: Leonardo Deascanio
tech-c: Rudson Costa
remarks: ===============================================
Uni Fibra
Website: https://unifibra.net/
Peering and Routing Policy: https://www.peeringdb.com/net/18558
Peering: peering[at]unifibra.net.br
===============================================
remarks: ===============================================
24 x 7 technical support regarding our BGP routing
policies or any inquiries concerning AS263008's
security and routing policies please reach out to us
at the following channels:
Network issues / requests: engenharia[at]unifibra.net.br
Peering issues / requests: peering[at]unifibra.net.br
Abuse and SPAM : abuse[at]unifibra.net.br
Or dial +55 (11) 4003-5215
===============================================
remarks: ============================================================
AS263008 Basic Interconnection Requirements
============================================================
remarks: The following is required from your organization in order to
establish a BGP session with Uni Fibra at ASN 263008:
- The customer must use a RIR assigned ASN.
- The customer must have a route/route6 object for each prefix
it intends to announce to us, which might include its own
prefixes and, if desired, its customers' prefixes as well (customer cone).
- Each route/route6 object corresponding to a customer prefix
(yours or a prefix from your customer cone) must inform the
correct ASN in its 'origin' field.
- The ASN mentioned in the 'origin' field of each route and route6
object must have its proper and corresponding aut-num object.
- The aforementioned aut-num objects must have a clear routing
policy stating what as-sets are to be announced to us.
remarks: - This as-set MUST be informed on PeeringDB ("IRR as-set/route-set")
Uni Fibra strongly encourages you to use two simultaneous methods to
validate the origin of the prefixes you announce to us: IRR and ROA
(published in your RPKI regime). This is highly recommended because
some of our direct upstreams and also indirect upstreams may reject
any routes where there is a failure in the origin validation process.
remarks: You can start this process by "cleaning up your own house first", then
working directly with your customers so they can do their homework too,
and, by doing that, we can all prevent route leaks and prefix hijacking
from happening. :-)
remarks: Last but not least, please feel free to contact us if you have any questions
or need our assistance in working these best practices with you!
We will definitely make ourselves available to increase the security of the
Internet, your experience as our customer/partner, and in the best
interest of our mutual agreement!
mnt-by: MAINT-AS263324
changed: rudsoncosta[at]3rsolution.com.br 20230208 #17:06:11Z
source: RADB
last-modified: 2025-03-17T15:00:07Z
输入域名、IP地址或ASN号码，系统自动识别