Skip to main content

AS267634

ASN267634

CRISTIANO ROBERTO DA SILVA BARBOSA - ME

Registry

Authoritative registration data

AS number
267634
Name
ASN267634
Organisation
CRISTIANO ROBERTO DA SILVA BARBOSA - ME
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS267634
45.71.40.0/24 IPv4 /24 not checked
45.71.41.0/24 IPv4 /24 not checked
2804:4478::/33 IPv6 /33 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 AS267634
Address families
IX.br (PTT.br) Recife: ATM/MPLA 10,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 AS267634 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS267634 in AS paths

Observed upstreams
Families
AS52965 ASN52965 279 366
v4 v6
AS270804 ASN270804 265 355
v6
AS267427 ASN267427 265 351
v4
AS53087 ASN53087 252 339
v4 v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS267634 in AS paths

Observed downstreams
Families
AS274822 251 337
v6

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS28624 ASN28624 1 2
v6

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.