arXiv Database Migrates to Cloud, Enhancing Reliability and Scalability for Research Community

On October 28, 2026, arXiv, a prominent open-access repository for scientific preprints, is migrating its core database to the cloud. This move is a significant component of the arXiv-CE project, aimed at modernizing the platform's technology stack. The database, which has been hosted on Cornell University servers for 25 years, will transition to a cloud environment to enhance reliability, resilience, and scalability. This migration is crucial for the global research and technical community. By moving to the cloud, arXiv expects to improve its service delivery through stronger redundancy, automated backups, and faster disaster recovery. This directly translates to more consistent access to critical research papers and reduced risk of service disruptions. Furthermore, the cloud infrastructure will allow arXiv to scale its capacity more effectively to accommodate the continuous growth in submissions and readership without the limitations of physical hardware maintenance. This ensures that the platform can continue to serve as a vital resource for scientific advancement. This development aligns with a broader, well-established trend in cloud adoption, even among non-profit and academic institutions. Organizations are increasingly recognizing the operational benefits and enhanced capabilities that cloud platforms offer, moving beyond traditional on-premises infrastructure. The shift from managing physical servers to leveraging cloud services for improved uptime, data integrity, and cost-efficiency is a common driver across various sectors. The integration of cloud solutions for core services like databases is a testament to the maturity and reliability of cloud computing. In practice, this means practitioners can expect a more robust and responsive arXiv. While there will be a scheduled maintenance window on October 28th, during which arXiv will be in a "read-only" mode for approximately five hours, the long-term benefits outweigh this temporary disruption. Users should be aware of this brief downtime for login-dependent functions, but can anticipate a more stable platform afterward. This migration also serves as a case study for other institutions considering similar moves, demonstrating how careful planning and execution can transition critical, long-standing services to the cloud with minimal impact and significant long-term gains.