Skip to main content

AS141618

ACT-AS-ID

PT Asia Central Telematika

Registry

Authoritative registration data

AS number
141618
Name
ACT-AS-ID
Organisation
PT Asia Central Telematika
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS141618
103.174.66.0/24 IPv4 /24 not checked
103.46.198.0/24 IPv4 /24 RPKI not found

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 AS141618
Address families
AIX 1,000 Mbps IPv4 · IPv6
BIX Jakarta 10,000 Mbps IPv4 · IPv6
CXC Jakarta 10,000 Mbps IPv4
IIX-Jakarta 1,000 Mbps IPv4 · IPv6
JKT-IX: Main 10,000 Mbps IPv4 · IPv6
OpenIXP / NiCE 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 AS141618 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS141618 in AS paths

Observed upstreams
Families
AS35280 F5 16 24
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS141618 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

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