Skip to main content

AS150158

PHS-AS-AP

PHSS CAM INDO CO,. LTD.

Registry

Authoritative registration data

AS number
150158
Name
PHS-AS-AP
Organisation
PHSS CAM INDO CO,. LTD.
Country
Flag of Cambodia KH Cambodia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS150158
185.223.154.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 AS150158
Address families
SGIX: Peering LAN 1,000 Mbps IPv4

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 AS150158 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS150158 in AS paths

Observed upstreams
Families
AS133210 ENTECHNOLOGIES-AS-AP 223 290
v4
AS6939 HURRICANE 32 36
v4
AS9304 HUTCHISON-AS-AP 1 1
v4
AS20326 TERASWITCH 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS150158 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v4
AS17639 CONVERGE-AS 1 1
v4
AS18106 VIEWQWEST-SG-AP 1 1
v4
AS35280 F5 1 1
v4
AS38001 NEWMEDIAEXPRESS-AS-AP 1 1
v4
AS49544 i3Dnet 1 1
v4
AS199524 GCORE 1 1
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.