Skip to main content

AS203843

AS-XINGKAI

Xing-Kai Wang

Registry

Authoritative registration data

AS number
203843
Name
AS-XINGKAI
Organisation
Xing-Kai Wang
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

3

Total announced

4

Announced prefixes

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

Prefixes announced by AS203843
103.244.163.0/24 IPv4 /24 not checked
2a14:7580:900::/47 IPv6 /47 not checked
2a14:7580:901::/48 IPv6 /48 not checked
2a14:7580:902::/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 AS203843
Address families
STUIX 1,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 AS203843 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS203843 in AS paths

Observed upstreams
Families
AS32595 LIBERALLY-INTERNATIONAL 286 409
v4 v6
AS7720 SKYWOLF-AS-AP 254 360
v6
AS6939 HURRICANE 223 317
v4 v6
AS24482 SGGS-AS-AP 2 13
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS203843 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS38855 STUIX-AS-TW 1 2
v4 v6
AS59105 1 2
v4 v6
AS207705 JK-NETWORK 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.