---
description: Information regarding our historical Solana data and how to interact with it.
---

# Overview

All historical data is stored on our own servers which is hosted on-premise to give users the fastest historical data retrieval times possible. So no external cloud dependencies!

## Historical Supported RPC Methods

* [getBlock](overview/getblock)
* [getBlocks](overview/getblocks)
* [getBlockTime](../solana-rpc/http-methods/getblocktime)
* [getBlocksWithLimit](overview/getblockswithlimit)
* [getFirstAvailableBlock](overview/getfirstavailableblock)
* [getSignaturesForAddress](overview/getsignaturesforaddress)
* [getSignatureStatuses](overview/getsignaturestatuses)
* [getSlot](overview/getslot)
* [getTransaction](overview/gettransaction)

## How To Use

Utilize any of the above RPC methods as normal but against the `/historical` URL path, while making sure to either omit the commitment level parameter all together or specify the "finalized" commitment level.

{% hint style="warning" %}
If you try to make a RPC request to the historical endpoint using a commitment level below "finalized", then you will receive an error letting you know that is not supported.
{% endhint %}

### Example URL:

```
https://basic.rpc.solanavibestation.com/historical?api_key=API-KEY
```

To verify that you are in fact querying the historical data back-end storage, you can check the HTTP response for the following header:

```
X-Historical-Data: true
```

Historical data is only ingested and stored as block data becomes "finalized". There is a small delay after a block becomes finalized before it is queriable by users. This is typically less than a few seconds. If you need to query data that has not become ingested to the historical back end yet, then you can still do so by omitting the /historical URL path, however data returned will only be what is stored on the specific RPC node you get routed to which typically only consists of data stored from the past 12-24 hours.
