Goldsky - Notice history

This incident has been resolved. We have a clear root cause and know how to prevent this going into the future. We'll continue reviewing our processes and will make a post-mortem available to enterprise-plan customers.

Two of our database machines became inaccessible. After working with AWS, we were able to access it. During the incident, we have moved VIP workloads to use other databases, and after monitoring and ensuring it won't happen again, we'll move back to our existing distributed setup.

Blocks, logs and transactions have now caught up. We are, however, still experiencing ~1 hour lag on the traces dataset. We're continuing to investigate the issue.

An upstream data infrastrature provider is having some issues, affecting our indexing pipeline. Vendor has implemented a mitigation and are currently monitoring the result.