Enjin status history
Current state: operational — “All Systems Operational” per https://www.enjinstatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Enjin incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: Degraded access to Staking – Pool Overview in Enjin Wallet — 12.6 h (2025-08-20 03:07 UTC). Excluded, never estimated: 1 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 (5)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-20 09:30 UTC | Beam Claims Temporarily Unavailable | resolved | minor | 26 min |
| 2025-11-25 07:58 UTC | ENJ/EFI Token Claim Processing Temporarily Unavailable | resolved | maintenance | 7 d 0 h |
| 2025-09-11 02:54 UTC | Enjin Platform Cloud: Intermittent Server Errors | resolved | critical | 4 h 22 min |
| 2025-09-02 03:51 UTC | Metadata Service Outage Impacting NFT.io and Enjin Wallet | resolved | major | 2 h 50 min |
| 2025-08-20 03:07 UTC | Degraded access to Staking – Pool Overview in Enjin Wallet | resolved | minor | 12 h 37 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 Enjin with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"enjin"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
