We identified the root cause of the second outage to be related to the database servers. Due to a power fluctuation, the servers crashed, automatically triggering the 503 page to be declared. We found the issue, and have patched it. This may occur again, and we will work more efficiently in patching it up.

We have yet again faced a service outage. We have checked prior factors, but this time a new factor is responsible. We have partially identified the factor and are actively working to resolve it.

We identified the issue to be caused by a misconfigured web interface. We have patched the issue and all systems are now functional.

Our IN web server is currently facing a service disruption. We are working on identifying the issue.