Victor Baranov

@JohnOldman0202 we're working this bug.

@diucicd This DB migration should resolve the issue https://github.com/blockscout/blockscout/pull/4712

Sorry for the late response. Yes, we provide hosting opportunity. https://docs.blockscout.com/for-projects/premium-features/your-chain-on-blockscout.com#hosting-your-chain-on-blockscout.com. I am closing this issue for now. If you still have further requests, please let me know.

Blockscout default option for fetching internal trasnactions is `callTracer` now (master branch, not released yet). Custom js tracer is optional. It should resolve your issue with indexing internal trasnsactions. I...

Resolved in https://github.com/blockscout/blockscout/pull/6401, included into [5.0.0](https://github.com/blockscout/blockscout/releases/tag/v5.0.0-beta).

Docker integration is production-ready. We provide various docker-compose configs for different clients https://github.com/blockscout/blockscout/tree/master/docker-compose.

> @vbaranov Thank you for your reply, I actually meant pool_timeout not pool_size. as I read in this thread [https://github.com/blockscout/blockscout/issues/1128](url) the answer of @acravenho : > > > Please remove...

@Matt8white sorry for the delay in answer. Such growing CPU consumption looks abnormal. Could you please update to the latest release of Blockscout [5.0.0](https://github.com/blockscout/blockscout/releases/tag/v5.0.0-beta) or even better to master branch?...

@Thegaram is internal transactions fetching enabled on your instance? Could you disable it for some time (`INDEXER_DISABLE_INTERNAL_TRANSACTIONS_FETCHER=true`) and provide some feedback, if this issue dissappeared or not?

@ct-toch how much CPU did you allocate for the Blockscout container? Is the situation the same with 5.1.3?