Goldsky - Notice history

All systems operational

API - Operational

100% - uptime
Aug 2024 · 100.0%Sep · 99.99%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Dashboard - Operational

100% - uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024
100% - uptime

Mirror Replication - Operational

100% - uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Chain Ingestion - Operational

100% - uptime
Aug 2024 · 99.97%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Subgraph Sources - Operational

100% - uptime
Aug 2024 · 99.85%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024
100% - uptime

API - Operational

Chain Ingestion - Operational

100% - uptime
Aug 2024 · 99.99%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Arweave Search Gateway - Operational

100% - uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Notice history

Oct 2024

Networking issues affecting subgraphs and pipelines for the last 10 min
  • Resolved
    Resolved
    This incident has been resolved.

Sep 2024

API endpoints are experiencing high failure rates
  • Resolved
    Resolved

    This incident has been resolved. Our API endpoint suffered an outage as a result of a bad deploy which interfered with networking.

  • Investigating
    Investigating
    We are currently investigating this incident.
Subgraph Indexing paused for Zetachain
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.

Aug 2024

Mirror pipelines are lagging
  • Resolved
    Resolved

    This incident has been resolved. Data will automatically be backfilled.

    Only chain ingestion was lagging, and mirror pipelines using subgraph sources were not affected.

  • Investigating
    Investigating

    We are currently investigating this incident. New blockchain events may be slow to be indexed. There has been no data loss, and we will backfill all data.

Gateway timeouts for webapp
  • Resolved
    Resolved

    This incident has been resolved. There was an infinite loop eating up resources. A fix has been deployed.

  • Investigating
    Investigating
    We are currently investigating this incident.
We identified an issue with subgraph ingestion for mirror.
  • Resolved
    Resolved

    Our ingestion system has recovered and all subgraph sourced mirror data for the affected subgraphs have been backfilled. No data was lost.

  • Monitoring
    Monitoring

    We've recovered the failing system and are currently backfilling data.

  • Identified
    Identified

    We are continuing to work on a fix for this incident. This will lead to a temporary delay in data from some subgraphs arriving in mirror sinks. We will backfill the data, and nothing should be lost.

Rolling all node groups to update subnets
  • Completed
    August 13, 2024 at 1:19 AM
    Completed
    August 13, 2024 at 1:19 AM
    Maintenance has completed successfully.
  • In progress
    August 12, 2024 at 4:00 PM
    In progress
    August 12, 2024 at 4:00 PM

    We are rolling all of our workloads from old node groups to new node groups to expand our subnets. All workloads should automatically restart. You may get notifications about subgraphs or pipelines failing, this is transient.

Compute outage with AWS
  • Resolved
    Update
    This incident has been resolved.
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    Recovery has started. For the next few minutes:

    • Consumers might experience loss of data freshness.

    • Pipelines might not start.

  • Identified
    Identified

    We are in the middle of a compute outage with AWS. We have opened a high urgency support ticket with them. We expect resolution soon. Degraded performance for Mirror.

Aug 2024 to Oct 2024

Next