PloxHost status history
Current state: operational — “All Systems Operational” per https://status.plox.host (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do PloxHost incidents last?
From 15 incidents with a vendor-posted start and resolve time. Longest on record: Minecraft Server Startup Service Disruption — 3.0 days (2025-08-12 19:54 UTC). Excluded, never estimated: nothing. 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 (15)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-01 16:49 UTC | Game Panel Unavailable | resolved | critical | 1 h 31 min |
| 2026-07-18 20:41 UTC | Full disk errors eu-finland-mc-bu78.ploxhost.com | resolved | minor | 5 h 40 min |
| 2026-06-27 21:53 UTC | CDN Offline | resolved | major | 25 min |
| 2026-04-03 15:42 UTC | Client Area unreachable | resolved | minor | 2 h 25 min |
| 2025-12-31 05:09 UTC | Emails not working | resolved | none | 2 d 2 h |
| 2025-11-02 03:52 UTC | Registry Downtime | resolved | minor | 17 h 39 min |
| 2025-10-29 13:40 UTC | Game Panel Downtime | resolved | major | 8 min |
| 2025-10-12 22:03 UTC | Game Panel Downtime | resolved | critical | 29 min |
| 2025-10-12 20:10 UTC | Registry Intermittence | resolved | major | 42 min |
| 2025-10-08 11:06 UTC | Game Panel Downtime | resolved | critical | 10 h 10 min |
| 2025-10-03 11:47 UTC | Billing Website Downtime | resolved | major | 7 min |
| 2025-09-27 13:45 UTC | Registry Issues | resolved | none | 2 h 40 min |
| 2025-09-13 16:29 UTC | Registry Issues | resolved | minor | 3 h 04 min |
| 2025-09-06 18:11 UTC | Connectivity Issues – Finland (EU) Nodes | resolved | none | 14 min |
| 2025-08-12 19:54 UTC | Minecraft Server Startup Service Disruption | resolved | minor | 2 d 23 h |
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 PloxHost with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"ploxhost"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}