StoneProof Outage History

StoneProof is up right now

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

Source: stoneprooflabs.statuspage.io

5incidents recorded
5last 12 months
0last 90 days
4 hourstypical duration

Incidents, newest first

Notice March 18, 2026 System upgrade 9h 13m Blockchain Explorer, Organization Registry, Mineral Lifecycle Tracking

Started Mar 18, 2026, 08:16 AM UTC· resolved Mar 18, 2026, 05:30 PM UTC

  1. investigating Mar 18, 2026, 08:16 AM UTC

    Scheduled system upgrade on March 21st, 2026

  2. monitoring Mar 18, 2026, 05:29 PM UTC

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

  3. resolved Mar 18, 2026, 05:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 20, 2026 Authentication issue on api health 3h 5m Organization Registry, Mineral Registry, Membership Management

Started Jan 20, 2026, 04:33 PM UTC· resolved Jan 20, 2026, 07:39 PM UTC

  1. investigating Jan 20, 2026, 04:33 PM UTC

    We are currently investigating this issue.

  2. identified Jan 20, 2026, 04:35 PM UTC

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

  3. monitoring Jan 20, 2026, 05:52 PM UTC

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

  4. resolved Jan 20, 2026, 07:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 20, 2026 API health on blockchain explorer 8h 26m Blockchain Explorer, Supply chain Validation, Alchemy Alchemy Dashboard

Started Jan 20, 2026, 09:25 AM UTC· resolved Jan 20, 2026, 05:52 PM UTC

  1. investigating Jan 20, 2026, 09:25 AM UTC

    API health on block explorer fell down to 70%. Suspected affected components are: Supplychain validation component

  2. identified Jan 20, 2026, 09:30 AM UTC

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

  3. monitoring Jan 20, 2026, 02:05 PM UTC

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

  4. resolved Jan 20, 2026, 05:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 19, 2026 This is an example incident –

Started Jan 19, 2026, 06:23 AM UTC· resolved Jan 19, 2026, 06:23 AM UTC

  1. investigating Jan 20, 2026, 06:07 AM UTC

    When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

  2. identified Jan 20, 2026, 06:07 AM UTC

    As you continue to work through the incident, update your customers frequently.

  3. monitoring Jan 20, 2026, 06:07 AM UTC

    Let your users know once a fix is in place, and keep communication clear and precise.

  4. resolved Jan 20, 2026, 06:07 AM UTC

    Empathize with those affected and let them know everything is operating as normal.

Read the full incident report →