Skip to main content

AS266571

ASN266571

PROFIBER TELECOM LTDA

Registry

Authoritative registration data

AS number
266571
Name
ASN266571
Organisation
PROFIBER TELECOM LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

6

Total announced

8

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS266571
45.7.108.0/22 IPv4 /22 not checked
45.7.109.0/24 IPv4 /24 not checked
2804:3e10::/32 IPv6 /32 not checked
2804:3e10:8000::/33 IPv6 /33 RPKI not found
2804:3e10::/33 IPv6 /33 not checked
2804:3e10:3000::/41 IPv6 /41 not checked
2804:3e10:3800::/41 IPv6 /41 not checked
2804:3e10:3f00::/41 IPv6 /41 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS266571
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 5,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS266571 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS266571 in AS paths

Observed upstreams
Families
AS268267 ASN268267 646 1,512
v4 v6
AS6939 HURRICANE 114 283
v4 v6
AS267613 ASN267613 116 142
v4 v6
AS35280 F5 8 18
v4 v6
AS137409 GSLNETWORKS-AS-AP 6 10
v4 v6
AS6057 6057 2 8
v4 v6
AS7195 7195 1 2
v6
AS39120 CONVERGENZE-AS 1 2
v6
AS52468 52468 1 2
v6
AS61626 ASN61626 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS266571 in AS paths

Observed downstreams
Families
AS271493 ASN271493 8 9
v4
AS262740 ASN262740 2 2
v6

No rows match “”.

Showing – of

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.