Simply Hosting & Servers status history
Current state: maintenance — “Service Under Maintenance” per https://status.simplyhosting.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Simply Hosting & Servers incidents last?
From 6 incidents with a vendor-posted start and resolve time. Longest on record: Suspected fibre issue between sites - Network at risk. — 2.9 days (2026-07-10 09:21 UTC). Excluded, never estimated: 2 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (8)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-14 23:00 UTC | Hyper V Standalone maintenance | maintenance | maintenance | open |
| 2026-07-10 09:21 UTC | Suspected fibre issue between sites - Network at risk. | resolved | none | 2 d 22 h |
| 2026-05-15 12:23 UTC | Switch failure in 1 rack - Reading L20 | resolved | none | 1 h 04 min |
| 2026-03-27 12:41 UTC | Switch failure in 1 rack - Reading N17 | resolved | none | 4 h 28 min |
| 2026-02-03 09:27 UTC | Network Issue | resolved | none | 7 h 31 min |
| 2025-11-24 13:08 UTC | Network Maintenance | resolved | maintenance | 20 h 35 min |
| 2025-10-24 13:10 UTC | Switch Failure | resolved | minor | 2 h 44 min |
| 2025-10-02 13:36 UTC | Network Circuit Issues | resolved | none | 18 h 00 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Simply Hosting & Servers with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"simply-hosting-servers"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
