Skip to main content

AS131447

POP-IDC-TH

POPIDC powered by CSLoxinfo

Registry

Authoritative registration data

AS number
131447
Name
POP-IDC-TH
Organisation
POPIDC powered by CSLoxinfo
Country
Flag of Thailand TH Thailand
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

2

Total announced

10

Announced prefixes

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

Prefixes announced by AS131447
103.246.16.0/22 IPv4 /22 not checked
103.7.56.0/22 IPv4 /22 RPKI valid
150.107.28.0/22 IPv4 /22 not checked
43.254.132.0/22 IPv4 /22 not checked
103.253.134.0/23 IPv4 /23 not checked
103.253.134.0/24 IPv4 /24 not checked
103.253.135.0/24 IPv4 /24 RPKI valid
150.107.28.0/24 IPv4 /24 not checked
2401:5700::/32 IPv6 /32 RPKI valid
2401:5700:2000::/40 IPv6 /40 RPKI valid

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 AS131447
Address families
BKNIX (Thailand): Bangkok 10,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 AS131447 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS131447 in AS paths

Observed upstreams
Families
AS9891 CSLOX-IDC-AS-AP 284 2,188
v4 v6
AS135063 POPNIXCO-AS-AP 348 932
v4 v6
AS6939 HURRICANE 260 530
v4 v6
AS59238 INOX-TH 117 148
v4
AS63529 BKNIX-RS-AP 15 29
v4 v6
AS9505 TWGATE-AP 2 6
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS131447 in AS paths

Observed downstreams
Families
AS136523 COLODEE-AS-AP 61 265
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 23
v4 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.