Enjin Outage History

Enjin had 5 outages in the last 2 years totaling 102h 43m of downtime — averaging 0.2 incidents per month.

There were 5 Enjin outages since June 13, 2025 totaling 102h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.enjinstatus.com

Critical September 11, 2025

Enjin Platform Cloud: Intermittent Server Errors

Detected by Pingoru: Sep 11, 2025, 02:54 AM UTC
Resolved: Sep 11, 2025, 07:17 AM UTC
Duration: 4h 22m

Affected: Enjin Mainnet

Timeline · 2 updates

investigating Sep 11, 2025, 02:54 AM UTC

Enjin Platform Cloud is experiencing intermittent “Server Error” responses and some sign-in attempts are failing or timing out. Affected functionality includes API requests and login. The technical team is investigating the cause and working to restore normal functionality. Apologies for the disruption.
resolved Sep 11, 2025, 07:17 AM UTC

A distributed denial-of-service (DDoS) attack targeting Enjin Platform Cloud was observed earlier and appears to have caused the intermittent availability issues. Enjin Platform Cloud's behavior appears normal at this time: login and API requests are succeeding. Further investigation into the earlier DDoS-related disruptions is ongoing, and mitigations will be applied as needed.

Read the full incident report →

Major September 2, 2025

Metadata Service Outage Impacting NFT.io and Enjin Wallet

Detected by Pingoru: Sep 02, 2025, 03:51 AM UTC
Resolved: Sep 02, 2025, 06:41 AM UTC
Duration: 2h 50m

Affected: Enjin WalletNFT.ioGovernance & Staking Interface

Timeline · 3 updates

investigating Sep 02, 2025, 03:51 AM UTC

Metadata Service is currently unavailable and returning errors on NFT.io and in the Enjin Wallet app, including the Staking interface. The technical team is investigating the cause and working to restore normal functionality. Apologies for the disruption.
investigating Sep 02, 2025, 04:07 AM UTC

We are continuing to investigate this issue.
resolved Sep 02, 2025, 06:41 AM UTC

This incident has been resolved.

Read the full incident report →

Minor August 20, 2025

Degraded access to Staking – Pool Overview in Enjin Wallet

Detected by Pingoru: Aug 20, 2025, 03:07 AM UTC
Resolved: Aug 20, 2025, 03:45 PM UTC
Duration: 12h 37m

Affected: Enjin Wallet

Timeline · 3 updates

investigating Aug 20, 2025, 03:07 AM UTC

An issue is preventing the Pool Overview screen in Enjin Wallet from loading for some mobile users. The technical team is currently investigating the cause and working to restore normal functionality. Apologies for the disruption.
investigating Aug 20, 2025, 03:44 PM UTC

We are continuing to investigate this issue.
resolved Aug 20, 2025, 03:45 PM UTC

This incident has been resolved.

Read the full incident report →

Notice August 7, 2025

Documentation Site Outage

Detected by Pingoru: Aug 07, 2025, 02:41 AM UTC
Resolved: Aug 07, 2025, 06:21 AM UTC
Duration: 3h 40m

Timeline · 3 updates

investigating Aug 07, 2025, 02:41 AM UTC

The documentation portal at https://docs.enjin.io is currently inaccessible. The technical team has been alerted and is actively investigating the issue to restore service as soon as possible.
monitoring Aug 07, 2025, 03:41 AM UTC

Access to the documentation portal at https://docs.enjin.io has been restored. The technical team is currently monitoring the service to ensure continued stability.
resolved Aug 07, 2025, 06:21 AM UTC

This incident has been resolved.

Read the full incident report →

Minor June 13, 2025

ENJ Staking Balance Display Bug (On-Chain Balances Unaffected)

Detected by Pingoru: Jun 13, 2025, 01:06 AM UTC
Resolved: Jun 16, 2025, 08:18 AM UTC
Duration: 3d 7h

Affected: Governance & Staking Interface

Timeline · 2 updates

investigating Jun 13, 2025, 01:06 AM UTC

We are aware of an issue causing incorrect ENJ values to be displayed to users staking with Enjin Wallet. The team is working on a fix. Please be aware the issue is only visual, and on-chain balance is not affected.
resolved Jun 16, 2025, 08:18 AM UTC

This incident has been resolved.

Read the full incident report →