Goldsky Status - Incident history https://status.goldsky.com Goldsky Wed, 17 Jun 2026 16:00:00 +0000 Database upgrade Type: Maintenance Affected Components: Subgraph Sources Jun 11, 18:40:07 GMT+0 - Identified - We are going to upgrade one of our database clusters. There will be a partial outage with Webhooks and Subgraph Sources during the upgrade window. No data will be lost. Type: Maintenance

Affected Components:

<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>18:40:07</var> GMT+0</small><br><strong>Identified</strong> - We are going to upgrade one of our database clusters. There will be a partial outage with Webhooks and Subgraph Sources during the upgrade window. No data will be lost..</p> ]]> Wed, 17 Jun 2026 16:00:00 +0000 https://status.goldsky.com/maintenance/cmq9ueerb03coqufbf2pdxduf https://status.goldsky.com/maintenance/cmq9ueerb03coqufbf2pdxduf Parts of the web app are not loading Type: Incident Duration: 33 minutes Affected Components: Dashboard Jun 9, 19:05:48 GMT+0 - Investigating - We are currently investigating this incident, but have no indication that data streaming or indexing have affected. Jun 9, 19:16:04 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 9, 19:38:40 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 33 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>19:05:48</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident, but have no indication that data streaming or indexing have affected..</p> <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>19:16:04</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>19:38:40</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 9 Jun 2026 19:05:48 +0000 https://status.goldsky.com/incident/cmq70fqzb01znpkc926k66123 https://status.goldsky.com/incident/cmq70fqzb01znpkc926k66123 Swell Mainnet — chain not producing blocks Type: Incident Duration: 5 hours and 46 minutes Affected Components: Swell Jun 5, 07:51:25 GMT+0 - Identified - Swell Mainnet stopped producing blocks at **\~07:20 UTC (2026-06-05)**, with the chain head stuck at **block 23,973,655**. We've traced this to an upstream halt on the Swell chain's sequencer — Goldsky's RPC infrastructure is fully operational and unaffected.e to succeed, but the chain head will not advance until Swell's sequencer recovers. We're monitoring and will update when block production Jun 5, 13:37:24 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 5 hours and 46 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>07:51:25</var> GMT+0</small><br><strong>Identified</strong> - Swell Mainnet stopped producing blocks at **\~07:20 UTC (2026-06-05)**, with the chain head stuck at **block 23,973,655**. We've traced this to an upstream halt on the Swell chain's sequencer — Goldsky's RPC infrastructure is fully operational and unaffected.e to succeed, but the chain head will not advance until Swell's sequencer recovers. We're monitoring and will update when block production.</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>13:37:24</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 5 Jun 2026 07:51:25 +0000 https://status.goldsky.com/incident/cmq0ml2yv004bnwa64m5iq0wm https://status.goldsky.com/incident/cmq0ml2yv004bnwa64m5iq0wm Database Upgrade Type: Maintenance Duration: 3 hours and 33 minutes Affected Components: Subgraph Sources Jun 4, 15:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 4, 18:33:03 GMT+0 - Completed - Maintenance has completed successfully. Jun 4, 15:00:00 GMT+0 - Identified - We are going to upgrade one of our database clusters. There will be a partial outage with Webhooks and Subgraph Sources during the upgrade window. No data will be lost. Type: Maintenance

Duration: 3 hours and 33 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>18:33:03</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are going to upgrade one of our database clusters. There will be a partial outage with Webhooks and Subgraph Sources during the upgrade window. No data will be lost..</p> ]]> Thu, 4 Jun 2026 15:00:00 +0000 https://status.goldsky.com/maintenance/cmpbap5oc006wqk0fr7sqvn1b https://status.goldsky.com/maintenance/cmpbap5oc006wqk0fr7sqvn1b Polygon-amoy (testnet) has halted Type: Incident Duration: 6 minutes Affected Components: Subgraph Sources, Chain Ingestion, Chain Ingestion, Mirror Replication Jun 3, 18:53:53 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 3, 18:59:23 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 6 minutes

Affected Components: , , ,

<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>18:53:53</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>18:59:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 3 Jun 2026 18:53:53 +0000 https://status.goldsky.com/incident/cmpyfdaw304eqnwx4hipc0toh https://status.goldsky.com/incident/cmpyfdaw304eqnwx4hipc0toh API down Type: Incident Duration: 2 minutes Affected Components: API Jun 3, 14:06:05 GMT+0 - Identified - Jun 3, 14:07:40 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>14:06:05</var> GMT+0</small><br><strong>Identified</strong> - .</p> <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>14:07:40</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 3 Jun 2026 14:06:05 +0000 https://status.goldsky.com/incident/cmpy536m401dxp3ch3mhivsni https://status.goldsky.com/incident/cmpy536m401dxp3ch3mhivsni Edge endpoints are experiencing elevated error rates Type: Incident Duration: 55 minutes Affected Components: Corn Maizenet, zkSync, Somnia Testnet, Unichain, Sei, Unichain Testnet, Monad, Polygon zkEVM, Avalanche, Arbitrum Sepolia, Polygon, opBNB Mainnet, Scroll Mainnet, Ethereum Sepolia, Gravity, Flare, Optimism, Moonbeam Mainnet, Kava Mainnet, Base, Kaia Mainnet, Abstract, Base Sepolia, Blast, HyperEVM Testnet, Fuse Mainnet, Gnosis, Monad Testnet, Optimism Sepolia, Swell, Zora, Arbitrum One, TAC, Berachain, Linea, Cyber, Story, Sonic, Bsc, Zircuit, HyperEVM, Mantle May 28, 21:59:38 GMT+0 - Identified - We are working with our upstream provider to address increased latency and error rates for Edge endpoints. May 28, 22:54:57 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 55 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>21:59:38</var> GMT+0</small><br><strong>Identified</strong> - We are working with our upstream provider to address increased latency and error rates for Edge endpoints..</p> <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>22:54:57</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 28 May 2026 21:59:38 +0000 https://status.goldsky.com/incident/cmpq1d2lo024spkr4gmr3bq3x https://status.goldsky.com/incident/cmpq1d2lo024spkr4gmr3bq3x Base Mainnet Ingestion Lag Type: Incident Duration: 43 minutes Affected Components: Chain Ingestion May 21, 01:23:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 21, 01:29:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Base Logs, Token, and Balances datasets are fully real-time. Base Receipt-Transaction datasets are halted as we monitor data correctness. May 21, 02:06:00 GMT+0 - Resolved - This incident has been resolved. Further data repairs will be propagated to various sinks through our pipelines. Type: Incident

Duration: 43 minutes

Affected Components:

<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>01:23:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>01:29:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. Base Logs, Token, and Balances datasets are fully real-time. Base Receipt-Transaction datasets are halted as we monitor data correctness. .</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>02:06:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Further data repairs will be propagated to various sinks through our pipelines. .</p> ]]> Thu, 21 May 2026 01:23:00 +0000 https://status.goldsky.com/incident/cmpeuwrdp04hsp9y3yjbdofj7 https://status.goldsky.com/incident/cmpeuwrdp04hsp9y3yjbdofj7 Base chain bad latest-block Type: Incident Duration: 1 hour and 2 minutes Affected Components: Base May 21, 01:21:00 GMT+0 - Investigating - A rogue upstream node returned block data far in the future, causing Edge to register a \~50M-block jump on Base. we are investigating this. May 21, 02:23:05 GMT+0 - Resolved - This incident has been resolved. we've removed the node from the pool and are investigating additional guardrails in the proxy to prevent recurrence. Type: Incident

Duration: 1 hour and 2 minutes

Affected Components:

<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>01:21:00</var> GMT+0</small><br><strong>Investigating</strong> - A rogue upstream node returned block data far in the future, causing Edge to register a \~50M-block jump on Base. we are investigating this..</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>02:23:05</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. we've removed the node from the pool and are investigating additional guardrails in the proxy to prevent recurrence..</p> ]]> Thu, 21 May 2026 01:21:00 +0000 https://status.goldsky.com/incident/cmpewku8e04xup9xhfsfcyot0 https://status.goldsky.com/incident/cmpewku8e04xup9xhfsfcyot0 Networking upgrade Type: Maintenance Duration: 10 minutes Affected Components: Corn Maizenet, Kaia Mainnet, Abstract, zkSync, Somnia Testnet, Base Sepolia, Blast, Unichain, HyperEVM Testnet, API, Fuse Mainnet, Gnosis, Monad Testnet, Optimism Sepolia, Sei, Swell, Unichain Testnet, Zora, Monad, Chain Ingestion, Polygon zkEVM, Arbitrum One, TAC, Berachain, Linea, Cyber, Story, Sonic, Avalanche, Arbitrum Sepolia, Polygon, opBNB Mainnet, Scroll Mainnet, Bsc, Zircuit, Ethereum Sepolia, HyperEVM, Gravity, Flare, Optimism, Arweave Search Gateway, Subgraph Sources, API, Mantle, Mirror Replication, Base, Moonbeam Mainnet, Kava Mainnet, Dashboard, Clickhouse + Query Endpoints, Chain Ingestion May 19, 15:00:00 GMT+0 - Identified - We are planning to upgrade a critical component of our networking stack. No downtime is expected. May 19, 15:00:01 GMT+0 - Identified - Maintenance is now in progress May 19, 15:10:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 10 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning to upgrade a critical component of our networking stack. No downtime is expected..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>15:10:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 19 May 2026 15:00:00 +0000 https://status.goldsky.com/maintenance/cmpbaxz1j00cgnlu2qaolyiz8 https://status.goldsky.com/maintenance/cmpbaxz1j00cgnlu2qaolyiz8 eth_getLogs null-topic collapse on gRPC fast-path Type: Incident Duration: 8 days and 44 minutes Affected Components: Base May 19, 08:30:00 GMT+0 - Investigating - We are currently investigating this incident on eth\_getLogs only when topics had a null followed by another filter. May 26, 09:14:00 GMT+0 - Resolved - This incident has been resolved. May 27, 09:14:15 GMT+0 - Postmortem - Our gRPC client (responsible for serving query methods like eth\_getLogs quickly) was incorrectly dropping null wildcards in the middle of eth\_getLogs topic filters, which silently misaligned subsequent positions. Our HTTP client behaved correctly, but most eth\_getLogs requests are served via the gRPC client. A request was affected if its `topics` array contained a `null` followed by another non-null filter — for example `topics: [selector, null, recipient]`, which is the standard shape `viem.getLogs({ event, args: { to: [...] } })` produces. Requests without a mid-array `null` were unaffected. If you ran an indexer that filtered logs by a non-first indexed topic against Base between 2026-05-19 and 2026-05-27, you may have missed events. Re-run the affected query range against Edge RPC again. Type: Incident

Duration: 8 days and 44 minutes

Affected Components:

<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident on eth\_getLogs only when topics had a null followed by another filter..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>09:14:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>09:14:15</var> GMT+0</small><br><strong>Postmortem</strong> - Our gRPC client (responsible for serving query methods like eth\_getLogs quickly) was incorrectly dropping null wildcards in the middle of eth\_getLogs topic filters, which silently misaligned subsequent positions. Our HTTP client behaved correctly, but most eth\_getLogs requests are served via the gRPC client. A request was affected if its `topics` array contained a `null` followed by another non-null filter — for example `topics: [selector, null, recipient]`, which is the standard shape `viem.getLogs({ event, args: { to: [...] } })` produces. Requests without a mid-array `null` were unaffected. If you ran an indexer that filtered logs by a non-first indexed topic against Base between 2026-05-19 and 2026-05-27, you may have missed events. Re-run the affected query range against Edge RPC again..</p> ]]> Tue, 19 May 2026 08:30:00 +0000 https://status.goldsky.com/incident/cmpnw2b9k00dqqnjhnm46ni59 https://status.goldsky.com/incident/cmpnw2b9k00dqqnjhnm46ni59 New Turbo pipeline creation outage Type: Incident Duration: 7 minutes Affected Components: API, Chain Ingestion, Subgraph Sources, Mirror Replication May 15, 13:11:14 GMT+0 - Investigating - We are currently investigating an issue involving the creation of new Turbo pipelines. May 15, 13:18:16 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 7 minutes

Affected Components: , , ,

<p><small>May <var data-var='date'> 15</var>, <var data-var='time'>13:11:14</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an issue involving the creation of new Turbo pipelines..</p> <p><small>May <var data-var='date'> 15</var>, <var data-var='time'>13:18:16</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 15 May 2026 13:11:14 +0000 https://status.goldsky.com/incident/cmp6xrh0n02b0pflyld2leg8l https://status.goldsky.com/incident/cmp6xrh0n02b0pflyld2leg8l Elevated latency on Edge RPC Type: Incident Duration: 6 hours and 28 minutes Affected Components: Corn Maizenet, Kaia Mainnet, Abstract, zkSync, Somnia Testnet, Base Sepolia, Blast, Unichain, HyperEVM Testnet, Fuse Mainnet, Gnosis, Monad Testnet, Optimism Sepolia, Sei, Swell, Unichain Testnet, Zora, Monad, Polygon zkEVM, Arbitrum One, TAC, Berachain, Linea, Cyber, Story, Sonic, Avalanche, Arbitrum Sepolia, Polygon, opBNB Mainnet, Scroll Mainnet, Bsc, Zircuit, Ethereum Sepolia, HyperEVM, Gravity, Flare, Optimism, Mantle, Base, Moonbeam Mainnet, Kava Mainnet May 13, 06:00:00 GMT+0 - Resolved - We've deployed configuration mitigations that significantly reduce auth-DB load and have a follow-up fix in flight for the underlying connector behavior. The fleet is currently stable and we are continuing to monitor. May 12, 19:00:00 GMT+0 - Investigating - Between approximately May 12th 20:00 UTC and May 13th 07:00 UTC today, customers in ams, cdg, iad, and sjc may have seen elevated latency and intermittent failures on Edge RPC requests. The root cause was a reconnect cascade between our edge fleet and the auth database, triggered by a brief upstream blip and amplified by a latent bug in our connection-handling code. Traffic was largely served throughout via our auth fail-open path; some requests timed out at peak. Type: Incident

Duration: 6 hours and 28 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Resolved</strong> - We've deployed configuration mitigations that significantly reduce auth-DB load and have a follow-up fix in flight for the underlying connector behavior. The fleet is currently stable and we are continuing to monitor..</p> <p><small>May <var data-var='date'> 12</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Investigating</strong> - Between approximately May 12th 20:00 UTC and May 13th 07:00 UTC today, customers in ams, cdg, iad, and sjc may have seen elevated latency and intermittent failures on Edge RPC requests. The root cause was a reconnect cascade between our edge fleet and the auth database, triggered by a brief upstream blip and amplified by a latent bug in our connection-handling code. Traffic was largely served throughout via our auth fail-open path; some requests timed out at peak..</p> ]]> Tue, 12 May 2026 19:00:00 +0000 https://status.goldsky.com/incident/cmp3u0nis03xhqoal9ozxop3r https://status.goldsky.com/incident/cmp3u0nis03xhqoal9ozxop3r Turbo pipelines stuck in restarting state during a security upgrade Type: Incident Duration: 17 minutes Affected Components: Mirror Replication Apr 30, 14:15:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 30, 14:32:00 GMT+0 - Resolved - This incident has been resolved. During a node upgrade, a configuration change did not propagate fast enough and some nodes were caught in a crash loop while the rollout completed. We are working on a permanent fix to prevent this kind of failure from happening again. This affected less than 5% of customer projects, for between 5-17 minutes. Apr 30, 19:36:03 GMT+0 - Postmortem - After a deep investigation, the root cause and impact is clear and new processes and alerts are being setup to mitigate this in the future. During an infrastructure upgrade meant to harden our security posture, some pipelines failed to restart, resulting in data not being sent to the sinks. This affected less than 5% of customer projects, for between 5-17 minutes. Pipelines in those projects deployed earlier than Monday will have been affected. No data would be lost, and the pipelines continued from where they left off once the issue was resolved. As such, the incident is downgraded from Major Outage to Partial Outage. New processes and monitors will be added by the end of the week to prevent these issues. Type: Incident

Duration: 17 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>14:15:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>14:32:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. During a node upgrade, a configuration change did not propagate fast enough and some nodes were caught in a crash loop while the rollout completed. We are working on a permanent fix to prevent this kind of failure from happening again. This affected less than 5% of customer projects, for between 5-17 minutes. .</p> <p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>19:36:03</var> GMT+0</small><br><strong>Postmortem</strong> - After a deep investigation, the root cause and impact is clear and new processes and alerts are being setup to mitigate this in the future. During an infrastructure upgrade meant to harden our security posture, some pipelines failed to restart, resulting in data not being sent to the sinks. This affected less than 5% of customer projects, for between 5-17 minutes. Pipelines in those projects deployed earlier than Monday will have been affected. No data would be lost, and the pipelines continued from where they left off once the issue was resolved. As such, the incident is downgraded from Major Outage to Partial Outage. New processes and monitors will be added by the end of the week to prevent these issues..</p> ]]> Thu, 30 Apr 2026 14:15:00 +0000 https://status.goldsky.com/incident/cmolm5hkz0elc48dohcd0siqv https://status.goldsky.com/incident/cmolm5hkz0elc48dohcd0siqv Solana ingestion is degraded because of upstream RPC issues. Type: Incident Duration: 1 hour and 23 minutes Affected Components: Chain Ingestion, Subgraph Sources, Mirror Replication Apr 21, 01:48:29 GMT+0 - Identified - We are continuing to work on a fix for this incident, we're working on load balancing with additional RPC providers. Apr 21, 03:10:59 GMT+0 - Resolved - We have identified the root cause of this outage. The issue originated with an upstream RPC provider that began missing specific blocks. This was a failure mode we had not previously encountered. As a result, Solana Turbo pipelines stalled as parallel workers entered a retry loop waiting on unavailable blocks. Detection was difficult initially, as all existing health indicators remained green. We have since forced a reset of affected pipelines to exit the retry loop, and processing has resumed. We have also deployed a dedicated monitor for this failure mode and are working to deploy automatic recovery for future incidents. Type: Incident

Duration: 1 hour and 23 minutes

Affected Components: , ,

<p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>01:48:29</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident, we're working on load balancing with additional RPC providers..</p> <p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>03:10:59</var> GMT+0</small><br><strong>Resolved</strong> - We have identified the root cause of this outage. The issue originated with an upstream RPC provider that began missing specific blocks. This was a failure mode we had not previously encountered. As a result, Solana Turbo pipelines stalled as parallel workers entered a retry loop waiting on unavailable blocks. Detection was difficult initially, as all existing health indicators remained green. We have since forced a reset of affected pipelines to exit the retry loop, and processing has resumed. We have also deployed a dedicated monitor for this failure mode and are working to deploy automatic recovery for future incidents..</p> ]]> Tue, 21 Apr 2026 01:48:29 +0000 https://status.goldsky.com/incident/cmo7yt0av0005f4xu7hd9busf https://status.goldsky.com/incident/cmo7yt0av0005f4xu7hd9busf Issues with subgraph indexing for historic Sei blocks Type: Incident Duration: 12 days and 12 hours Affected Components: Chain Ingestion Apr 15, 18:00:00 GMT+0 - Resolved - After an upgrade to the Sei network RPCs, historic data for blocks can be corrupt and affect indexing. This should not affect subgraphs that are already at edge, only new subgraphs that need to re-index older blocks. We are working with RPC providers to resolve the incident. Type: Incident

Duration: 12 days and 12 hours

Affected Components:

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Resolved</strong> - After an upgrade to the Sei network RPCs, historic data for blocks can be corrupt and affect indexing. This should not affect subgraphs that are already at edge, only new subgraphs that need to re-index older blocks. We are working with RPC providers to resolve the incident..</p> ]]> Wed, 15 Apr 2026 18:00:00 +0000 https://status.goldsky.com/incident/cmnxzlruq023seyyy3g9wyl98 https://status.goldsky.com/incident/cmnxzlruq023seyyy3g9wyl98 Solana Ingestion for Turbo is lagging Type: Incident Duration: 45 minutes Affected Components: Chain Ingestion, , Mirror Replication, Mirror → Mar 12, 13:03:52 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 12, 13:39:48 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 12, 13:49:17 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 45 minutes

Affected Components: , ,

<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>13:03:52</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>13:39:48</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>13:49:17</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 12 Mar 2026 13:03:52 +0000 https://status.goldsky.com/incident/cmmnhbhli04tnm6ow3czlieqr https://status.goldsky.com/incident/cmmnhbhli04tnm6ow3czlieqr Chain ingestion halted Type: Incident Duration: 18 minutes Affected Components: Chain Ingestion Mar 9, 15:00:00 GMT+0 - Identified - We've identified an issue with AWS database infrastructure. working with aws to resolve. Mar 9, 15:18:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 18 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - We've identified an issue with AWS database infrastructure. working with aws to resolve..</p> <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>15:18:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 9 Mar 2026 15:00:00 +0000 https://status.goldsky.com/incident/cmmjbe0ab00cj9jffhur5yst8 https://status.goldsky.com/incident/cmmjbe0ab00cj9jffhur5yst8 Optimism chain halt Type: Incident Duration: 5 minutes Affected Components: Optimism, Chain Ingestion, Chain Ingestion Mar 4, 23:14:37 GMT+0 - Identified - The Optimism chain has halted (last block as of posting this is 10 minutes old). Mar 4, 23:19:41 GMT+0 - Resolved - Optimism is now producing blocks again. Type: Incident

Duration: 5 minutes

Affected Components: , ,

<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>23:14:37</var> GMT+0</small><br><strong>Identified</strong> - The Optimism chain has halted (last block as of posting this is 10 minutes old). .</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>23:19:41</var> GMT+0</small><br><strong>Resolved</strong> - Optimism is now producing blocks again..</p> ]]> Wed, 4 Mar 2026 23:14:37 +0000 https://status.goldsky.com/incident/cmmcnm3eg01xkufos3ga3pvnt https://status.goldsky.com/incident/cmmcnm3eg01xkufos3ga3pvnt Database instability Type: Incident Duration: 27 minutes Affected Components: , API, Chain Ingestion, Subgraphs → Mar 3, 16:59:02 GMT+0 - Identified - We have identified the root cause of database instability and are working with AWS to remediate. Mar 3, 17:26:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 27 minutes

Affected Components: , ,

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>16:59:02</var> GMT+0</small><br><strong>Identified</strong> - We have identified the root cause of database instability and are working with AWS to remediate..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>17:26:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 3 Mar 2026 16:59:02 +0000 https://status.goldsky.com/incident/cmmaur8md0dsv4gg2ivu1dojt https://status.goldsky.com/incident/cmmaur8md0dsv4gg2ivu1dojt Database cluster migration Type: Maintenance Duration: 20 minutes Affected Components: API, Arweave Search Gateway, Subgraph Sources, Chain Ingestion Mar 2, 19:46:00 GMT+0 - Identified - We conducting database maintenance tasks. This should be a fully online operation. Mar 2, 20:05:55 GMT+0 - Completed - Maintenance aborted successfully, no downtime observed. Type: Maintenance

Duration: 20 minutes

Affected Components: , , ,

<p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>19:46:00</var> GMT+0</small><br><strong>Identified</strong> - We conducting database maintenance tasks. This should be a fully online operation. .</p> <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>20:05:55</var> GMT+0</small><br><strong>Completed</strong> - Maintenance aborted successfully, no downtime observed..</p> ]]> Mon, 2 Mar 2026 19:46:00 +0000 https://status.goldsky.com/maintenance/cmm9lby7v00lny2o04o1sv1sm https://status.goldsky.com/maintenance/cmm9lby7v00lny2o04o1sv1sm A Cloudflare outage is affecting many of our upstream providers, causing indexing lag on many networks. Type: Incident Duration: 7 hours and 49 minutes Affected Components: Corn Maizenet, Kaia Mainnet, zkSync, Abstract, Somnia Testnet, Base Sepolia, Blast, Unichain, HyperEVM Testnet, Fuse Mainnet, Gnosis, Monad Testnet, Optimism Sepolia, Sei, Swell, Unichain Testnet, Zora, Monad, Polygon zkEVM, Arbitrum One, TAC, Berachain, Optimism, Linea, Cyber, Story, Sonic, Avalanche, Arbitrum Sepolia, Polygon, opBNB Mainnet, Scroll Mainnet, Bsc, Zircuit, Ethereum Sepolia, HyperEVM, Gravity, Flare, Chain Ingestion, Subgraph Sources, Mantle, Mirror Replication, Base, Moonbeam Mainnet, Kava Mainnet, , Chain Ingestion, Edge → Feb 26, 15:37:00 GMT+0 - Resolved - This incident has been resolved. Feb 26, 14:48:33 GMT+0 - Monitoring - We are attempting to work around the affected nodes, but some networks are entirely affected by this outage. You can follow Cloudflare's status here: <https://www.cloudflarestatus.com> Type: Incident

Duration: 7 hours and 49 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>15:37:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>14:48:33</var> GMT+0</small><br><strong>Monitoring</strong> - We are attempting to work around the affected nodes, but some networks are entirely affected by this outage. You can follow Cloudflare's status here: <https://www.cloudflarestatus.com>.</p> ]]> Thu, 26 Feb 2026 14:48:33 +0000 https://status.goldsky.com/incident/cmm3kw6590pszhrim13tym7tv https://status.goldsky.com/incident/cmm3kw6590pszhrim13tym7tv Issues with mirror data Type: Incident Duration: 29 minutes Affected Components: Chain Ingestion Feb 23, 20:32:35 GMT+0 - Investigating - Most mirror pipelines have issues consuming data, we're investigating. Feb 23, 20:48:03 GMT+0 - Monitoring - Early signs that data is flowing again, so it looks like we will recover shortly. There should be no data loss, but there might be a backlog of data to process. Feb 23, 21:01:06 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 29 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>20:32:35</var> GMT+0</small><br><strong>Investigating</strong> - Most mirror pipelines have issues consuming data, we're investigating..</p> <p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>20:48:03</var> GMT+0</small><br><strong>Monitoring</strong> - Early signs that data is flowing again, so it looks like we will recover shortly. There should be no data loss, but there might be a backlog of data to process..</p> <p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>21:01:06</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 23 Feb 2026 20:32:35 +0000 https://status.goldsky.com/incident/cmlzmv1ut086np79zv87mfx28 https://status.goldsky.com/incident/cmlzmv1ut086np79zv87mfx28 Subgraph ingestion for Mirror is lagging on some shards Type: Incident Duration: 4 hours and 28 minutes Affected Components: Subgraph Sources Feb 12, 15:51:02 GMT+0 - Identified - If you are not seeing up-to-date data from your subgraph based mirror pipeline, it's likely related to an ongoing incident. We are continuing to work on a fix for this incident. Feb 12, 20:18:33 GMT+0 - Resolved - This incident has been resolved. No data has been lost. Type: Incident

Duration: 4 hours and 28 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>15:51:02</var> GMT+0</small><br><strong>Identified</strong> - If you are not seeing up-to-date data from your subgraph based mirror pipeline, it's likely related to an ongoing incident. We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>20:18:33</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. No data has been lost..</p> ]]> Thu, 12 Feb 2026 15:51:02 +0000 https://status.goldsky.com/incident/cmljmym4h00bl4wx1bi753utk https://status.goldsky.com/incident/cmljmym4h00bl4wx1bi753utk Mirror pipeline records received metrics are not populating in the dashboard or billing estimates Type: Incident Duration: 20 hours and 7 minutes Affected Components: , Chain Ingestion, Subgraph Sources, Mirror Replication, Dashboard, Mirror → Feb 10, 10:00:00 GMT+0 - Investigating - We are currently investigating this incident. Feb 10, 23:44:26 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 11, 06:07:01 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 20 hours and 7 minutes

Affected Components: , , , ,

<p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>23:44:26</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>06:07:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 10 Feb 2026 10:00:00 +0000 https://status.goldsky.com/incident/cmlha3s4a057c11rovq74s3yw https://status.goldsky.com/incident/cmlha3s4a057c11rovq74s3yw Solana Mainnet indexing has stalled Type: Incident Duration: 24 minutes Affected Components: Mirror Replication, Chain Ingestion, Subgraph Sources, , Mirror → Feb 3, 20:15:00 GMT+0 - Investigating - We are currently investigating this incident. Feb 3, 20:39:21 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 24 minutes

Affected Components: , , ,

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>20:15:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>20:39:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 3 Feb 2026 20:15:00 +0000 https://status.goldsky.com/incident/cml7247gz02fdq0dbncig40vi https://status.goldsky.com/incident/cml7247gz02fdq0dbncig40vi Ethereum Mainnet Mirror Ingestion Lagging Type: Incident Duration: 5 minutes Affected Components: Mirror Replication, Chain Ingestion Feb 3, 18:21:23 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 3, 18:26:24 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 5 minutes

Affected Components: ,

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>18:21:23</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>18:26:24</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 3 Feb 2026 18:21:23 +0000 https://status.goldsky.com/incident/cml6xdab209ak8qow4ussx81n https://status.goldsky.com/incident/cml6xdab209ak8qow4ussx81n Arbitrum One Traces ingestion issues Type: Incident Duration: 4 hours and 11 minutes Affected Components: Chain Ingestion Jan 21, 14:24:58 GMT+0 - Monitoring - We implemented a fix and arbitrum traces ingestion is catching up quickly. Jan 21, 14:39:07 GMT+0 - Resolved - This incident has been resolved. Jan 21, 10:27:40 GMT+0 - Investigating - We're seeing some lag on Arbitrum One traces ingestion and we're actively working to provide a fix. Type: Incident

Duration: 4 hours and 11 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>14:24:58</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and arbitrum traces ingestion is catching up quickly..</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>14:39:07</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>10:27:40</var> GMT+0</small><br><strong>Investigating</strong> - We're seeing some lag on Arbitrum One traces ingestion and we're actively working to provide a fix..</p> ]]> Wed, 21 Jan 2026 10:27:40 +0000 https://status.goldsky.com/incident/cmknvq0vb13xa4liiod32lqog https://status.goldsky.com/incident/cmknvq0vb13xa4liiod32lqog Solana Ingestion for Turbo is lagging Type: Incident Duration: 2 hours and 9 minutes Affected Components: Chain Ingestion Jan 15, 09:12:19 GMT+0 - Identified - The issue has been identified to be slow downloads from Cloudflare (R2 + workers). However, we have been able to get pipelines up and running again, but with \~1 hour lag. We're currently working on solutions to get the pipelines back to edge faster. Jan 15, 09:36:40 GMT+0 - Resolved - This incident has been resolved. Jan 15, 07:27:49 GMT+0 - Investigating - Turbo pipelines consuming solana data is currently experiencing issues fetching new blocks. We're investigating. Type: Incident

Duration: 2 hours and 9 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>09:12:19</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified to be slow downloads from Cloudflare (R2 + workers). However, we have been able to get pipelines up and running again, but with \~1 hour lag. We're currently working on solutions to get the pipelines back to edge faster..</p> <p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>09:36:40</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>07:27:49</var> GMT+0</small><br><strong>Investigating</strong> - Turbo pipelines consuming solana data is currently experiencing issues fetching new blocks. We're investigating..</p> ]]> Thu, 15 Jan 2026 07:27:49 +0000 https://status.goldsky.com/incident/cmkf4nm2g01wng4pok4l8hzyp https://status.goldsky.com/incident/cmkf4nm2g01wng4pok4l8hzyp Upgrading webhook system Type: Maintenance Duration: 1 hour and 29 minutes Affected Components: API Oct 2, 16:00:00 GMT+0 - Identified - We are going to be upgrading our webhook system. We expect no downtime. There will be no data loss. Oct 2, 16:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 2, 17:28:55 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 1 hour and 29 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are going to be upgrading our webhook system. We expect no downtime. There will be no data loss..</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>16:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>17:28:55</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Thu, 2 Oct 2025 16:00:00 +0000 https://status.goldsky.com/maintenance/cmg8p18g10ssh10wccro764v4 https://status.goldsky.com/maintenance/cmg8p18g10ssh10wccro764v4 Upgrading webhook system Type: Maintenance Duration: 5 days Affected Components: , Chain Ingestion, API, Subgraphs → Sep 24, 17:57:00 GMT+0 - Identified - We are upgrading our subgraph webhook system. There will be no data loss. A few webhooks may get sent more than once. Total migration time should be less than 10 minutes. Sep 24, 19:57:00 GMT+0 - Completed - Maintenance is now complete Type: Maintenance

Duration: 5 days

Affected Components: , ,

<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>17:57:00</var> GMT+0</small><br><strong>Identified</strong> - We are upgrading our subgraph webhook system. There will be no data loss. A few webhooks may get sent more than once. Total migration time should be less than 10 minutes..</p> <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>19:57:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance is now complete.</p> ]]> Wed, 24 Sep 2025 17:57:00 +0000 https://status.goldsky.com/maintenance/cmfyad0rf0006zlp8oeq739ov https://status.goldsky.com/maintenance/cmfyad0rf0006zlp8oeq739ov Upgrading webhook system Type: Maintenance Duration: 1 hour and 25 minutes Affected Components: , Subgraphs → Sep 23, 20:54:37 GMT+0 - Completed - Maintenance didn't start. Will try again tomorrow. Sep 23, 19:30:00 GMT+0 - Identified - We are upgrading our subgraph webhook system. There will be no data loss. A few webhooks may get sent more than once. Total migration time should be less than 10 minutes. Sep 23, 19:30:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 1 hour and 25 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>20:54:37</var> GMT+0</small><br><strong>Completed</strong> - Maintenance didn't start. Will try again tomorrow..</p> <p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are upgrading our subgraph webhook system. There will be no data loss. A few webhooks may get sent more than once. Total migration time should be less than 10 minutes..</p> <p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>19:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Tue, 23 Sep 2025 19:30:00 +0000 https://status.goldsky.com/maintenance/cmfwy3lu6000z6dncibi4v82w https://status.goldsky.com/maintenance/cmfwy3lu6000z6dncibi4v82w Upgrading analytics database Type: Maintenance Duration: 3 hours and 17 minutes Affected Components: Dashboard Jan 31, 14:37:00 GMT+0 - Identified - Our analytics database provider needs to perform an upgrade during which time reads and writes will be unavailable for: 1\. subgraph logs 1. subgraph requests 2. pipeline logs 3. pipeline statuses Subgraphs and pipelines will continue to work as normal. Just the logs and requests metrics will be unavailable since we store those in an analytics database. Jan 31, 17:53:35 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 3 hours and 17 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>14:37:00</var> GMT+0</small><br><strong>Identified</strong> - Our analytics database provider needs to perform an upgrade during which time reads and writes will be unavailable for: 1\. subgraph logs 1. subgraph requests 2. pipeline logs 3. pipeline statuses Subgraphs and pipelines will continue to work as normal. Just the logs and requests metrics will be unavailable since we store those in an analytics database..</p> <p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>17:53:35</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Fri, 31 Jan 2025 14:37:00 +0000 https://status.goldsky.com/maintenance/cm6gkag5b008zh6vrnpjma7cs https://status.goldsky.com/maintenance/cm6gkag5b008zh6vrnpjma7cs Arweave Search Gateway Maintenance. Redirected to Arweave.net Type: Maintenance Duration: 2 days, 15 hours and 15 minutes Affected Components: Arweave Search Gateway Jan 12, 17:21:58 GMT+0 - Completed - Maintenance has completed successfully. Jan 10, 02:07:00 GMT+0 - Identified - The arweave search gateway is undergoing maintenance. the Graphql requests will be redirected to Arweave.net. Type: Maintenance

Duration: 2 days, 15 hours and 15 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>17:21:58</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>02:07:00</var> GMT+0</small><br><strong>Identified</strong> - The arweave search gateway is undergoing maintenance. the Graphql requests will be redirected to Arweave.net. .</p> ]]> Fri, 10 Jan 2025 02:07:00 +0000 https://status.goldsky.com/maintenance/cm5q8lowc001bci3laq27ufl4 https://status.goldsky.com/maintenance/cm5q8lowc001bci3laq27ufl4 Blockchain Warehouse Maintenance Type: Maintenance Duration: 2 hours and 52 minutes Affected Components: Clickhouse + Query Endpoints Dec 18, 18:21:09 GMT+0 - Identified - Issue identified on upgrade Dec 18, 16:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Dec 18, 17:40:38 GMT+0 - Completed - Maintenance has completed successfully. Dec 18, 19:21:57 GMT+0 - Completed - Maintenance has completed successfully. Dec 18, 16:30:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 2 hours and 52 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>18:21:09</var> GMT+0</small><br><strong>Identified</strong> - Issue identified on upgrade.</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>17:40:38</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>19:21:57</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>16:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Wed, 18 Dec 2024 16:30:00 +0000 https://status.goldsky.com/maintenance/cm4u3xv6k000p12thkuiybxn2 https://status.goldsky.com/maintenance/cm4u3xv6k000p12thkuiybxn2 Maintenance of Clickhouse and query endpoints Type: Maintenance Duration: 1 hour Affected Components: API, Dashboard, Clickhouse + Query Endpoints Dec 18, 14:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 18, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Dec 18, 14:00:00 GMT+0 - Identified - We are planning a scheduled maintenance of our hosted clickhouse data warehouse and their query endpoints. Logs and metrics for pipelines and subgraphs will be affected. Estimated downtime is around 60 minutes. Type: Maintenance

Duration: 1 hour

Affected Components: , ,

<p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>14:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning a scheduled maintenance of our hosted clickhouse data warehouse and their query endpoints. Logs and metrics for pipelines and subgraphs will be affected. Estimated downtime is around 60 minutes..</p> ]]> Wed, 18 Dec 2024 14:00:00 +0000 https://status.goldsky.com/maintenance/cm4skxhps000udxbzkvk0eyh4 https://status.goldsky.com/maintenance/cm4skxhps000udxbzkvk0eyh4 Upgrading clickhouse Type: Maintenance Duration: 2 days, 13 hours and 1 minute Affected Components: API, Dashboard Dec 5, 14:30:01 GMT+0 - Identified - Maintenance is now in progress Dec 5, 14:30:00 GMT+0 - Identified - Clickhouse is undergoing an upgrade. Logs and metrics for pipelines and subgraphs will be affected. Dec 5, 15:31:00 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 2 days, 13 hours and 1 minute

Affected Components: ,

<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>14:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Identified</strong> - Clickhouse is undergoing an upgrade. Logs and metrics for pipelines and subgraphs will be affected..</p> <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>15:31:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Thu, 5 Dec 2024 14:30:00 +0000 https://status.goldsky.com/maintenance/cm4a4zdg50001s3gsdfupj57l https://status.goldsky.com/maintenance/cm4a4zdg50001s3gsdfupj57l Maintenance of Clickhouse and query endpoints Type: Maintenance Duration: 30 minutes Affected Components: Clickhouse + Query Endpoints Dec 5, 14:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 5, 14:30:00 GMT+0 - Completed - Maintenance has completed successfully Dec 5, 14:00:00 GMT+0 - Identified - We are planning a scheduled maintenance of our hosted clickhouse data warehouse and their query endpoints. Estimated downtime is around 20 minutes. Type: Maintenance

Duration: 30 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>14:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning a scheduled maintenance of our hosted clickhouse data warehouse and their query endpoints. Estimated downtime is around 20 minutes..</p> ]]> Thu, 5 Dec 2024 14:00:00 +0000 https://status.goldsky.com/maintenance/cm489tb3z000j14lkeyyiuinh https://status.goldsky.com/maintenance/cm489tb3z000j14lkeyyiuinh Rolling all node groups to update subnets Type: Maintenance Duration: 9 hours and 19 minutes Affected Components: Chain Ingestion, API, Mirror Replication, Dashboard, Chain Ingestion, Arweave Search Gateway, API, Subgraph Sources Aug 12, 16:00:00 GMT+0 - Identified - 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. Aug 13, 01:19:01 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 9 hours and 19 minutes

Affected Components: , , , , , , ,

<p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>01:19:01</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Mon, 12 Aug 2024 16:00:00 +0000 https://status.goldsky.com/maintenance/clzratahi5504gyodejbpyzkp https://status.goldsky.com/maintenance/clzratahi5504gyodejbpyzkp Mirror pipeline maintance Type: Maintenance Duration: 1 hour and 5 minutes Affected Components: Chain Ingestion, Mirror Replication, Subgraph Sources Apr 23, 21:20:00 GMT+0 - Completed - Upgrading underlying infrastructure, there may be slight delays in mirror pipelines Type: Maintenance

Duration: 1 hour and 5 minutes

Affected Components: , ,

<p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>21:20:00</var> GMT+0</small><br><strong>Completed</strong> - Upgrading underlying infrastructure, there may be slight delays in mirror pipelines.</p> ]]> Tue, 23 Apr 2024 21:20:00 +0000 https://status.goldsky.com/maintenance/clvcw7j6r1246bln76j7en0dc https://status.goldsky.com/maintenance/clvcw7j6r1246bln76j7en0dc Upstream maintenance may affect Mirror data latency Type: Maintenance Duration: 5 hours and 53 minutes Affected Components: Chain Ingestion, Mirror Replication, Subgraph Sources Apr 3, 16:18:32 GMT+0 - Identified - An upstream provider is undergoing maintenance which could affect latency for Mirror pipelines, we are monitoring the service and will update if there are any issues. Apr 3, 22:11:58 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 5 hours and 53 minutes

Affected Components: , ,

<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>16:18:32</var> GMT+0</small><br><strong>Identified</strong> - An upstream provider is undergoing maintenance which could affect latency for Mirror pipelines, we are monitoring the service and will update if there are any issues..</p> <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>22:11:58</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Wed, 3 Apr 2024 16:18:32 +0000 https://status.goldsky.com/maintenance/cluk0kz909059ban1oon90ec2 https://status.goldsky.com/maintenance/cluk0kz909059ban1oon90ec2 Subgraph indexer maintenance Type: Maintenance Duration: 2 days and 12 hours Affected Components: API, Chain Ingestion Mar 26, 13:45:00 GMT+0 - Completed - We are planning for a scheduled maintenance during this time which may prevent deploys of new subgraphs and lead to indexing lag until maintenance completes. Type: Maintenance

Duration: 2 days and 12 hours

Affected Components: ,

<p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>13:45:00</var> GMT+0</small><br><strong>Completed</strong> - We are planning for a scheduled maintenance during this time which may prevent deploys of new subgraphs and lead to indexing lag until maintenance completes..</p> ]]> Tue, 26 Mar 2024 13:45:00 +0000 https://status.goldsky.com/maintenance/clu8kcsd898266bhocz6ljhuad https://status.goldsky.com/maintenance/clu8kcsd898266bhocz6ljhuad Database Shard Migration Type: Maintenance Affected Components: , Mirror → Jul 21, 00:00:00 GMT+0 - Completed - An upgrade will be done that improves indexing speed for subgraphs. There will be up of two minutes of indexing downtime in the worse case, and in the best case there will be no downtime. There will be a rolling restart of API nodes, so subscription requests may be interrupted Type: Maintenance

Affected Components:

<p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Completed</strong> - An upgrade will be done that improves indexing speed for subgraphs. There will be up of two minutes of indexing downtime in the worse case, and in the best case there will be no downtime. There will be a rolling restart of API nodes, so subscription requests may be interrupted.</p> ]]> Fri, 21 Jul 2023 00:00:00 +0000 https://status.goldsky.com/maintenance/clkbtyri0398571caoc56ou52w4 https://status.goldsky.com/maintenance/clkbtyri0398571caoc56ou52w4