> For the complete documentation index, see [llms.txt](https://gitbook-docs.coinmetrics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-docs.coinmetrics.io/access-our-data/status-page.md). # Status Page ## Overview Our Status Page reports the operational state of every Coin Metrics data product and service, announces planned maintenance, and publishes a notice each time we recalculate or clean historical data. Subscribe at [status.coinmetrics.io](https://status.coinmetrics.io/). Data change notices are how we tell you that history you have already pulled has been corrected, so a subscription is the most reliable way to know when to backfill. ## Components The page carries three kinds of post, each filed against a component: incidents, data change notices, and scheduled maintenance, whether on our own infrastructure or at a source we depend on. Components are grouped in this order. | Group | Components | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Market Data Products | Market Data Feed, CM Prices, Indexes (the Coin Metrics Bletchley Indexes), Reference Data | | On-Chain Data Products | Network Data Pro, ATLAS, FARUM | | Services | Pro API v4, Community API v4, Website, Mobile App, Flat Files, Frontend Tools (Coverage, Daily Network Metrics Availability, and the Charting Tool) | | Data Change Notifications | Eight components, listed below | | Labs | A single component rather than a group, covering experimental prototypes | | Third Party Data | Market Data Vendor and Network Data Vendor, for problems originating upstream at a supported exchange or node | | Maintenance | Data Center Maintenance | | FFIOMD API | HTTP API, WebSocket API | ### Data Change Notifications These eight components are subscribed to separately from the incident components, so following a product's incidents does not deliver its change notices. | Component | Covers changes to | | ------------------------ | --------------------- | | Market Data Feed Changes | Market Data Feed data | | CM Prices Changes | Reference Rates data | | Network Data Pro Changes | Network Data Pro data | | ATLAS Changes | ATLAS data | | FARUM Changes | FARUM data | | CMBI Indexes Changes | CMBI index data | | Reference Data Changes | datonomy data | | Flat Files Changes | Flat Files data | ## Reading a data change notice Every recalculation notice states its scope in the same fields, so one read tells you whether it touches data you hold. | Field | What it means | Example | | -------------------- | ----------------------------------------------------------------- | ---------------------------- | | Data Type | The dataset that was corrected | Reference Rates USD | | Assets or Markets | The specific assets, or the specific markets, that were corrected | `fun`, `gno`, `leo`, `paxg` | | Metrics | The affected metrics, when the change is metric-specific | `CapMrktCurUSD`, `IssTotUSD` | | Frequencies Impacted | The affected frequencies, or every frequency | `1s`, `1h` | | Time Range of Impact | The historical window that changed | 2026-06-17 to 2026-06-28 | {% hint style="info" %} Corrected values are live as soon as the notice publishes. If a notice covers data you have already stored, re-request that time range from the API, or re-download the affected files, to pick up the corrected values. {% endhint %} ## Statuses and updates Each component reads Operational, Degraded Performance, Partial Outage, Major Outage, or Maintenance, color-coded from green through red with blue for maintenance. Incidents post updates as Investigating, Identified, Monitoring, and Resolved, and maintenance as Scheduled, In progress, and Completed, so a single issue generates several notifications. **Past Incidents** covers roughly the last two weeks, with the older archive under **Incident History**. ## Subscribing 1. Go to [status.coinmetrics.io](https://status.coinmetrics.io/) and select **Subscribe to Updates**. 2. Choose a channel and enter the destination. Email and text message send a one-time code to confirm. | Channel | What arrives | | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- | | Email | Incidents created, updated, and resolved | | Text message | Incidents created and resolved, without the intermediate updates | | Slack | Incident updates and maintenance messages, through the Atlassian Statuspage app | | Webhook | Incidents created, updated, and resolved, plus any component status change. You supply the endpoint and an email address we notify if it fails | | RSS or Atom | The full incident history, with no subscription needed | {% hint style="warning" %} The subscribe form has no per-component picker, so one subscription delivers every notification the page publishes. To follow a single issue instead, use the **Subscribe** control on that incident. {% endhint %} ## Programmatic access Feeds and a read-only JSON API let you wire status into your own monitoring. | Resource | URL | | --------------------- | ------------------------------------------------------------------ | | RSS feed | `https://status.coinmetrics.io/history.rss` | | Atom feed | `https://status.coinmetrics.io/history.atom` | | Overall status | `https://status.coinmetrics.io/api/v2/status.json` | | Components | `https://status.coinmetrics.io/api/v2/components.json` | | Incidents | `https://status.coinmetrics.io/api/v2/incidents.json` | | Scheduled maintenance | `https://status.coinmetrics.io/api/v2/scheduled-maintenances.json` | | Everything at once | `https://status.coinmetrics.io/api/v2/summary.json` | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://gitbook-docs.coinmetrics.io/access-our-data/status-page.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.