Crypto Agent Desk
Menu

Use casesPrice / level alerts

02 · Alerts

Venue status monitor

A monitor for exchange status pages, withdrawal pauses, and basis that blows out while a venue is impaired.

Level
Advanced
Cadence
While you have balances or positions on the venue; reviewed whenever an incident opens
Read
8 min
Updated

Definition

A venue status monitor watches the status pages and incident notes of venues where you have risk, and optionally compares that venue’s perp to a hedge venue. It is an operations alarm. It does not move funds.

Who it is for

Traders with balances or open perps on venues that publish an incident feed.

Job to be done

Tell you when a venue you use reports an incident, a withdrawal pause, or a basis gap that showed up while the venue was impaired.

Human gate. You confirm the incident on the venue’s own status page before you cancel, hedge, or withdraw. The agent does not initiate a transfer.

Inputs and outputs

Inputs

  • Venues where you have balances, open orders, or positions
  • The official status page or incident feed URL
  • Optional hedge venue for a basis check
  • What you want paged: withdrawals, trading halt, matching delay, or all incidents

Outputs

  • A message quoting the incident title, state, and time
  • Whether your book on that venue is positions, balances, or both
  • Optional basis versus the hedge venue, labeled as a snapshot
  • A link back to the status page

Step-by-step workflow

  1. 01Bind venues to balancesIf you have nothing there, do not watch it. Incident tourism will drown the one venue that matters.
  2. 02Subscribe to the official feedSave the URL in the config. The agent may summarize the latest incident, and it must quote it.
  3. 03Define page-worthy statesWithdrawal pause and trading halt are the usual ones. A scheduled maintenance note can be a digest item instead of a page.
  4. 04Add basis only as contextIf you have a hedge venue, include one snapshot. Label it so nobody treats a halted book as executable.
  5. 05Close the loopWhen the status page changes state, send one update. Do not send a stream of identical reminders.
  6. 06Human gateYou decide whether to pull orders, reduce, or wait. Transfers are a manual act on the venue after you have read the notice.

Suggested tool types

These are categories of tools, not product picks. Crypto Agent Desk does not certify vendors and does not run an affiliate program.

TypeWhy it is here
Status page or incident feedPrimary source. Social posts are not the incident.
Read-only balance and position snapshotSo the alert knows you are exposed. No withdrawal scope.
Price feed on the venue and a hedge venueBasis context while matching is impaired.
Alert transportIncidents should reach a channel you check when you are away from the book.

Risks and failure modes

  • Rumor before the status page

    A social post can lead the status page and can also be wrong. Page on the official feed; mention rumors only as unconfirmed.

  • Basis as a trade idea

    Basis blows out for mechanical reasons during an outage. The monitor reports it. It does not tell you to arb a frozen book.

  • Stale "resolved"

    Resolved on the status page is not the same as withdrawals flowing. Keep the alert open until you see the state you care about.

Operator notes

Outage trades are where people pay the spread twice. The monitor’s job is to get the official sentence in front of you while your orders are still your orders.

Message shape

VENUE incident: TITLE. State: STATE. Started: TIME. Your exposure: positions / balances / none on file. Hedge basis snapshot: VALUE or not checked. Source: STATUS_URL. Not a transfer instruction.

Prompt you can paste

Summarize the latest incident from this official status text: STATUS_TEXT.
My exposure note: EXPOSURE.
Page me only if the state is in PAGE_STATES.
If you include basis, label it as a snapshot and not an executable arb.
Quote the incident. Do not tell me to withdraw, cancel, or hedge.

Done when

You can tell a real incident from a scheduled note, and the message always points at the status page rather than a screenshot of a reply.

FAQ

Should this auto-cancel orders?

Not in this playbook. Canceling into a partial outage can be worse than leaving a resting order. That decision stays manual.

What if the status page is down too?

Say so. "Status page unreachable since TIME" is a valid alert. Do not replace it with a guess from social media.

How is this different from a news digest?

A digest can mention an incident later. This monitor exists to reach you when a venue holding your risk changes state.

Published . Updated . This is an operating playbook, not a recommendation to buy, sell, or hold any asset.

Newsletter

Get the next playbook note

One playbook note when there is something worth filing. No token calls. The signup does not send yet — Resend (or another mail API) is not connected.