Skip to main content

AS23347

ZYC

ZYC Network LLC

Registry

Authoritative registration data

AS number
23347
Name
ZYC
Organisation
ZYC Network LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

6

Total announced

7

Announced prefixes

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

Prefixes announced by AS23347
23.156.153.0/24 IPv4 /24 not checked
2602:814:f000::/40 IPv6 /40 not checked
2602:814:f00c::/46 IPv6 /46 not checked
2602:814:f00a::/48 IPv6 /48 not checked
2602:814:f00c::/48 IPv6 /48 not checked
2602:814:f014::/48 IPv6 /48 not checked
2602:f921::/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 AS23347
Address families
Kent Internet Exchange Point 10,000 Mbps IPv6
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv4 · IPv6
ZXIX Hong Kong 1,024 Mbps 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 AS23347 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS23347 in AS paths

Observed upstreams
Families
AS3204 XTOM-V-PS 244 797
v6
AS142064 VERGETEL1-AS-AP 213 455
v6
AS17433 HNSL-AS-AP 241 296
v4
AS44324 MOEDOVE-AS 216 294
v6
AS6939 HURRICANE 100 133
v6
AS25091 IP-Max 3 24
v6
AS48646 STEFAN6 1 4
v6
AS401753 BIXCE 1 4
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS23347 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

10 adjacencies that may be an artefact of collector peering

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.