Skip to main content

AS19338

19338

Autonomous System AS19338 from CL-ACIS-LACNIC

Registry

Authoritative registration data

AS number
19338
Name
19338
Organisation
Autonomous System AS19338 from CL-ACIS-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS19338 in AS paths

Observed upstreams
Families
AS6057 6057 32 546
v4 v6
AS7004 34 122
v4 v6
AS6939 HURRICANE 34 78
v4
AS7195 7195 4 9
v6

No rows match “”.

Showing of

Observed downstreams

9 networks seen after AS19338 in AS paths

Observed downstreams
Families
AS6429 127 1,110
v4 v6
AS6535 17 625
v4 v6
AS27995 27995 20 340
v4 v6
AS14795 7 28
v4
AS19411 7 19
v4
AS10778 4 8
v4
AS264636 7 7
v4
AS22047 22047 5 7
v4
AS49544 i3Dnet 1 3
v6

No rows match “”.

Showing of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 22 297
v4 v6
AS269956 20 281
v4 v6
AS270014 270014 20 281
v4 v6
AS36236 NETACTUATE 15 271
v4 v6
AS51185 MAINSTREAMING-AS 14 262
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.