Skip to main content

AS39838

as-peering_latam

Valor Information Technologies, S.L.

Registry

Authoritative registration data

AS number
39838
Name
as-peering_latam
Organisation
Valor Information Technologies, S.L.
Country
RIR
RIPE
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 AS39838
141.136.56.0/21 IPv4 /21 not checked
45.145.135.0/24 IPv4 /24 not checked
2a0a:e9c3::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS39838 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS39838 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 1,654 45,305
v4 v6
AS271957 182 1,068
v6
AS6057 6057 12 388
v4 v6
AS39640 256 345
v6
AS49353 as-jsans 253 336
v4
AS7195 7195 12 171
v4 v6
AS6939 HURRICANE 22 22
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS39838 in AS paths

Observed downstreams
Families
AS272809 1,306 33,355
v4 v6
AS21826 327 13,415
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS52320 52320 6 150
v4 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.