> For the complete documentation index, see [llms.txt](https://help.simnetonline.com/blog/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.simnetonline.com/blog/2014-posts/planned-maintenance-downtime-january-9th-2015-3-6am-central.md). # Planned Maintenance Downtime – January 9th, 2015 @ 3-6AM Central SIMnet will be unavailable Friday, January 9th, 2015 from 3:00AM – 6:00AM Central. We typically try to do planned maintenance on Sunday mornings, but this is the only maintenance slot available with our hosting provider before the Spring semester kicks into high gear. During the late December maintenance we became aware of an issue with the BIOS firmware running on the database hardware. In order to better control the internal temperature of the server the firmware needs an upgrade. Also, as a precautionary measure we’re replacing the CPU’s that have a history of temperature spikes. This maintenance is necessary to ensure reliability and scalability for the upcoming semester. Sincerely,\ SIMnet Product Team --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.simnetonline.com/blog/2014-posts/planned-maintenance-downtime-january-9th-2015-3-6am-central.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.