Introduction
I use Spectrum as my ISP. As the web server is inside my own network, so long as the server is running, evrything looks good. I cannot tell if it is available to the public. On March 21, 2026, and again on March 22, 2026, I received emails from users saying my sites were offline. When I checked, it appears that Spectrum had reset the router and removed port forwarding to the server on both 80 (HTTP) and 443 (HTTPS) ports.
Worse still, when I checked the server logs towards the end of April 2026, I found although the server was running, no one could reach the site for part of the April 15th, the whole of the 16th - 21st, and part of April 22nd.
On April 22, 2026, I created a free account on Uptime Robot which should inform me when the sites are not accessible to the wider web.
This page was written to show the uptime statistics for the server and why it was down.
Uptime
This graph was drawn with the Google Visualizations API. Google uses this API for a lot of its own graphs, and uses this Google Sheet. The statistics come from those provided by Uptime Robot.
Downtime
| Date | Time Down | Reason |
| June 11, 2026 | 15m, 31s | Spectrum ISP outage |
| June 1, 2026 | 5m, 3s | From Event Viewer - ID 41 - The system rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. |
| May 23, 2026 | 5m, 5s | BIOS update |
Information
| Downtime Allowed | |||
|---|---|---|---|
| Uptime % | Per Year | Per Month | Per Week |
| 90% (one nine) | 36.5 days | 72 hours | 16.8 hours |
| 99% (two nines) | 3.65 days | 7.2 hours | 1.68 hours |
| 99.9% (three nines) | 8.77 hours | 43.8 min | 10.1 min |
| 99.99% (four nines) | 52.6 min | 4.38 min | 1.01 min |
| 99.999% (five nines) | 5.26 min | 26.3 sec | 6.05 sec |
| 99.9999% (six nines) | 31.6 sec | 2.63 sec | 0.6 sec |
Event Viewer
Windows Event Viewer provides a lot of information.
Windows Event Viewer
Choose Windows Logs > System from the left-hand menu. If you know the approximate date and time a particular shutdown occurred then simply scroll down the event you are interested in. If you do not, then click on Filter Current Log in the right-hand menu and add 41, 1074, 1076, 6005, 6006, 6008 to the Event ID field. Click on OK.
Windows Event Viewer filter
The main window will then change to show the appropriate event IDs...
Filtered Windows Event Viewer
| Event ID | Description |
| 41 | The device did not restart correctly using a clean shutdown first. This event could be caused if the computer stopped responding, crashed, or lost power unexpectedly. |
| 1074 | The system has been shutdown properly by a user or process. Including when it was shut down using the Start menu or CTRL+ALT+DEL was pressed. |
| 1076 | Follows after Event ID 6008 and means that the first user with shutdown privileges logged on to the server after an unexpected restart or shutdown and specified the cause. |
| 6005 | The Event Log service was started. Indicates the system startup. |
| 6006 | The Event Log service was stopped. Indicates the proper system shutdown, usually after Event ID 1074. |
| 6008 | After an improper shutdown this shows the shutdown was unexpected, usually after Event ID 41. |