Skip to main content

AS45265

CSLOX-DOM-AS-AP

CSLOXINFO Transit AS with Domestic (National Internet Exchange)

Registry

Authoritative registration data

AS number
45265
Name
CSLOX-DOM-AS-AP
Organisation
CSLOXINFO Transit AS with Domestic (National Internet Exchange)
Country
Flag of Thailand TH Thailand
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS45265
Address families
BKNIX (Thailand): Bangkok 10,000 Mbps IPv4 · IPv6
CSL Thai-IX Bangkok: Main 100,000 Mbps IPv4 · IPv6
TRUE-IX 40,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 AS45265 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS45265 in AS paths

Observed upstreams
Families
AS63529 10 28
v6

No rows match “”.

Showing – of

Observed downstreams

8 networks seen after AS45265 in AS paths

Observed downstreams
Families
AS4750 55 586
v4 v6
AS9891 16 171
v4 v6
AS24429 1 8
v4 v6
AS58930 1 2
v4
AS139341 ACE-AS-AP 1 2
v4 v6
AS142299 1 2
v4 v6
AS45581 INFONET-THAI-TH-AP 1 1
v4
AS135511 1 1
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 68 746
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.