Skip to main content
Skip to content
Crypto Trading

Crypto Trading Halts in 2027: What Cancel-Only, Post-Only and Reopening Really Allow

A working chart does not prove that a market can accept or match your order. This 2027 guide compares documented Kraken and Coinbase trading modes, explains cancellation and reopening uncertainty, and adds a local permission checker that keeps stale observations and unknown states visible.

A golden gate stopping luminous trading paths against a deep purple background.
Reading options: audio, text size & sections

Decentralised News · 2027 planning edition · Evidence reviewed 22 November 2026

What Matters

Check the exact market state and action, then reconcile your own orders. Cancel-only can allow exits from pending instructions while preventing new orders; an auction can show a price without offering immediate execution. A successful request, a permitted action and a confirmed fill are separate facts.

Evidence and method

This documentary comparison uses official Kraken and Coinbase trading rules, product references, auction documentation and status interfaces checked on 22 November 2026. It is a planning edition for 2027, not a live operational status report. Definitions are scoped to the cited spot-market services; they are not assumed to govern every derivatives, custody or transfer process. The checked sources even describe different matching behavior under a similarly named limit-only mode, which the article preserves. No incident-frequency study, real-money test, order submission or cancellation was performed. Numerical examples and the checker’s age threshold are hypothetical. The tool works locally and cannot verify a live market, account eligibility or a completed action.

DN Alpha Thesis

The useful recovery signal is a fresh, scoped permission record combined with a reconciled account state. “The exchange is back” is too broad to decide whether a cancellation can work, an order can rest, or a market can match. DN separates those questions and keeps prior execution uncertainty visible. This makes the article different from an uptime leaderboard or a generic trading-bot circuit breaker: it explains the exchange-defined operating state that the trader or bot must interpret. The result is a practical way to avoid turning a recovered connection into an unsupported assumption about execution.

DN Market Mode Permission Check 2027

This local checker uses documented definitions checked 22 November 2026. Enter an observed state yourself. It does not verify a live market or send requests. The age limit is your own assumption.

Documented mode permits this action type

Selected actioncancel
Matching under mapped modePaused or restricted
Observation age15 seconds (within your entered limit)
  • This is a documentary mode check, not live validation, account eligibility or execution confirmation.
  • A permitted cancellation still requires a confirmed resulting order state.
Scenario method and limits

The initial inputs and results are an original, synthetic DN example. They are provided to make the method reproducible, not as live prices, measured performance or a prediction for 2027. Change the inputs and download your own scenario above.

  • No live state is fetched or authenticated.
  • Documented definitions can change and must be rechecked.
  • Spot-mode interpretation does not establish derivatives, funding, liquidation, deposit or withdrawal behavior.
  • Auction permissions require phase details the checker deliberately does not assume.

The market can be visible without being tradeable

A chart updates, a balance loads and an order book appears. A trader reasonably assumes the exchange is back. The next market order fails, while an old limit order is still waiting for a reopening process the trader has not checked.

The problem is that “up” and “down” are poor descriptions of trading permissions. A venue can allow cancellations while rejecting new orders. It can collect limit orders without matching them. It can accept some order types while blocking others. A working website establishes none of those permissions by itself.

This 2027 guide focuses on the state of the market and the actions that state permits. It compares official Kraken and Coinbase documentation checked on 22 November 2026, with an accompanying local permission checker. It is not a live status monitor, an uptime ranking or a claim that either venue experienced a particular incident.

Four separate questions replace one green light

Before interpreting a recovery message, separate four questions: can the service be reached; can this specific market accept an instruction; can the instruction match; and what happened to your own earlier instruction?

LayerEvidence to inspectWhat it cannot establish alone
ConnectivityFresh successful response from the relevant serviceThat new orders or cancellations are permitted
Market permissionsCurrent product or engine mode and venue-specific definitionThat your account or order passes every other check
Matching stateTrading or auction phase, current book and execution feedThat your price and size will fill
Personal order stateOrder acknowledgement, execution records and cancellation resultThat a missing response means the order was never accepted

The distinction is especially valuable when an automated workflow spans more than one market. A service-level recovery can leave one product restricted. A cancellation channel can recover before matching resumes. A market-data feed can be reachable while a private account request still fails. Those are possibilities to check, not a universal sequence to assume.

Write the permission check as a sentence: “At this timestamp, this source reports this state for this product, and the current rule definition permits this action.” That is a reviewable observation. “The exchange looks fine” is not.

What the mode names mean in the checked documents

Kraken’s trading-mode guide separates normal operation, maintenance, cancel-only, post-only and limit-only states. Coinbase’s product reference exposes restriction flags including disabled trading, cancel-only, post-only and limit-only. These names require venue-specific interpretation.

Documented modeNew instructionsExisting-order cancellationMatching
Kraken maintenanceNo new ordersUnavailable in this modePaused
Kraken cancel-onlyNo new ordersPermittedPaused
Kraken post-onlyPost-only limit ordersPermittedPaused
Coinbase trading disabledRestrictedRestrictedNo permission inferred
Coinbase cancel-onlyNo new ordersPermittedPaused
Coinbase post-onlyMaker-only ordersPermittedPaused
Coinbase limit-onlyLimit orders; no market ordersPermittedCrossing limit orders may match

One material difference deserves attention: the checked Kraken support table describes matching as paused in limit-only mode, whereas Coinbase’s product documentation explicitly allows crossing limit orders to match in its limit-only state. A shared label is not a shared rule. If current live behavior or a newer official notice conflicts with a cached definition, treat the permission as unresolved until reconciled.

The table describes mode-level permissions, not successful outcomes. A permitted cancellation still needs confirmation. A permitted limit order can fail another check or remain unfilled. “Matching may occur” means that the engine can execute eligible orders; it says nothing about the quality or completeness of your own fill.

Post-only order instructions and a post-only market are different

An individual post-only instruction controls whether that order may take existing liquidity. A market-wide post-only phase controls the book’s operating state. The phrases look similar in an interface, but the scope differs.

Imagine a trader who normally uses a post-only limit order to seek maker treatment. During ordinary trading, another participant may later trade against that resting order. During a documented market-wide phase that suspends matching, acceptance of a new order does not mean anyone can execute against it yet. Confusing those situations produces a false impression of available exit liquidity.

It also changes what the trader should verify. For an individual order, check its submitted flags and acknowledgement. For a restricted market, check the product or engine mode, the mode definition and the transition conditions. A successful post-only submission is evidence of an accepted instruction, not evidence that continuous trading has resumed.

DN’s earlier maker/taker guide explains the individual-order fee distinction. This article addresses the market permission surrounding every participant’s orders. Keeping those questions separate prevents an otherwise useful order-setting rule from becoming an incorrect recovery signal.

A reopening auction is a process, not an executable quote

Coinbase’s book reference distinguishes auction collection, opening and completion. Indicative quotes can change; collection permits orders and cancellations without matching, while requests during the opening transition can be queued. An indicative opening price is therefore not a promise that a new instruction can trade immediately at that level.

Consider an illustrative market that last traded at 100 before a pause. During collection, the indicative reopening price moves from 98 to 96 as orders change. A trader with a buy limit at 99 should not calculate a realised two-unit benefit from the first indicative price. No completed execution has been established.

If the final opening price is 96 and the order receives a fill, the fill record determines the executed quantity and cash result. If the opening price is 100, the 99 limit may remain unfilled. If the trader submits a cancellation during a transition, the relevant question is whether the cancellation became effective before execution, not whether the button was pressed first on the trader’s screen.

The same reasoning applies to a bot that sees a crossed indicative book and interprets it as immediate arbitrage. It first needs to establish whether the feed represents a collection state, a matching transition or continuous trading. Subtracting a bid from an ask is not enough to establish an executable opportunity.

Scheduled maintenance does not guarantee a fixed reopening timetable

Coinbase’s Markets Trading Rules describe an intended scheduled-downtime reopening process involving cancel-only and auction stages, while retaining discretion over timing, resting orders and alternative reopening paths. A published process is useful preparation; it is not a countdown that authorises a client to resume merely because a timer expired.

Kraken’s maintenance-schedule reference provides a planning view distinct from emergency advisories. Its system-status reference explicitly separates the engine state from accompanying scheduled or emergency information. That supports two checks: what is expected to happen and what the engine reports now.

A sensible preparation record therefore contains the announced service scope, expected start and end, affected products, pending instructions and the specific signals required before normal activity resumes. The expected end time belongs in the record, but should not be the only recovery condition.

For a manual trader, this can be a short note with the relevant official pages and order identifiers. For a trading desk, it can be an explicit operating procedure. The important property is that the decision survives a change in the timetable without relying on someone remembering an informal assumption.

The hidden exposure is the order you assume disappeared

Suppose a hypothetical account holds 1 BTC and has an unconfirmed sell instruction for 0.4 BTC when connectivity fails. A second venue becomes available. The trader sells another 0.4 BTC elsewhere to replace the uncertain exit.

If the first sell never executed, the trader sold 0.4 BTC in total. If it executed completely, the trader sold 0.8 BTC. If it partially filled 0.2 BTC, the total is 0.6 BTC. The same replacement action creates three different outcomes because the original state remains unknown.

With a desired remaining holding of 0.6 BTC, those outcomes leave 0.6, 0.2 or 0.4 BTC respectively before considering transfer and account details. The arithmetic is simple; the difficult input is whether the first order filled. An operational incident does not convert that unknown into zero.

This example is not a recommendation to hedge, replace or hold. It shows why any contingency decision should record the unresolved quantity range. A trader choosing to act despite uncertainty should understand the possible combined exposure rather than treating the second action as a clean substitute.

When access returns, reconstruct the sequence from accepted instructions, fills, effective cancellations and current balances. An updated chart or a reassuring status banner cannot reconcile those records on its own.

Cancellation intent is not cancellation confirmation

There are at least three useful states: you decided to cancel; you sent a cancellation request; and the venue confirmed the resulting order state. A log that merges them into one “canceled” flag creates an evidentiary gap precisely when the connection is unreliable.

Keep the order identifier, cancellation request time, response or error, and final state distinct. If a response is missing, the safe description is “cancellation unconfirmed.” If execution reports arrive later, update the state from those reports rather than preserving the earlier assumption.

This matters even in cancel-only mode. The published mode can allow cancellations, yet your request might still fail to reach the relevant service or concern an order that already filled. Permission is an engine policy; confirmation is evidence about your instruction.

A recovery checklist should therefore count unresolved instructions, not merely open orders currently displayed in one interface. A missing row can mean a changed filter, completed execution, cancellation or delayed data. The reconciliation process determines which explanation fits.

Use the DN Market Mode Permission Check

The tool applies the checked mode definitions to a selected action. It does not query a live endpoint and does not send an order. Enter the venue, reported mode, intended action, age of the observation and the maximum age your own workflow accepts.

In the default illustrative scenario, Coinbase is entered as cancel-only, the action is cancellation, and the observation is 15 seconds old against a reader-chosen 60-second limit. The result says the documented mode permits that type of request and that the observation is within the chosen age limit. It does not say the observation is authentic or that the cancellation succeeded.

Change the action to a market order and the mode check fails. Change the observation age to 61 seconds and the result becomes stale under the same policy. Choose an unknown mode and it remains unknown. The checker does not quietly substitute full trading for an unrecognised state.

The age limit is a workflow choice, not an exchange service promise. A 60-second threshold may be inappropriate for a fast strategy; a slower process still needs a fresh state before committing capital. Even a recent response can become obsolete immediately after capture. The tool makes the assumption visible rather than claiming to remove that uncertainty.

Why an incident page and an engine state both matter

A status page supplies human context: affected components, incident updates and maintenance notices. An engine or product endpoint supplies a machine-readable trading state. Kraken’s status API documentation, for example, distinguishes summary, component, incident and scheduled-maintenance data. Documentation sample responses are not evidence of a current incident.

Use each source for the question it answers. A platform-wide incident can explain why a request failed without establishing that every market is closed. A product flag can establish a restriction without explaining its duration. A resolved incident can remove one cause of disruption without proving that all of your prior orders have reached final states.

When sources disagree, preserve both observations with timestamps and scope. Do not resolve the disagreement by choosing whichever permits trading. A dated record of an unresolved discrepancy is more useful than a confident but unsupported “operational” label.

For an automated system, this suggests a separation between market-permission logic and account-reconciliation logic. For a human operator, it means maintaining two lists: what actions the market currently allows, and what happened to your pending instructions. Clearing one list does not automatically clear the other.

A practical restart sequence

  1. Identify the exact service and product. Distinguish website access, market data, order entry, cancellations, matching and transfers.
  2. Capture the current official state. Save the observed timestamp, source and mode. Read a newer notice if the cached rule definition may be obsolete.
  3. Map the intended action to the mode. Check order type, cancellation permission and whether matching is active or deferred.
  4. Reconcile earlier instructions. Resolve accepted orders, fills and cancellations; retain an explicit uncertainty range where evidence is incomplete.
  5. Refresh balances and strategy inputs. Use current account data and current market conditions rather than replaying an old plan automatically.
  6. Resume only within the verified scope. One recovered product or channel is not evidence that every dependent service is ready.

For an unlevered spot purchase, stale permissions may mainly delay entry. For a strategy with opposing legs, unresolved execution can change the net position. For derivatives, separate contract rules can govern margin, funding and liquidation. A spot-market mode table should not be used to infer that those processes pause in the same way.

The commercial implication is straightforward: choose a workflow that can explain its behavior during restricted operation, not merely one that submits orders quickly in normal conditions. A well-documented recovery state and an auditable cancellation result can matter more than a marginal fee saving when the intended action is unavailable.

What this comparison can and cannot settle

The article establishes documented distinctions between modes and shows how to reason about their consequences. It does not rank actual outage frequency, test execution during maintenance, predict reopening prices, promise compensation or establish that a user can withdraw funds.

The 2027 edition label is a planning horizon. The source check occurred on 22 November 2026, and the relevant rule or API definition should be revisited before operational use. If a product introduces another state, the correct first result is “unmapped,” followed by a documentation review.

The decision to preserve is compact: current product, current mode, permitted action, observation age and personal order state. Together they describe what you know. Where one remains unknown, the uncertainty belongs in the result instead of being hidden behind an overall green status.

Frequently asked questions

Can I cancel an order during a trading halt?

It depends on the exact venue and mode. Cancel-only states are specifically designed to allow cancellation while restricting new orders. A full halt or maintenance state can restrict cancellation as well. A permitted cancellation still needs a confirmed result for your order.

Does post-only mean the same thing for an order and for an entire market?

No. An individual post-only instruction controls whether that order may take liquidity. A market-wide post-only phase can allow qualifying limit orders while suspending matching. Check both the submitted order flags and the market operating state.

Is an auction indicative price an executable quote?

No. It is information about a developing reopening process and can change before matching. The auction phase, your order terms, the final opening price and the actual execution record determine the outcome.

Does a resolved incident mean every earlier order was canceled?

No. Incident resolution concerns service operation. Earlier orders may have filled, partially filled, remained open or been canceled. Reconcile order and execution records rather than inferring their state from a status banner.

Does the DN checker connect to Kraken or Coinbase?

No. It applies cited documentary definitions to your entered venue, mode, action and observation age. It sends no request, holds no credentials and cannot confirm live permissions, account eligibility or order success.

Sources and verification

Primary documentation checked on 22 November 2026. Exchange rules, regional availability, fees and API behavior can change; recheck the exact product and account before using this 2027 planning guide.

  1. Kraken possible trading modes — Venue mode definitions and checked limit-only description.
  2. Coinbase Exchange product reference — Product restriction flags and matching behavior under limit-only.
  3. Coinbase Exchange auction/book reference — Indicative quotes, auction collection/opening phases and request handling.
  4. Coinbase Markets Trading Rules — Scheduled reopening process, discretion and definitions.
  5. Kraken maintenance schedule API — Scheduled planning view and separation from emergency incidents.
  6. Kraken system status API — Engine state distinct from advisory arrays.
  7. Kraken status API documentation — Summary, component, incident and maintenance data; sample responses are documentation only.

Related DN research

Method and corrections: This is a 2027 planning edition based on evidence available on 22 November 2026. Calculations are synthetic and are not a claim of executed trades, future fees or investment returns. If a cited rule changes, the exact product, documentation link and effective date are the evidence needed to update this analysis.

Change log: Initial research edition, 22 November 2026.

Get the most talked about stories directly in your inbox

Join the Decentralised News briefing for independent crypto, DeFi and AI analysis. No spam, unsubscribe anytime.