Completed -
The scheduled maintenance has been completed.
May 15, 07:58 UTC
Verifying -
Verification is currently underway for the maintenance items.
May 14, 17:01 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 12, 07:00 UTC
Scheduled -
We will be upgrading our Solana Mainnet nodes to 1.17.33 on 2024-05-12 at 07.00 UTC
This updates includes the following Highlighted Changes: - Backport connection stream counter to v1.17 - v1.17: corrected to not use hardcoded connections count for unstaked - v1.17: Change DEFAULT_TPU_CONNECTION_POOL_SIZE to 1 - v1.17: quic: delay calling set_max_concurrent_uni_streams/set_receive_window - v1.17: Disable cache warmer if RPC is not using it - v1.17: Parameterize max streams per ms - v1.17: quic server: set initial window to PACKET_DATA_SIZE - v1.17: Limit max concurrent connections
Resolved -
This incident has been resolved.
May 11, 09:07 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 11, 08:06 UTC
Investigating -
We observe BSC testnet archive node is stuck at block number 40231834. You may experience problems when retrieve block states for any the block height is after this number. Our team is investigating on the issue.
All our BSC testnet full nodes are operating as normal.
May 11, 07:50 UTC
Completed -
The scheduled maintenance has been completed.
May 10, 09:43 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 9, 07:55 UTC
Scheduled -
We will be upgrading our Solana-validator nodes on Solana Devnet and Testnet to 1.18.12 on 2024-05-09 at 07:55 UTC
This updates includes the following Highlighted Changes: v1.18: Disable cache warmer if RPC is not using it v1.18: Change DEFAULT_TPU_CONNECTION_POOL_SIZE to 1 v1.18: Limit max concurrent connections v1.18: blockstore: send duplicate proofs for chained merkle root conflicts v1.18: quic: delay calling set_max_concurrent_uni_streams/set_receive_window v1.18: cli: Use --use-rpc flag correctly during program deployments v1.18: sleep instead of drop when stream rate exceeded limit;
Completed -
The scheduled maintenance has been completed.
May 8, 08:10 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 8, 07:00 UTC
Scheduled -
We will be upgrading our stacks-blockchain-api nodes on Stacks Mainnet/Testnet to v7.11.0-beta.6 on 2024-05-08 at 07:00 UTC
This updates includes the following Highlighted Changes: - add burn_block_height to transactions - add average stacks block time to burn block endpoints - add total tx count to burn block endpoints - add average block times endpoint - fix inconsistent block transaction results in Rosetta response
Please see detailed change log at $ReleaseNotes
May 8, 06:42 UTC
Resolved -
This incident has been resolved.
May 3, 03:44 UTC
Investigating -
The Polygon Amoy network appears to have stalled at block 6579439 - The QuickNode team is investigating with the Polygon team and will update with more information once it is available.
May 3, 00:33 UTC
Completed -
The scheduled maintenance has been completed.
May 2, 03:18 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 2, 03:00 UTC
Scheduled -
We will be upgrading our substrate-api-sidecar nodes on Polkadot Mainnet to v19.0.0 on 2024-05-02 at 03:00 UTC
This updates includes the following Highlighted Changes: - This PR introduces breaking changes in the staking-payouts endpoint. More specifically: - The payouts for eras after the v1.2.0 runtime upgrade are now retrieved and returned in the endpoint's response - The payouts are retrieved by using the new storage items erasStakersPaged and erasStakersOverview - The use of erasStakersClipped is deprecated but still supported. It will be completely removed in the future - Payouts with claimed false are now retrieved and returned in the endpoint's response - Payouts are now retrievable from any block height within the queried era