Hiro Outage History

Hiro is up right now

Pingoru has recorded 73 incidents for Hiro: 73 in the last 12 months and 0 in the last 90 days.

Source: status.hiro.so

73incidents recorded
73last 12 months
0last 90 days
3 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Hiro in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202647 of 720 (1%)
May 202649 of 744 (1%)
June 20261819 of 720 (3%)
July 202611 of 744 (0%)
August 202610 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 28 (0%)

Incidents, newest first

Critical January 16, 2026 Status Page Incident 25s platform.hiro.so

Started Jan 16, 2026, 06:09 PM UTC· resolved Jan 16, 2026, 06:10 PM UTC

  1. investigating Jan 16, 2026, 06:09 PM UTC

    Status page is currently showing downtime without an incident

  2. resolved Jan 16, 2026, 06:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 11, 2026 Mainnet Stacks Blockchain API Errors 20m Stacks Blockchain API, explorer.hiro.so

Started Jan 11, 2026, 02:04 PM UTC· resolved Jan 11, 2026, 02:25 PM UTC

  1. investigating Jan 11, 2026, 02:04 PM UTC

    We are investigating an issue with the Mainnet API service that began at Jan 11, 2026, 9:04 AM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. resolved Jan 11, 2026, 02:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 3, 2026 Mainnet Stacks Core Outage 1h 17m Stacks Blockchain API

Started Jan 03, 2026, 03:10 AM UTC· resolved Jan 03, 2026, 04:28 AM UTC

  1. investigating Jan 03, 2026, 03:10 AM UTC

    We are investigating an issue with the Mainnet Stacks Blockchain Node that began at Jan 2, 2026, 10:10 PM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the Testnet API may be impacted. We will share more details as additional information becomes available.

  2. resolved Jan 03, 2026, 04:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 27, 2025 Mainnet Stacks Blockchain API Errors 5h 3m Stacks Blockchain API, explorer.hiro.so

Started Dec 27, 2025, 10:19 AM UTC· resolved Dec 27, 2025, 03:23 PM UTC

  1. investigating Dec 27, 2025, 10:19 AM UTC

    We are investigating an issue with the Mainnet API service that began at Dec 27, 2025, 5:19 AM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. resolved Dec 27, 2025, 03:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 25, 2025 Mainnet API Block Progression Stalled 22h 48m Stacks Blockchain API, explorer.hiro.so

Started Dec 25, 2025, 05:44 PM UTC· resolved Dec 26, 2025, 04:32 PM UTC

  1. investigating Dec 25, 2025, 05:44 PM UTC

    We're investigating a stall in block progression for the Mainnet Stacks Blockchain API.

  2. monitoring Dec 25, 2025, 06:31 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 26, 2025, 04:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 22, 2025 Testnet Stacks Blockchain API Outage 29m Stacks Blockchain API, explorer.hiro.so

Started Dec 22, 2025, 07:53 PM UTC· resolved Dec 22, 2025, 08:22 PM UTC

  1. investigating Dec 22, 2025, 07:53 PM UTC

    We are investigating degraded performance with the Stacks Blockchain API in Testnet that began at Dec 22, 2025, 2:53 PM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. monitoring Dec 22, 2025, 08:05 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 22, 2025, 08:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 22, 2025 Mainnet Stacks Blockchain API Errors 1h 7m Stacks Blockchain API, explorer.hiro.so

Started Dec 22, 2025, 04:45 AM UTC· resolved Dec 22, 2025, 05:53 AM UTC

  1. investigating Dec 22, 2025, 04:45 AM UTC

    We are investigating an issue with the Mainnet API service that began at Dec 21, 2025, 11:45 PM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. resolved Dec 22, 2025, 05:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 19, 2025 Mainnet API Block Progression Stalled 32m Stacks Blockchain API, explorer.hiro.so

Started Dec 19, 2025, 02:44 PM UTC· resolved Dec 19, 2025, 03:16 PM UTC

  1. investigating Dec 19, 2025, 02:44 PM UTC

    We're investigating a stall in block progression for the Mainnet Stacks Blockchain API.

  2. identified Dec 19, 2025, 02:50 PM UTC

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

  3. resolved Dec 19, 2025, 03:16 PM UTC

    This incident has been resolved, and a post-mortem will be added later today.

  4. postmortem Dec 19, 2025, 05:45 PM UTC

    # Summary On December 19, 2025, at approximately 8:47 AM ET, the mainnet Stacks Blockchain API stopped advancing at Bitcoin block 928,558 and Stacks block 5,385,227. This stall impacted the Explorer and any services relying on the mainnet Stacks Blockchain API. Block ingestion was restored at approximately 9:46 AM ET, after which the API resumed syncing. The API fully caught up to chain tip by 10:11 AM ET. # Impact The stall affected all consumers of the mainnet Stacks Blockchain API, including: * The Stacks Explorer * Chainhooks v2 * Any downstream services dependent on API block progression Detection and mitigation were delayed due to a misconfigured silenced alert in Hiro’s alerting system. As a result, engineers were notified later than expected, extending the duration of user impact. # Root cause The definitive root cause is still under investigation. However, initial analysis indicates that the Stacks Blockchain API entered an unexpected internal state regarding an internal block-synchronization system it depends on, preventing further block progression. Recovery required manual intervention at the database level to reset the API’s block sync state. For context, Hiro operates a custom internal block-sync system to improve sync performance and recovery behavior for our API services. We do not believe this condition would affect users syncing directly from a standard Stacks Core node. # Resolution Once discovered, action was immediately taken to communicate, diagnose, and rectify the mainnet Stacks Blockchain API stall via manual database intervention. Additionally, the silenced alert that should have notified Hiro engineers has been corrected. Should this happen again before a permanent fix is in place, our engineers will be notified appropriately and able to restore block progression much faster. Further action will be taken to verify any issues in how the Stacks Blockchain API interacts with our block-sync system and implement a permanent fix. # Action Items Below are some items Hiro will complete to prevent another mainnet Stacks Blockchain API stall under similar conditions, and to improve the speed at which it was recovered: * Investigate any issues in the Stacks Blockchain API that would lead to an unexpected state with our internal block-sync system, and implement a permanent fix. * Update any critical alerts to reduce the need for silencing specific instances of them, reducing the possibility for human error. * Add a new alert\(s\) for any gaps found.

Read the full incident report →

Critical December 15, 2025 Mainnet Chainhooks Outage 1h 24m Stacks Blockchain API, Chainhook

Started Dec 15, 2025, 04:08 PM UTC· resolved Dec 15, 2025, 05:32 PM UTC

  1. investigating Dec 15, 2025, 04:08 PM UTC

    We are investigating an issue with the Mainnet Chainhooks service that began at Dec 15, 2025, 11:08 AM ET. Additional information will be shared once it becomes available.

  2. monitoring Dec 15, 2025, 04:20 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 15, 2025, 05:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 12, 2025 Mainnet Stacks Blockchain API Errors 15m Stacks Blockchain API, explorer.hiro.so

Started Dec 12, 2025, 11:43 PM UTC· resolved Dec 12, 2025, 11:58 PM UTC

  1. investigating Dec 12, 2025, 11:43 PM UTC

    We are investigating an issue with the Mainnet API service that began at Dec 12, 2025, 6:43 PM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. resolved Dec 12, 2025, 11:58 PM UTC

    Incident is non impacting

Read the full incident report →

Major December 12, 2025 Platform Backend Errors 5m Backend

Started Dec 12, 2025, 04:17 PM UTC· resolved Dec 12, 2025, 04:22 PM UTC

  1. investigating Dec 12, 2025, 04:17 PM UTC

    We are investigating an issue with the Platform Backend service that began at Dec 12, 2025, 11:17 AM ET. Additional information will be shared once it becomes available.

  2. resolved Dec 12, 2025, 04:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 11, 2025 Mainnet Stacks Blockchain API Errors 4h 23m Stacks Blockchain API, explorer.hiro.so

Started Dec 11, 2025, 04:01 PM UTC· resolved Dec 11, 2025, 08:24 PM UTC

  1. investigating Dec 11, 2025, 04:01 PM UTC

    We are investigating an issue with the Mainnet API service that began at Dec 11, 2025, 10:57 AM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. monitoring Dec 11, 2025, 04:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 11, 2025, 08:24 PM UTC

    Upon review, we found some network instability within our infrastructure that was causing the Stacks Blockchain API to delay block ingestion. We believe to have found and resolved the underlying cause.

Read the full incident report →

Major December 10, 2025 Mainnet Stacks Blockchain API Errors – Stacks Blockchain API, explorer.hiro.so

Started Dec 10, 2025, 07:38 PM UTC· resolved Dec 10, 2025, 07:38 PM UTC

  1. investigating Dec 10, 2025, 07:33 PM UTC

    We are investigating an issue with the Mainnet API service that began at Dec 10, 2025, 2:33 PM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. resolved Dec 10, 2025, 07:46 PM UTC

    After review, we found some services were experiencing memory pressure, leading to a reduction in blocks processed by our Stacks Blockchain API. The memory pressure has been addressed, and this incident has been resolved.

Read the full incident report →

Major December 10, 2025 Mainnet Stacks Blockchain API Errors 1h 6m Stacks Blockchain API, explorer.hiro.so

Started Dec 10, 2025, 05:24 PM UTC· resolved Dec 10, 2025, 06:31 PM UTC

  1. investigating Dec 10, 2025, 05:24 PM UTC

    We are investigating an issue with the Mainnet API service that began at Dec 10, 2025, 12:17 PM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. resolved Dec 10, 2025, 06:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 4, 2025 Mainnet Stacks Blockchain API Errors 28m Stacks Blockchain API, explorer.hiro.so

Started Dec 04, 2025, 09:56 PM UTC· resolved Dec 04, 2025, 10:25 PM UTC

  1. investigating Dec 04, 2025, 09:56 PM UTC

    We are investigating an issue with the Mainnet API service that began at Dec 4, 2025, 4:56 PM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. resolved Dec 04, 2025, 10:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 29, 2025 Mainnet Chainhooks Outage 43s Stacks Blockchain API, Chainhook

Started Nov 29, 2025, 01:58 AM UTC· resolved Nov 29, 2025, 01:59 AM UTC

  1. investigating Nov 28, 2025, 10:14 PM UTC

    We are investigating an issue with the Mainnet Chainhooks service that began at Nov 28, 2025, 5:14 PM ET. Additional information will be shared once it becomes available.

  2. investigating Nov 29, 2025, 01:58 AM UTC

    We are investigating this issue

  3. resolved Nov 29, 2025, 01:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 26, 2025 Mainnet Stacks Blockchain API Errors 25m Stacks Blockchain API, explorer.hiro.so

Started Nov 26, 2025, 03:16 PM UTC· resolved Nov 26, 2025, 03:42 PM UTC

  1. investigating Nov 26, 2025, 03:16 PM UTC

    We are investigating an issue with the Mainnet API service that began at Nov 26, 2025, 10:16 AM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. investigating Nov 26, 2025, 03:41 PM UTC

    We are continuing to investigate this issue.

  3. resolved Nov 26, 2025, 03:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 26, 2025 Platform Frontend Outage – platform.hiro.so

Started Nov 26, 2025, 08:32 AM UTC· resolved Nov 26, 2025, 08:32 AM UTC

  1. investigating Nov 26, 2025, 08:30 AM UTC

    We are investigating an issue with the Platform Frontend service that began at Nov 26, 2025, 3:30 AM ET. Additional information will be shared once it becomes available.

  2. resolved Nov 26, 2025, 02:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 22, 2025 Mainnet Stacks Blockchain API Errors 11m Stacks Blockchain API, explorer.hiro.so

Started Nov 22, 2025, 08:07 AM UTC· resolved Nov 22, 2025, 08:18 AM UTC

  1. investigating Nov 22, 2025, 08:07 AM UTC

    We are investigating an issue with the Mainnet API service that began at Nov 22, 2025, 3:07 AM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. resolved Nov 22, 2025, 08:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 18, 2025 Testnet Stacks Blockchain API Outage 2h 23m Stacks Blockchain API, explorer.hiro.so

Started Nov 18, 2025, 02:35 PM UTC· resolved Nov 18, 2025, 04:58 PM UTC

  1. investigating Nov 18, 2025, 02:35 PM UTC

    We are investigating degraded performance with the Stacks Blockchain API in Testnet that began at Nov 18, 2025, 9:29 AM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. monitoring Nov 18, 2025, 02:42 PM UTC

    The issue has been identified as a Cloudflare network outage. We will continue to monitor the situation as Cloudflare remediates the issue. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  3. monitoring Nov 18, 2025, 03:10 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Nov 18, 2025, 04:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 18, 2025 Platform Frontend Outage 3h 57m platform.hiro.so

Started Nov 18, 2025, 01:00 PM UTC· resolved Nov 18, 2025, 04:58 PM UTC

  1. investigating Nov 18, 2025, 01:00 PM UTC

    We are investigating an issue with the Platform Frontend service that began at Nov 18, 2025, 8:00 AM ET. Additional information will be shared once it becomes available.

  2. monitoring Nov 18, 2025, 01:23 PM UTC

    The issue has been identified as a Cloudflare network outage. We will continue to monitor the situation as Cloudflare remediates the issue. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  3. monitoring Nov 18, 2025, 02:20 PM UTC

    Cloudflare's outage is still impacting Hiro services. We will continue to monitor the situation to ensure our services are restored as soon as Cloudflare's incident is resolved.

  4. monitoring Nov 18, 2025, 03:11 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Nov 18, 2025, 04:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 18, 2025 Mainnet Token Metadata API Outage 4h 29m Token Metadata API

Started Nov 18, 2025, 12:28 PM UTC· resolved Nov 18, 2025, 04:58 PM UTC

  1. investigating Nov 18, 2025, 12:28 PM UTC

    We are investigating an issue with the Mainnet Token Metadata API that began at Nov 18, 2025, 7:27 AM ET. Additional information will be shared once it becomes available.

  2. monitoring Nov 18, 2025, 12:45 PM UTC

    The issue has been identified as a Cloudflare network outage. We will continue to monitor the situation as Cloudflare remediates the issue. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  3. monitoring Nov 18, 2025, 01:27 PM UTC

    Cloudflare's outage is still impacting Hiro services. We will continue to monitor the situation to ensure our services are restored as soon as Cloudflare's incident is resolved.

  4. monitoring Nov 18, 2025, 02:20 PM UTC

    Cloudflare's outage is still impacting Hiro services. We will continue to monitor the situation to ensure our services are restored as soon as Cloudflare's incident is resolved.

  5. monitoring Nov 18, 2025, 03:11 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Nov 18, 2025, 04:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 18, 2025 Mainnet Stacks Blockchain API Outage 4h 30m Stacks Blockchain API, explorer.hiro.so

Started Nov 18, 2025, 12:27 PM UTC· resolved Nov 18, 2025, 04:58 PM UTC

  1. investigating Nov 18, 2025, 12:27 PM UTC

    We are investigating an issue with the Mainnet API service that began at Nov 18, 2025, 7:27 AM ET. Data retrieved from this API’s endpoints may be several blocks behind. The Stacks Explorer, wallets, and any services using the API may be impacted. We will share more details as additional information becomes available.

  2. monitoring Nov 18, 2025, 12:45 PM UTC

    The issue has been identified as a Cloudflare network outage. We will continue to monitor the situation as Cloudflare remediates the issue. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  3. monitoring Nov 18, 2025, 01:27 PM UTC

    Cloudflare's outage is still impacting Hiro services. We will continue to monitor the situation to ensure our services are restored as soon as Cloudflare's incident is resolved.

  4. monitoring Nov 18, 2025, 02:21 PM UTC

    Cloudflare's outage is still impacting Hiro services. We will continue to monitor the situation to ensure our services are restored as soon as Cloudflare's incident is resolved.

  5. monitoring Nov 18, 2025, 03:11 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Nov 18, 2025, 04:58 PM UTC

    This incident has been resolved.

Read the full incident report →