Skip to main content

AS53727

AS-PENGUIN

Penguin Networks

Registry

Authoritative registration data

AS number
53727
Name
AS-PENGUIN
Organisation
Penguin Networks
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

7

Total announced

9

Announced prefixes

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

Prefixes announced by AS53727
168.151.27.0/24 IPv4 /24 not checked
23.172.56.0/24 IPv4 /24 not checked
2602:f982:200::/44 IPv6 /44 not checked
2602:f982::/44 IPv6 /44 not checked
2602:f982:101::/48 IPv6 /48 RPKI valid
2602:f982:102::/48 IPv6 /48 not checked
2602:f982:120::/48 IPv6 /48 not checked
2602:f982:200::/48 IPv6 /48 not checked
2602:f982::/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

Internet Exchange memberships listed for AS53727
Address families
FogIXP 1,000 Mbps IPv6
ONIX 100 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 AS53727 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS53727 in AS paths

Observed upstreams
Families
AS21700 NEPTUNE-NETWORKS 471 2,332
v4 v6
AS20473 AS-VULTR 251 453
v4 v6
AS34927 iFog-GmbH 243 346
v6
AS47498 FogIXP 3 3
v6
AS39351 ESAB-AS 2 2
v6
AS205794 RTTW-AS 1 1
v6
AS209022 Tschajera-Limited 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS53727 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8298 IPNG 1 1
v6
AS41666 PYRO-AS 1 1
v6
AS58299 OPENFACTORY-AS 1 1
v6
AS60326 DEADBEEF-AS 1 1
v6
AS209823 ENKI-AS 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. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.