Hidalgo Outage History

Hidalgo is up right now

Hidalgo had 2 outages in the last 2 years totaling 191h 58m of downtime — averaging 0.1 incidents per month.

There were 2 Hidalgo outages since September 21, 2025 totaling 191h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://hidalgodigital.statuspage.io

Minor June 20, 2026

Hub Invites Improvements

Detected by Pingoru
Jun 20, 2026, 04:20 PM UTC
Resolved
Jun 21, 2026, 05:25 PM UTC
Duration
1d 1h
Affected: HidalgoDigital.comEneko NetworkClient Dashboards
Timeline · 6 updates
  1. identified Jun 20, 2026, 04:20 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Jun 20, 2026, 04:23 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jun 20, 2026, 04:36 PM UTC

    Update implemented. Sites are restored. Enabling user invite permissions for registered accounts.

  4. monitoring Jun 21, 2026, 03:55 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jun 21, 2026, 05:25 PM UTC

    Invitation module established.

  6. postmortem Jun 21, 2026, 05:25 PM UTC

    Development, testing and deployment of a referrer module affected the memory caps in the server, pausing the delivery of assets at different intervals. The issue has been resolved with logs showing no further conflicts and all components are now operational.

Read the full incident report →

Minor September 21, 2025

Dashboards- Status Enablement

Detected by Pingoru
Sep 21, 2025, 04:00 PM UTC
Resolved
Sep 28, 2025, 02:54 PM UTC
Duration
6d 22h
Affected: Client Dashboards
Timeline · 3 updates
  1. identified Sep 21, 2025, 04:00 PM UTC

    Asset status enablement. Activation started in Client Dashboards; activation in other depencencies pending. Details: https://hidalgodigital.com/dashboards/issues/evaluate-kb/

  2. identified Sep 21, 2025, 04:01 PM UTC

    Activating site status per dependency.

  3. resolved Sep 28, 2025, 02:54 PM UTC

    This incident has been resolved.

Read the full incident report →