Error: Net::ReadTimeout with #<TCPSocket:(closed)>

GraphQL API
,
1

Every api call return error Net::ReadTimeout with #TCPSocket:(closed) periodically
But one time in two minutes it work

2

Which API?

Please share your query. Give us more data.

3

I received timeout for every queries I tried

for example:

query (
  $network: EthereumNetwork!
  $address: [String!]
  $limit: Int!
  $offset: Int!
  $from: ISO8601DateTime
  $till: ISO8601DateTime
) {
  ethereum(network: $network) {
    in: transfers(
      options: { asc: "block.timestamp.time", limit: $limit, offset: $offset }
      date: { since: $from, till: $till }
      amount: { gt: 0 }
      receiver: { in: $address }
    ) {
      wallet: receiver {
        address
      }
      block {
        timestamp {
          time(format: "%Y-%m-%d %H:%M:%S")
        }
      }
      address: sender {
        address
        annotation
        smartContract {
          contractType
        }
      }
      currency {
        address
        symbol
        tokenType
      }
      amount
      transaction {
        hash
      }
    }
    out: transfers(
      options: { asc: "block.timestamp.time", limit: $limit, offset: $offset }
      date: { since: $from, till: $till }
      amount: { gt: 0 }
      sender: { in: $address }
    ) {
      wallet: sender {
        address
      }
      block {
        timestamp {
          time(format: "%Y-%m-%d %H:%M:%S")
        }
      }
      address: receiver {
        address
        annotation
        smartContract {
          contractType
        }
      }
      currency {
        address
        symbol
        tokenType
      }
      amount
      transaction {
        hash
      }
    }
  }
}
4

I need Parameters too.

5 
      {
        network: "bsc",
        address: ["0x82f2E28260B0Ead8a7C60E3De37A9004C5A28b1c"],
        limit: 10000,
        offset: 0,
        from: undefined,
        till: undefined,
      }
6

Try this.

7

It works but not consistently…
I think problem is not in query or variables, cos it works but not always
or network problem or api server problem…