To the authors and users of Jurnal Poliban services,

We regret to inform you that on Friday, May 17, 2024, our server experienced a serious security incident. Initial reports from the manager of Jurnal Poliban indicated an inability to upload documents, prompting our IT team to investigate. They discovered an illegal user disrupting the system, leading to system damage and kernel panic, resulting in data loss. We are tirelessly working to repair the damage, recover data from backups as of May 10, 2024, and implement additional security measures. However, due to a bug in the database backup application, there are limitations in restoring backup data to Ejurnal. We sincerely apologize for the inconvenience caused.

Here are the concrete impacts of the incident:

1. Loss of Publication Data: Publication data from Jurnal Poliban for Volume 8 Number 1, Volume 8 Number 2, Volume 9 Number 1, and Volume 9 Number 2 were lost due to the incident. This includes all articles that were published and recorded in the journal during that period.

2. Loss of Submission Data: Data regarding all submissions or article submissions made between 2023 and April 2024 were also lost. This includes all information related to articles that were submitted for consideration by the journal.

3. Uncertainty in Publication History: The loss of this data has resulted in uncertainty regarding the publication history of Jurnal Poliban during that period. Researchers, authors, and readers who rely on this historical data for reference or information retrieval may experience difficulties accessing or verifying previously published articles.

Recovery of publication data is underway, but the process history of these articles on OJS is lost, and can only be referenced in the email history on ejurnal saved in Gmail. The publication recovery process will be carried out gradually, and indexes will be corrected according to the indexing stored on Google Scholar, Garuda, and other indexing platforms.

If there's anything else I can assist you with, please let me know.