---
title: "getNetworkStatus"
method: POST
path: "/network/status"
tags: ["Cardano - Rosetta"]
---

# getNetworkStatus

`POST /network/status`

This endpoint returns the current status of the network requested. Any
NetworkIdentifier returned by /network/list should be accessible here.

## Request body

- NetworkRequest — A NetworkRequest is utilized to retrieve some data specific exclusively to a NetworkIdentifier.
  - `network_identifier` NetworkIdentifier, required — The network_identifier specifies which network a particular object is associated with.
    - `blockchain` string, required
    - `network` string, required — If a blockchain has a specific chain-id or network identifier, it should go in this field. It is up to the client to determine which network-specific identifier is mainnet or testnet.
    - `sub_network_identifier` SubNetworkIdentifier — In blockchains with sharded state, the SubNetworkIdentifier is required to query some object on a specific shard. This identifier is optional for all non-sharded blockchains.
      - `network` string, required
      - `metadata` object
  - `metadata` object

## Response `200`

Expected response to a valid request

- NetworkStatusResponse — NetworkStatusResponse contains basic information about the node's view of a blockchain network. It is assumed that any BlockIdentifier.Index less than or equal to CurrentBlockIdentifier.Index can be queried. If a Rosetta implementation prunes historical state, it should populate the optional `oldest_block_identifier` field with the oldest block available to query. If this is not populated, it is assumed that the `genesis_block_identifier` is the oldest queryable block. If a Rosetta implementation performs some pre-sync before it is possible to query blocks, sync_status should be populated so that clients can still monitor healthiness. Without this field, it may appear that the implementation is stuck syncing and needs to be terminated.
  - `current_block_identifier` BlockIdentifier, required — The block_identifier uniquely identifies a block in a particular network.
    - `index` integer, required — This is also known as the block height.
    - `hash` string, required — This should be normalized according to the case specified in the block_hash_case network options.
  - `current_block_timestamp` integer, required — The timestamp of the block in milliseconds since the Unix Epoch. The timestamp is stored in milliseconds because some blockchains produce blocks more often than once a second.
  - `genesis_block_identifier` BlockIdentifier, required — The block_identifier uniquely identifies a block in a particular network.
    - `index` integer, required — This is also known as the block height.
    - `hash` string, required — This should be normalized according to the case specified in the block_hash_case network options.
  - `oldest_block_identifier` BlockIdentifier — The block_identifier uniquely identifies a block in a particular network.
    - `index` integer, required — This is also known as the block height.
    - `hash` string, required — This should be normalized according to the case specified in the block_hash_case network options.
  - `sync_status` SyncStatus — SyncStatus is used to provide additional context about an implementation's sync status. This object is often used by implementations to indicate healthiness when block data cannot be queried until some sync phase completes or cannot be determined by comparing the timestamp of the most recent block with the current time.
    - `current_index` integer — CurrentIndex is the index of the last synced block in the current stage. This is a separate field from current_block_identifier in NetworkStatusResponse because blocks with indices up to and including the current_index may not yet be queryable by the caller. To reiterate, all indices up to and including current_block_identifier in NetworkStatusResponse must be queryable via the /block endpoint (excluding indices less than oldest_block_identifier).
    - `target_index` integer — TargetIndex is the index of the block that the implementation is attempting to sync to in the current stage.
    - `stage` string — Stage is the phase of the sync process.
    - `synced` boolean — synced is a boolean that indicates if an implementation has synced up to the most recent block. If this field is not populated, the caller should rely on a traditional tip timestamp comparison to determine if an implementation is synced. This field is particularly useful for quiescent blockchains (blocks only produced when there are pending transactions). In these blockchains, the most recent block could have a timestamp far behind the current time but the node could be healthy and at tip.
  - `peers` Peer[]
    - `peer_id` string, required
    - `metadata` object

## Other responses

- `500` — unexpected error

---

[API](https://skmtc.net/tatum/apis/blockchain-data.md) · [All operations](https://skmtc.net/tatum/apis/blockchain-data/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tatum/blockchain-data/versions/8622ee4b8fae/schema)