AS266268 JND - PROVEDOR

Company Website:

http://www.pronetprovedor.com.br

Looking Glass:

https://bgp.he.net/lg/266268

Country of Origin:

Brazil

Internet Exchanges: 3

Prefixes Originated (all): 2
Prefixes Originated (v4): 1
Prefixes Originated (v6): 1

Prefixes Announced (all): 2
Prefixes Announced (v4): 1
Prefixes Announced (v6): 1

RPKI Originated Valid (all): 2
RPKI Originated Valid (v4): 1
RPKI Originated Valid (v6): 1

RPKI Originated Invalid (all): 0
RPKI Originated Invalid (v4): 0
RPKI Originated Invalid (v6): 0

BGP Peers Observed (all): 1
BGP Peers Observed (v4): 1
BGP Peers Observed (v6): 1

IPs Originated (v4): 1,024
AS Paths Observed (v4): 705
AS Paths Observed (v6): 663

Average AS Path Length (all): 4.404
Average AS Path Length (v4): 4.573
Average AS Path Length (v6): 4.225

AS266268 IPv4 Peers

ASN	Name
AS61568	ALOO TELECOM - FSF TECNOLOGIA SA

AS266268 IPv6 Peers

ASN	Name
AS61568	ALOO TELECOM - FSF TECNOLOGIA SA

AS266268 IPv4 Peer Count

AS266268 IPv6 Peer Count

AS266268 IPv4 Prefixes Announced

AS266268 IPv6 Prefixes Announced

AS266268 IPv4 Prefixes Originated

AS266268 IPv6 Prefixes Originated

AS266268 IPv4 Route Propagation

Loading...

AS266268 IPv6 Route Propagation

Loading...

Prefix	Description	Visibility
Loading Prefixes...

Prefix	Description
45.65.208.0/22	JND - PROVEDOR

Prefix	Description	Visibility
Loading Prefixes...

Prefix	Description
2804:3d54::/32	JND - PROVEDOR

Bogon Prefixes
Prefix	Type	Status

Rank	Description	IPv6	Peer
1	ALOO TELECOM - FSF TECNOLOGIA SA	X	AS61568

Rank	Description	IPv4	Peer
1	ALOO TELECOM - FSF TECNOLOGIA SA	X	AS61568

Loading whois...

Loading...

TC

aut-num: AS266268 as-name: PRONET_PROVEDOR descr: JOSE N. D. DE C. J. - PRONET - PROVEDOR admin-c: NIJ27-NICBR tech-c: RUCRO64-NICBR import: from AS61568 accept ANY import: from AS61618 accept ANY mp-import: afi ipv6.unicast from AS61568 accept ANY mp-import: afi ipv6.unicast from AS61618 accept ANY export: to AS61568 announce AS266268:AS-ANNOUNCEMENTS export: to AS61618 announce AS266268:AS-ANNOUNCEMENTS mp-export: afi ipv6.unicast to AS61568 announce AS266268:AS-ANNOUNCEMENTS mp-export: afi ipv6.unicast to AS61618 announce AS266268:AS-ANNOUNCEMENTS remarks: =============================================== PRONET_PROVEDOR Website: https://www.pronetprovedor.com.br/ Status Page: http://status.pronetprovedor.com.br/ Looking Glass: http://lg.pronetprovedor.net.br/ BGP View: http://bgpview.pronetprovedor.com.br:3000/ Routing Policy and Communities: http://www.pronetprovedor.com.br/routingpolicy =============================================== remarks: =============================================== 24 x 7 technical support regarding our BGP routing policies or any inquiries concerning AS266268's security and routing policies please reach out to us at the following channels: remarks: Network issues / requests: noc@pronetprovedor.com.br Peering issues / requests: peering@pronetprovedor.com.br Abuse and SPAM : abuse@pronetprovedor.com.br Or dial +55 (75) 9804-6384 =============================================== remarks: ============================================================ AS266268 Basic Interconnection Requirements ============================================================ remarks: The following is required from your organization in order to establish a BGP session with PRONET PROVEDOR at ASN 266268: - 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. - This as-set MUST be informed on PeeringDB ("IRR as-set/route-set") remarks: PRONET PROVEDOR 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-AS266268 notify: frelan1@hotmail.com changed: noc@3rsolution.com.br 20251110 source: TC last-modified: 2025-11-10T19:29:33Z

Exchange	CC	City	IPv4	IPv6
PTT Fortaleza	BR	Fortaleza	45.68.76.52	2001:12f8:0:9::148:52
PTT Salvador	BR	Salvador	200.219.145.214	2001:12f8:0:8::214
PTT São Paulo	BR	São Paulo	187.16.214.207	2001:12f8::214:207

Loading probes...