Hypixel status history
Current state: operational — “All Systems Operational” per https://status.hypixel.net (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Hypixel incidents last?
From 9 incidents with a vendor-posted start and resolve time. Longest on record: Minecraft Server Connection Issues — 7.0 days (2026-02-06 19:14 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 (9)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-15 07:45 UTC | SkyBlock Joining Disruption | resolved | critical | 2 h 02 min |
| 2026-07-08 15:03 UTC | SkyBlock Emergency Maintenance | resolved | critical | 6 h 43 min |
| 2026-07-01 17:18 UTC | SkyBlock Joining Disruption | resolved | minor | 10 h 06 min |
| 2026-06-23 11:10 UTC | Pit Emergency Maintenance | resolved | critical | 46 h 32 min |
| 2026-04-14 06:43 UTC | SkyBlock Profile Visibility | resolved | minor | 1 h 08 min |
| 2026-03-05 04:44 UTC | Players unable to login | resolved | major | 45 h 09 min |
| 2026-02-16 13:59 UTC | Emails not sending | resolved | minor | 1 h 16 min |
| 2026-02-06 19:14 UTC | Minecraft Server Connection Issues | resolved | minor | 7 d 0 h |
| 2025-10-03 16:52 UTC | Authentication issues for 1.8.9 players | resolved | minor | 3 d 18 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 Hypixel with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"hypixel"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}