Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Quicknode

    Last checked 28 Eki 05:53 UTC

    Quicknode status

    Blockchain infrastructure for secure, decentralized innovation.

    Experiencing an issue?

    Quicknode logo

    Quicknode çöktü mü?

    Status unavailable

    Having issues with Quicknode?

    Share your experience to help others stay informed.

    Current statusHealth graphOutage reportsOutage mapSocial signalsStatus historyComponentsIncident historyMaintenanceCommunityReviewsAboutFAQsMonitor serviceSimilar servicesComparison

    Latest activity

    Last 24 hours
    1. Status verification pending

      The latest official observation is not fresh enough to confirm current service health.

      Official provider status
      28 Eki 05:53 UTC
    2. Official incident resolved

      Aptos Testnet - Chain Stall at Block 16,617,441 — This incident has been resolved.

      Official provider status
      28 Eki 05:15 UTC
    3. Official maintenance completed

      [Critical] Zcash - Mainnet & Testnet - Upgrade to Zebra 7.0.0 — The scheduled maintenance has been completed.

      Official provider status
      28 Eki 00:01 UTC
    4. Official maintenance completed

      [Standard] Gravity Mainnet - Upgrade to v1.10.1 — The scheduled maintenance has been completed.

      Official provider status
      28 Eki 00:00 UTC
    5. Official incident resolved

      Injective Testnet - Degraded Performance — This incident has been resolved.

      Official provider status
      27 Eki 21:48 UTC

    Quicknode outage reports

    0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.

    Yakın zamanda kesinti bildirimi yok

    Son 24 saat içinde topluluk tarafından bu hizmet için kesinti bildirimi gönderilmedi.

    Quicknode durumu değiştiğinde bildirim alın

    E-posta, push ve webhook bildirimleri.

    İzlemeyi başlat

    Quicknode kesinti haritası

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Haritanın tamamını görün

    Quicknode kesinti haritası

    Loading report locations…

    Quicknode status history

    Official status observations, not measured service uptime.

    Quicknode components

    Component nameStatus

    More components are available below.

    Quicknode incident history

    Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.

    View more history
    Incident nameDurationStartedUTCAcknowledgedSeverity
    Official status·Resolved5h 16m27 Eki 202623:59 UTCYesMinor
    Official status·Resolved23m27 Eki 202621:25 UTCYesMinor
    Official status·Resolved12h 22m26 Eki 202614:07 UTCYesMinor
    Official status·Resolved30m25 Eki 202623:57 UTCYesMinor
    Official status·Resolved1h 5m23 Eki 202608:00 UTCYesUnknown
    Official status·Resolved1h 21m19 Eki 202609:38 UTCYesMinor
    Official status·Resolved53m13 Eki 202615:23 UTCYesUnknown
    Official status·Resolved13h 29m10 Eki 202608:50 UTCYesMajor

    Uptimus'ta Quicknode izleme hakkında

    Uptimus, Quicknode hizmetini resmi durum kaynağından izler ve olayları, bakımları ve bileşenleri ortak bir duruma dönüştürür.

    Bu sayfa şu anda 231 bileşen, 154 olay, 294 bakım ve 78 günlük bilinen geçmiş içerir.

    Uptimus bağımsızdır ve Quicknode ile bağlantılı değildir. Sağlıklı durum her kullanıcı, cihaz veya bölgenin etkilenmediğini garanti etmez.

    Uptimus Quicknode hizmetini nasıl izler

    Quicknode veya izlenen bir bileşen büyük ya da kritik kesinti bildirdiğinde bildirim alın. Uyarılar e-posta, push ve yapılandırılmış entegrasyonlar dahil etkin workspace kanallarına yönlendirilebilir. Mevcut geçmiş 154 dizinlenmiş olay içerir ve uyarılara güncel durumun ötesinde bağlam sağlar. Yakın zamanda dizinlenen bir olay “Aptos Testnet - Chain Stall at Block 16,617,441” idi.

    Düşük performans, kısmi etki ve tam kesinti olmayan küçük olaylar hakkında bildirim alın. Uptimus şu anda 231 Quicknode bileşenini izliyor. Uyarılar e-posta, push ve yapılandırılmış entegrasyonlar dahil etkin workspace kanallarına yönlendirilebilir.

    Bakım bildirimleri
    Quicknode planlı, zamanlanmış veya etkin bakım yayınladığında bildirim alın. Uptimus mevcut Quicknode geçmişinden 294 bakım aralığını dizinledi. Uyarılar e-posta, push ve yapılandırılmış entegrasyonlar dahil etkin workspace kanallarına yönlendirilebilir.

    Scheduled maintenance

    Planned work published by the official provider.

    1. ✓

      [Standard] Morph - Hoodi Mainnet - Upgrade to v0.6.4 & morph-v2.2.7 (Celadon Fork)

      Maintenance

      We are upgrading our Morph Mainnet infrastructure to node v0.6.4 and morph-v2.2.7 ahead of the mandatory Celadon network upgrade, which activates on Hoodi Testnet at 2026-10-28 06:00 UTC. Celadon introduces MorphTx v2, which lets users pay gas with an alternative token and delegate their EOA to contract code (EIP-7702) in a single transaction. It also corrects the rounding of alt-token fee refunds, so users are charged the precisely rounded net fee. All existing transaction types, including MorphTx v0/v1 and standard 0x04 SetCode transactions, remain fully supported. During the maintenance window, brief interruptions to RPC availability may occur. RPC changes: - eth_sendRawTransaction — MorphTx v2 (type 0x7F, version 0x02) is accepted once Celadon activates. Before activation, v2 transactions are rejected. - Transaction-building requests (e.g. eth_sendTransaction, eth_estimateGas) — The MorphTx version no longer needs to be specified and is derived from the request. A non-empty authorizationList combined with feeTokenID, reference, or memo builds a v2 transaction. Otherwise, v1 is used. - eth_getTransactionByHash — Now returns authorizationList for MorphTx v2 transactions. - MorphTx v2 transactions with a non-empty authorizationList cannot create contracts (same rule as EIP-7702). - Fees for transactions paying gas in an alternative token may differ slightly from previous values due to the corrected refund rounding. https://github.com/morph-l2/morph/releases/tag/v0.6.4 https://github.com/morph-l2/go-ethereum/releases/tag/morph-v2.2.7

      Started 2 Kas 2026 00:00 UTC · Ongoing

    2. ✓

      [Urgent] Stacks Mainnet - Upgrade to v9.7.0

      Maintenance

      We are upgrading our Stacks Mainnet infrastructure to v9.7.0 on 2026-11-02. This release patches recent Node.js security vulnerabilities and introduces new v3 API endpoints for block and transaction data, along with enhanced transaction metadata. A brief database migration will occur during the upgrade, and brief interruptions to RPC availability may occur on that date. RPC Changes: - GET /extended/v3/blocks — New cursor-paginated endpoint for Stacks block summaries, including tenure_height, tx_count, and Bitcoin anchor block reference. - GET /extended/v3/blocks/{height_or_hash} — New endpoint providing Stacks block details, including parent block hash, block size, and execution cost. - GET /extended/v3/bitcoin-blocks — New cursor-paginated endpoint for Bitcoin block summaries with header time and associated Stacks/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash} — New endpoint providing Bitcoin block details with header time and associated block/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash}/blocks — New endpoint listing Stacks blocks anchored to a specific Bitcoin block. - event_count — Added to v3 transaction summaries across all v3 endpoints (transactions list, batch, block transactions, principal transactions, and search). - /v2 RPC proxy — Simplified to a plain passthrough; custom fee estimation and transaction endpoint configuration are no longer available. https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v9.7.0

      Started 2 Kas 2026 00:00 UTC · Ongoing

    3. ✓

      [Urgent] NEAR - Mainnet - Upgrade to 2.14.0

      Maintenance

      We are upgrading our NEAR Mainnet infrastructure to nearcore 2.14.0 on 2026-10-30. This is a mandatory protocol upgrade (protocol version 86 to 88) introducing consensus-breaking changes, new action validation rules, and improved cryptographic support. Validators must upgrade before protocol version 87 voting begins on November 4th. Brief interruptions to RPC availability may occur on that date. RPC Changes: - view_access_key_list now supports pagination with after_key and limit parameters, returning a last_key field. Accounts with more than 100 access keys must use pagination; unpaginated requests for these accounts will fail. - tx, send_tx, and broadcast_tx_commit responses now include an optional cause field on TIMEOUT_ERROR, describing transaction progress (NOT_OBSERVED, PENDING, DOES_NOT_TRACK_SHARD, or ERROR). - tx_status is now the stable method name for what was EXPERIMENTAL_tx_status. Both names work identically; Quicknode documentation for tx_status is in progress. https://github.com/near/nearcore/releases/tag/2.14.0

      Started 30 Eki 2026 00:00 UTC · Ongoing

    4. ✓

      [Standard] Hedera Mainnet - Upgrade to Mirror Node v0.165.0 & RPC Relay v0.80.2

      Maintenance

      We are upgrading our Hedera Mainnet infrastructure to Mirror Node v0.165.0 and RPC Relay v0.80.2 on 2026-10-28. This release prepares the mirror node for the Nova/TSS 3.22.0 consensus-layer transition, introduces cryptographic improvements to block proof handling, and adds new REST and gRPC endpoints with enhanced security hardening. Brief interruptions to RPC availability may occur on that date. RPC Changes: Block proof hashing — Block proof hashing is transitioning to a new format. Dual support for both block proof formats is maintained during the rollout period to enable gradual operator deployment. https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.165.0

      Started 28 Eki 2026 00:00 UTC · Ongoing

    5. ✓

      Standard Fluent - Mainnet & Testnet - Upgrade to v1.5.1

      Maintenance

      We are upgrading our Fluent infrastructure to v1.5.1 on 2026-10-28. This release introduces native Ethereum precompiles (0x01–0x11 and P256VERIFY) via revm for significantly faster cryptographic operations, upgrades the rWasm runtime to 0.7.2 for improved consensus safety, and enforces a protocol-level transaction gas cap. Brief interruptions to RPC availability may occur on that date. RPC Changes: eth_sendTransaction / eth_sendRawTransaction — Transactions exceeding 100 Mgas will be rejected by the network (EIP-7825 with Fluent-specific limit); clients sending such transactions will receive rejection errors. Precompile execution (ecrecover, keccak256, sha256, ripemd160, bigModExp, bn256Add, bn256ScalarMul, bn256Pairing, blake2f, KZG, BLS12-381) — All Ethereum precompiles now execute via native revm implementations at the same addresses with identical gas costs and results, but with several times faster performance. https://github.com/fluentlabs-xyz/fluentbase/releases/tag/v1.5.1

      Started 28 Eki 2026 00:00 UTC · Ongoing

    6. ✓

      [Standard] Bitcoin Mainnet - Upgrade ord to 0.29.1

      Maintenance

      We are upgrading our Bitcoin Mainnet Ordinals infrastructure from ord 0.23.2 to 0.29.1. This release rolls up several versions of indexer improvements, including richer inscription metadata in API responses, new gallery and bulk lookup endpoints, a new recursive endpoint for raw block data, and a fix for indexing transactions that include pay-to-anchor outputs. During the maintenance window, brief interruptions to Ordinals API availability may occur. RPC Changes: - Inscription JSON responses — added. Inscription responses now include a properties object (attributes, traits, title, and gallery items) along with the metaprotocol field. - Inscription parents — fixed. Invalid parents are now filtered out and no longer returned for inscriptions. - /children routes — added. Child inscription routes now support JSON responses. - /gallery — added. New JSON endpoint for retrieving gallery inscriptions, with paginated gallery items. - /galleries and /collections — changed. /collections now returns results in reverse order, and hidden inscriptions are excluded from both /collections and /galleries. - /missing — added. New endpoint to check whether a batch of inscriptions exists in a single request. - /r/block/ — added. New recursive endpoint that returns the raw block hex for a given block hash or height. - Block inscriptions pagination — changed. Requests for an out-of-range page now return an empty page instead of an error. - Outpoint and TXID lookups — fixed. Outpoints and TXIDs made up entirely of decimal digits now resolve correctly instead of being misrouted. - Sat lookups — fixed. "Not found" sat index responses are no longer cached, so subsequent lookups return current data. - Rune amounts — fixed. Decimal amounts with excessive precision or values that would overflow now return a proper error. - Pay-to-anchor outputs — fixed. Transactions containing pay-to-anchor (P2A) outputs are now indexed correctly. Prior versions could return incorrect inscription and output data for these transactions. https://github.com/ordinals/ord/releases/tag/0.29.1

      Started 28 Eki 2026 00:00 UTC · Ongoing

    7. ✓

      [Urgent] Sui - Testnet - Upgrade to v1.83.0

      Maintenance

      We are upgrading our Sui Testnet infrastructure to v1.83.0 on 2026-10-28. This release advances the protocol to version 140 with consensus-breaking changes, including refined object funds withdrawal checks, transaction effects optimization, and substantial improvements to gRPC and error handling. Brief interruptions to RPC availability may occur on that date. RPC Changes: - SimulateTransaction — When gas selection cannot find enough SUI to cover the gas budget, the error now carries structured metadata (owner, requiredBudget, coinBalance, addressBalance) via a google.rpc.ErrorInfo with reason INSUFFICIENT_GAS_BALANCE (domain sui.io), allowing clients to read the required budget without message parsing. If budget estimation fails, the error reports the execution failure with reason TRANSACTION_EXECUTION_FAILED and includes ExecutionError details. - SubscribeTransactions, SubscribeCheckpoints — Now populates effects object types, clever errors, and event json when the read mask requests them, matching GetTransaction behavior. - ListTransactions, ListEvents — Requests below the node's retention now return OUT_OF_RANGE instead of INTERNAL. Cursors can be sent back in either ordering without skipping items. Descending requests with end_checkpoint above the latest indexed checkpoint + 1 now return OUT_OF_RANGE. On pruning fullnodes, all requests needing data below the pruning floor return OUT_OF_RANGE. Pages now correctly report hasNextPage/hasPreviousPage based on end reason rather than arbitrary boundaries. - ListCheckpoints — Requests with a starting cursor past the server's indexed tip now return OUT_OF_RANGE instead of an empty page. Pages now correctly report hasNextPage/hasPreviousPage based on end reason. Checkpoints with an after cursor at or below filter.afterCheckpoint, or a before cursor at or above filter.beforeCheckpoint, now returns the checkpoints within the bound instead of an empty page. - GetEpoch — Now lists mldsa65_auth among protocol feature flags. https://github.com/MystenLabs/sui/releases/tag/testnet-v1.83.0

      Started 28 Eki 2026 00:00 UTC · Ongoing

    8. ✓

      [Critical] Zcash - Mainnet & Testnet - Upgrade to Zebra 7.0.0

      Resolved

      The scheduled maintenance has been completed.

      Started 27 Eki 2026 00:00 UTC · Resolved 28 Eki 2026 00:01 UTC

    Kurtarma bildirimleri
    Quicknode veya etkilenen bir bileşen tekrar sağlıklı çalışmaya döndüğünde haberdar olun. Sayfa 78 günlük bilinen geçmiş içerir; çözülen olaylar daha sonra incelenebilir. Uyarılar e-posta, push ve yapılandırılmış entegrasyonlar dahil etkin workspace kanallarına yönlendirilebilir.
    Durum mesajları
    Uptimus, Quicknode tarafından yayınlanan olay başlığını normalleştirilmiş durumla birlikte saklar. Mevcut geçmiş 154 dizinlenmiş olay içerir ve uyarılara güncel durumun ötesinde bağlam sağlar. Yakın zamanda dizinlenen bir olay “Aptos Testnet - Chain Stall at Block 16,617,441” idi.
    Durum ayrıntıları
    Olay ve bakım güncellemeleri araştırma, azaltma ve kurtarma sürecini izlemek için korunur. Uptimus tarafından korunan yakın tarihli resmi güncelleme: “This incident has been resolved.”.
    Bileşen durumu filtreleme
    Tüm bileşenleri veya kullandığınız Quicknode ürünlerini seçin. Resmi bildirimler bu seçime uyar. Uptimus şu anda 231 Quicknode bileşenini izliyor. Filtreleme teslim edilen resmi uyarıları değiştirir, olayları herkese açık geçmişten kaldırmaz.

    Sıkça Sorulan Sorular

    Quicknode durumu değiştiğinde bildirim alın

    İzlemeyi başlat
    Similar services
    Comparison

    Quicknode için Uptimus ve Downdetector

    Downdetector herkese açık sayfaları kullanıcı raporlarına odaklanır. Uptimus bu etkinliği sağlayıcının yayımladığı resmi olaylar, bakımlar ve bileşen durumlarıyla birleştirir.

    Quicknode için Uptimus ve Downdetector
    Karşılaştırma ölçütleriUptimusDowndetector
    Quicknode için topluluk kesinti raporlarıDahilDahil
    Tekil raporları geniş kesintilerden ayıran uyarlanabilir temelDahilDahil
    24 saatlik rapor etkinliği ve bölgesel kesinti görünümüDahilDahil
    Web siteleri, durum sağlayıcıları, Steam oyunları ve Android uygulama ve oyunları için tek alanDahilAyrı ürün
    Aynı çalışma alanından e-posta, push ve webhook uyarılarıDahilAyrı ürün
    Quicknode için resmi olay güncellemeleri ve durum zaman çizelgesiDahilRapor odaklı
    Bileşen sağlığı ve bakım pencereleri ayrı tutulurDahilHerkese açık sayfalarda sınırlı
    DahilRapor odaklı · Herkese açık sayfalarda sınırlıAyrı ürün

    The current official status of Quicknode cannot be verified. The latest stored provider observation indicated ongoing maintenance. 0 reports were recorded for Quicknode in the last 24 hours. Last official check: 28 Eki 05:53 UTC.

    Bu hizmeti değerlendirin

    Geçen ay Quicknode'ı nasıl değerlendirirsiniz?

    Henüz değerlendirme yok

    (Ayda bir inceleme sınırı)

    Topluluk Tartışması

    Quicknode hakkındaki düşüncelerinizi paylaşın

    A
    Henüz yorum yok

    İlk yorum yapan siz olun!

    İzlenecek daha fazla hizmet

    Diğer popüler hizmetleri ve mevcut durumlarını keşfedin

    Tüm hizmetlere göz atın
    SpectrumOverwatch®Triton DigitalSherpanyNylasFormativeBeanstalkScrutinizerSavvycalFont Awesome