Skip to main content

AS27678

27678

Autonomous System AS27678 from CL-NICH-LACNIC

Registry

Authoritative registration data

AS number
27678
Name
27678
Organisation
Autonomous System AS27678 from CL-NICH-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

6

Total announced

14

Announced prefixes

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

Prefixes announced by AS27678
200.1.122.0/23 IPv4 /23 not checked
190.124.24.0/24 IPv4 /24 not checked
190.124.25.0/24 IPv4 /24 not checked
200.1.120.0/24 IPv4 /24 not checked
200.16.113.0/24 IPv4 /24 not checked
200.27.115.0/24 IPv4 /24 not checked
200.7.6.0/24 IPv4 /24 not checked
200.7.7.0/24 IPv4 /24 not checked
2001:1398:14::/48 IPv6 /48 not checked
2001:1398:1::/48 IPv6 /48 not checked
2001:1398:2::/48 IPv6 /48 not checked
2001:1398:3::/48 IPv6 /48 not checked
2001:1398:4::/48 IPv6 /48 not checked
2001:1398:5::/48 IPv6 /48 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 AS27678 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS27678 in AS paths

Observed upstreams
Families
AS14259 938 5,062
v4 v6
AS18747 IFX18747 64 193
v4 v6
AS6429 40 117
v4 v6

No rows match “”.

Showing of

Observed downstreams

12 networks seen after AS27678 in AS paths

Observed downstreams
Families
AS52234 120 145
v4 v6
AS52305 88 120
v4 v6
AS28377 59 116
v4 v6
AS52306 69 86
v4 v6
AS25192 32 54
v4 v6
AS52304 25 29
v4 v6
AS14650 6 7
v4
AS61455 6 6
v4 v6
AS35052 5 5
v4 v6
AS264798 5 5
v4 v6
AS6429 2 2
v4
AS112 1 1
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.