Skip to main content

AS28319

28319

Autonomous System AS28319 from CL-WISP1-LACNIC

Registry

Authoritative registration data

AS number
28319
Name
28319
Organisation
Autonomous System AS28319 from CL-WISP1-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS28319
160.19.200.0/24 IPv4 /24 not checked
160.19.201.0/24 IPv4 /24 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 AS28319
Address families
PIT Santiago - PIT Chile: LAN 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 AS28319 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS28319 in AS paths

Observed upstreams
Families
AS263237 838 3,880
v4
AS266771 266771 249 322
v4
AS6939 HURRICANE 45 77
v4
AS6057 6057 4 26
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS28319 in AS paths

Observed downstreams
Families
AS52439 52439 845 3,952
v4

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 2 13
v4
AS49544 i3Dnet 2 13
v4
AS269956 2 13
v4
AS270014 2 13
v4
AS51185 MAINSTREAMING-AS 2 8
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.