-
Notifications
You must be signed in to change notification settings - Fork 134
Open
Labels
bugType: Something isn't workingType: Something isn't working
Description
Description
The Mirror Node REST API /api/v1/accounts/{id} endpoint returns 503 Service Unavailable when querying the fee collector account 0.0.98 (EVM address 0x0000000000000000000000000000000000000062) with the default parameters.
Account 0.0.98 is the network fee collector and receives fees from every transaction on the network, resulting in billions of transaction records. When the API attempts to fetch transactions for this account, the database query times out and returns a service unavailable error.
Steps to reproduce
Run the following command:
curl "https://testnet.mirrornode.hedera.com/api/v1/accounts/0x0000000000000000000000000000000000000062?limit=100"Expected Result:
Account data with transactions
Actual Result:
Request hangs for approximately 20 seconds, then returns:
503 Service Unavailable
Additional context
- Other accounts with normal transaction volumes return successfully
- Adding
&transactions=falseto the query works around the issue by excluding transaction data - This affects any client attempting to query system accounts with high transaction volumes
Hedera network
testnet
Version
latest
Operating system
None
Metadata
Metadata
Assignees
Labels
bugType: Something isn't workingType: Something isn't working