Skip to main content

AS267419

ASN267419

VISUALNET TELECOM

Registry

Authoritative registration data

AS number
267419
Name
ASN267419
Organisation
VISUALNET TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

3

Total announced

6

Announced prefixes

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

Prefixes announced by AS267419
45.235.156.0/22 IPv4 /22 not checked
45.235.156.0/23 IPv4 /23 not checked
45.235.158.0/23 IPv4 /23 not checked
2804:4d38::/32 IPv6 /32 not checked
2804:4d38:8000::/33 IPv6 /33 RPKI valid
2804:4d38::/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 AS267419
Address families
IX.br (PTT.br) Brasília: ATM/MPLA 100,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 AS267419 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS267419 in AS paths

Observed upstreams
Families
AS52573 ASN52573 457 2,034
v4 v6
AS1031 PEER1-1031 2 8
v4
AS61568 ASN61568 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS267419 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS271253 ASN271253 1 4
v4

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.