Blockio の障害履歴

Ongoing connectivity issues at our datacenter are causing an elevated error rate and delayed responses across our services. There is no ETA to a resolution, but you can track it here: https://status.linode.com/incidents/n7yt1l21qtyz.

This incident has been resolved.

Datacenter connectivity issues will cause intermittent errors/delays in various components of our services. The issue is expected to last through November 24th as maintenance crews isolate and fix the cause.

This incident has been resolved.

Ongoing datacenter connectivity issues are causing an elevated number of errors for API calls, delays in webhook delivery, and errors/delay in various UI functionality. This issue is expected to last a few hours.

This incident has been resolved.

New incoming transactions will get indexed slower until this is resolved.

This incident has been resolved.

Some functions of the UI and API will be temporarily unavailable for 2-3 hours as we perform maintenance on our infrastructure.

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

This incident has been resolved.

Indexer for Block.io account addresses is undergoing maintenance. ETA for resolution is ~2 hours.

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

This incident has been resolved.

This maintenance will affect querying data for external Bitcoin addresses and WebHooks. We will provide an ETA for this maintenance once an estimate is available.

We are continuing to work on a fix for this issue.

Bitcoin address data for non-account addresses will be stale for the next 7-14 days as we re-index the larger Bitcoin blockchain.

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

This incident has been resolved.

ETA to resolution: 30 minutes.

ETA is ~45min. Apologies for the inconvenience.

Maintenance is 70% complete.

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

This incident has been resolved.

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

We are continuing to work on a fix for this issue.

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

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

The Litecoin network's indexing is currently delayed and should return to normal in the next 5-6 hours. During this time users will experience delays in new incoming transactions' appearance via parts of the REST API.

Updated ETA is 8-10 hours from now.

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

This incident has been resolved.

We are currently investigating this issue.

We've identified the issue (downstream links). We're awaiting a remedy for this from the relevant ISPs.

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

This incident has been resolved.

An issue at our hosting provider has affected blockchain indexing for external-incoming transactions at this time. ETA to resolution: 60 minutes.

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

The infrastructure responsible for blockchain indexing will undergo some maintenance for around 60 minutes in the next 2 hours. Blockchain indexing is operating normally at this time.

This incident has been resolved.

Existing network connectivity issues are due to CloudFlare's outage; see https://www.cloudflarestatus.com/incidents/hmc1qbk6sb3v.

This incident has been resolved.

CloudFlare and Google DNS outages are causing network connectivity issues globally, and Block.io is affected as well.

https://www.cloudflarestatus.com/

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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

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

Infrastructure instability for Web Wallet caused the issue. This is now resolved.

Unscheduled maintenance for Dogecoin transactions indexes. ETA to resolution is 10pm Pacific Time. Bitcoin and Litecoin networks are unaffected.

This incident has been resolved.

We are currently investigating this issue.

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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

This incident has been resolved.

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

This incident has been resolved.