Service disruption detected
The AboutSharma network began experiencing a broad infrastructure outage affecting services hosted on the primary physical server.
Restoration, recovery & resilience
Most essential websites are back online following the October 2 SSD failure. Deployment automation and major platforms have been improved, while professional recovery of the remaining mission-critical data is the next priority.
DriveSavers in California expressed strong confidence in recovering data from the failed storage device. This is particularly important for three mission-critical services whose remaining data cannot be reconstructed from existing backups alone.
View the recovery updateStatus reflects the documented restoration updates through October 8. Dates below identify the recorded restoration or verification milestone for each service.
| Service & recovery details | Reported state | Recovery milestone |
|---|---|---|
| business1.aboutsharma.comNearly all data recovered; platform modernized. | Operational | |
| payslips.aboutsharma.comAll data recovered; platform modernized. | Operational | |
| 1.aboutsharma.com / one.aboutsharma.comRestored; platform modernized on October 8. | Operational | |
| www.aboutsharma.comMain website restored and verified. | Operational | |
| lorawan.aboutsharma.comIoT infrastructure restored and verified. | Operational | |
| jazz.aboutsharma.comRestored and verified as functional. | Operational | |
| sydag.aboutsharma.comRestored and verified as functional. | Operational | |
| www.squeakyclean-ww.comVerified as fully functional by the milestone shown. | Operational | |
| cloudnetworkpurdue.comFully restored and verified. | Operational |
1.aboutsharma.com and one.aboutsharma.com are shown together as one service group. The complete incident timeline records subsequent platform and data recovery developments.
Chronological updates from October 2 through October 8, 2026. All times are Eastern Time (EDT, UTC-04:00). Approximate times and ranges are identified.
The AboutSharma network began experiencing a broad infrastructure outage affecting services hosted on the primary physical server.
Pre-existing academic commitments, including classes and examinations, prevented a full hardware investigation or server redeployment effort during this window. No material recovery changes were made during this period.
Active investigation began across the failed server hardware, storage device, boot behavior, and available recovery paths.
Testing increasingly pointed toward a physical failure of the server's SSD rather than an application, operating-system, networking, or routine configuration problem.
Additional hardware verification was pursued before treating the SSD failure as confirmed.
Following additional consultation and hands-on testing with technically experienced Purdue upperclassmen and peers, the SSD was independently tested using external SSD enclosures and other available hardware.
Because professional SSD recovery and physical server replacement would take substantially longer, restoration of public services was decoupled from recovery of the failed hardware.
An Amazon Web Services EC2 instance was provisioned as temporary infrastructure and became the foundation of the interim recovery environment.
The first public-facing services began returning online. At approximately the same time, Ansible deployment notebooks and playbooks began being developed so restoration could move away from one-off manual configuration toward a repeatable deployment process.
Restoring lorawan.aboutsharma.com required rebuilding more than the public website. Work returned to the Purdue lab to reconnect the supporting IoT environment and its dependencies.
1.aboutsharma.com and www.aboutsharma.com were restored and verified as functional, marking the first major public recovery milestone.
After roughly four hours of reconstruction work, the major networking, telemetry, service-dependency, and secure lab-to-AWS communication components required for the LoRaWAN deployment had been rebuilt or reconnected.
lorawan.aboutsharma.com was fully restored and verified as operational.
After the overnight restoration work, Aryan stepped away for rest. No restoration work was performed during this period.
Service restoration resumed after the morning break, with remaining deployments being rebuilt and verified against the interim infrastructure.
jazz.aboutsharma.com was restored and verified as functional.
sydag.aboutsharma.com was restored at approximately 2:15 PM. www.squeakyclean-ww.com was also verified as fully functional as of this update.
A planned break was taken before the next restoration block.
Work continued across the remaining business services, with business.aboutsharma.com and arc.aboutsharma.com among the documented priorities.
cloudnetworkpurdue.com was restored to its full operational state and verified as functional.
business1.aboutsharma.com was recovered successfully and deployed smoothly to the interim environment. Post-deployment verification confirmed the service was functioning as expected.
Data has been successfully recovered through August 3, 2026. Material after that date is being thoroughly investigated across multiple remote servers and devices to identify every recoverable copy or fragment.
Before any recovered material is accepted back into the environment, its integrity is being scrutinized using industry-standard validation practices.
Most essential websites are now back online and operational. business1.aboutsharma.com has been fully restored, with nearly all associated data successfully recovered.
payslips.aboutsharma.com is now fully operational. All associated data has been successfully recovered.
The Server Infrastructure Ansible files have been significantly refined and successfully tested on one of our new servers.
This is an important step toward making future deployments, migrations, and disaster recovery considerably faster and more reliable through a repeatable deployment process.
Following a discussion with DriveSavers in California about the failed storage device, their team expressed strong confidence that their engineers can recover the remaining data.
This recovery is particularly important for three mission-critical services whose remaining data cannot be reconstructed through our existing backups alone.
The final recovery quote is approximately $2,800. The full cost is being covered by AboutSharma Network, funded by Aryan.
Several major services have undergone substantial redesigns and codebase improvements:
The redevelopment has addressed inefficient, dated, and increasingly difficult-to-maintain parts of the original codebases. The affected platforms have now been modernized, streamlined, and improved across infrastructure and user experience.
The work has involved approximately 2 million OpenAI tokens and 2 million Anthropic tokens across code review, refactoring, debugging, infrastructure work, and UI/UX improvements.
A physical SSD failure took the server hosting these services offline on October 2. Hardware testing and independent checks established that retrieval of the underlying data required professional laboratory recovery.
Public services were progressively rebuilt and verified on AWS EC2 while hardware and data recovery proceeded. The Ansible deployment files have since been refined and successfully tested on one of the new servers.
October 2: Primary server outage following SSD failure.
October 3-8: Active service and data recovery.
Earlier daily entries are retained in the interactive history.
One status per calendar day. Earlier entries are retained from the published history; recovery days include services already brought back online.
Hover or tap a day to view its record. With the history focused, use Left/Right arrows, Home/End, and Escape.
The recovery incident remains open. Most essential services are operational. Professional recovery of the remaining mission-critical data continues, with an expected target of November 1, 2026.
Incident open