Downtime
Service disruption detected
The AboutSharma network began experiencing a broad infrastructure outage affecting services hosted on the primary physical server.
Restoration, recovery & resilience
Critical services restored.Remaining work queued.
A physical SSD failure on October 2 took the AboutSharma network offline. Critical services were restored within hours on interim AWS infrastructure and the network has been stable since. Lower-priority services followed progressively, several rebuilt rather than simply restarted; professional recovery of the remaining mission-critical data is underway, and a few non-critical services are queued for restoration.
Confirmed online10 service groupsDocumented restoration milestones
Queued for restoration6 servicesLower priority; not started yet
Mission-critical recovery3 servicesData expected by November 1
Recovery quote$2,800 approx.Covered in full by the network
Mission-critical data recoveryOctober 7 development
A professional recovery path for the remaining data.
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 updateService restoration
What is operational
Status reflects the documented restoration updates through October 14. Dates below identify the recorded restoration or verification milestone for each service.
Reported operational10 service groups
| Service & recovery details | Reported state | Recovery milestone |
|---|---|---|
| business.aboutsharma.comNearly all data recovered; platform modernized. | Operational | |
| payslips.aboutsharma.comAll data recovered; rebuilt October 13. | Operational | |
| savings.aboutsharma.comRelaunched with an expanded feature set. | 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.
Incident response log
Recovery, step by step.
Chronological updates from October 2 through October 14, 2026. All times are Eastern Time (EDT, UTC-04:00). Approximate times and ranges are identified.
October 2, 2026
Detection, investigation, and interim infrastructureOperations
Recovery investigation temporarily deferred
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.
Investigation
Hardware investigation began
Active investigation began across the failed server hardware, storage device, boot behavior, and available recovery paths.
Investigation
Preliminary findings indicated SSD failure
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.
Root cause
Physical SSD failure 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.
The failure could not reasonably be recovered with the equipment and methods available personally. Retrieval of the underlying data would require professional laboratory-grade data recovery services.
Infrastructure
AWS EC2 interim recovery environment provisioned
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.
October 3, 2026
Reconstruction and progressive service restorationInfrastructure
Initial services returned and deployment automation began
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.
Infrastructure
LoRaWAN infrastructure reconstruction began
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.
Sensor connectivityChirpStackTelemetry pipelinesService dependenciesTailscaleLab-to-AWS communication
The temporary AWS EC2 instance was joined to the same Tailscale network so the cloud recovery environment could communicate securely with the required Purdue lab infrastructure.
Restored
First public services restored and verified
1.aboutsharma.com and www.aboutsharma.com were restored and verified as functional, marking the first major public recovery milestone.
Infrastructure
Major LoRaWAN networking and dependencies reconnected
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.
Restored
LoRaWAN restoration completed
lorawan.aboutsharma.com was fully restored and verified as operational.
Operations
Recovery break
After the overnight restoration work, Aryan stepped away for rest. No restoration work was performed during this period.
Recovery
Recovery work resumed
Service restoration resumed after the morning break, with remaining deployments being rebuilt and verified against the interim infrastructure.
Restored
Jazz service restored
jazz.aboutsharma.com was restored and verified as functional.
Restored
SyDAg restored and Squeaky Clean verified
sydag.aboutsharma.com was restored at approximately 2:15 PM. www.squeakyclean-ww.com was also verified as fully functional as of this update.
At this point, current recovery work was focused on business.aboutsharma.com.
Operations
Food and rest break
A planned break was taken before the next restoration block.
Recovery
Recovery continued across remaining services
Work continued across the remaining business services, with business.aboutsharma.com and arc.aboutsharma.com among the documented priorities.
Restored
Cloud Network Purdue fully restored
cloudnetworkpurdue.com was restored to its full operational state and verified as functional.
Restored
Business recovered and deployed successfully
business.aboutsharma.com was recovered successfully and deployed smoothly to the interim environment. Post-deployment verification confirmed the service was functioning as expected.
Eight public services are now confirmed restored and verified.
Data recovery
Recovered data now extends through August 3, 2026
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.
The estimate recorded at this point was 1:30 AM ET on October 4 for completing recovery of all data that could reasonably be recovered through available copies. This historical target preceded the professional recovery plan documented on October 7.
October 6, 2026
Essential services and data restorationService restoration
Most essential websites are back online
Most essential websites are now back online and operational. business.aboutsharma.com has been fully restored, with nearly all associated data successfully recovered.
Service restoration
Payslips restored with complete data recovery
payslips.aboutsharma.com is now fully operational. All associated data has been successfully recovered.
October 7, 2026
Deployment resilience and professional data recoveryInfrastructure milestone
Ansible deployment files refined and tested on a new server
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.
Mission-critical recovery
DriveSavers expresses strong confidence in recovering the remaining data
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.
Expected recovery target: no later than November 1, 2026. Recovery remains in progress.
October 8, 2026
Platform modernization and user experience improvementsPlatform modernization
Major services redesigned and their codebases modernized
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.
~2 millionOpenAI tokens
~2 millionAnthropic tokens
October 13, 2026
Rebuilt rather than restartedService rebuilt
Payslips rebuilt
payslips.aboutsharma.com was rebuilt and returned to service at approximately 2:30 PM on October 13. Rather than restarting the previous deployment, the recovery work was used as an opportunity to refresh the application.
October 14, 2026
Relaunched with more than it had beforeService relaunchLatest update
Savings relaunched with expanded functionality
savings.aboutsharma.com was brought online around 1:00 AM on October 14, returning with a significantly expanded feature set compared with its previous version. As with Payslips, the recovery was used to improve the service, not just to restore it.
Incident context
Cause and recovery strategy
Primary server SSD failure
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.
Interim infrastructure, repeatable deployments
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.
Daily incident record
System status history
AboutSharma NetworkHistory through October 14, 2026
October 2: Primary server outage following SSD failure.
October 3-14: Service and data recovery.
Earlier daily entries are retained in the interactive history.
OperationalRecoveryOutage
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.
Still pending
Queued for restoration
These lower-priority services remain queued for restoration. No restoration attempts have been made on them yet.
- Photos
- Storage
- Analytics
- Lost & Found
- Grafana
- pgAdmin
Postscript
Recovery context
The services and infrastructure that matter most operationally were restored with real urgency in the hours after the hardware failure. Once they were stable, the remaining lower-priority services were deliberately taken off emergency footing rather than worked on around the clock, and attention returned to academic, work, research, and other existing commitments.
A Fall Break trip to Austin, Texas, planned well in advance, ran from October 9 to October 13. Comparatively little infrastructure work was done during those days; the time was set aside for travel and personal plans. By then the important services were already back, and the systems still outstanding did not justify cancelling other commitments.
Recovery work resumed afterwards: Payslips was rebuilt on October 13 and Savings relaunched on October 14, both improved rather than simply restarted. The remaining non-critical services are queued for restoration, not abandoned, and will be brought back progressively.
As of October 14, 2026, this incident is mostly resolved. Critical services and most of the network have been operational since early October, Payslips and Savings have been rebuilt and relaunched, professional recovery of the remaining mission-critical data is expected by November 1, 2026, and six lower-priority services are queued for restoration. Current service health is on the live status page.
Mostly resolved