The status entry for the Blast (BLAST) network shutdown records a maintenance item that moved through several states on Coinbase's status page. The most useful reading is chronological: the shutdown was scheduled, then marked in progress, and finally marked completed. The entry also carries an explicit warning that users had to act to keep access to their funds.
That is the confirmed change. What follows separates what the page states from what it implies, and flags the questions a status entry of this type does not answer.
What the entry records, in order
The timeline has three labeled states, each with a date and time in PDT. The first scheduled notice appeared on Oct 7 at 15:50 PDT, saying the Blast network was being shut down by the project team. At the same timestamp, the entry moved to in progress, with scheduled maintenance described as currently in progress.
The final state is dated Oct 27 at 03:00 PDT and reads that the scheduled maintenance has been completed. Note the gap between the two: the entry was created and marked in progress on the same day, and the completion notice is dated roughly three weeks later. The page does not explain that gap.
| Status | Date and time (PDT) | What the entry says |
|---|---|---|
| Scheduled | Oct 7, 15:50 | The Blast network is being shut down by the project team. |
| In progress | Oct 7, 15:50 | Scheduled maintenance is currently in progress. |
| Completed | Oct 27, 03:00 | The scheduled maintenance has been completed. |
What the status labels mean here
A status page is a record of an operator's own view of a service event, not a general statement about the network. The labels are procedural. "Scheduled" marks an announced future change; "in progress" marks work the operator considers underway; "completed" marks the operator's closure of the item.
This matters because the underlying trigger described in the entry is external to Coinbase. The entry says the Blast network is being shut down by the project team, so the completed status describes how Coinbase handled that change, not a decision by Coinbase to end support on its own.
The user action clause
The strongest operational line in the entry is a warning: readers must take action to not lose access to their funds. The entry also specifies that BLAST not moved off of Coinbase before October 26, 2026 will not be accessible after the Blast network is shut down.
Read together, these two sentences form a deadline and a consequence. The deadline is October 26, 2026, and it precedes the Oct 27 completion timestamp. Anyone reading the entry today should treat the deadline as the controlling date, not the completion date.
- Check whether you hold the asset named in the entry.
- Note the cutoff date printed in the entry itself.
- Treat the completion notice as the operator's closing record, not as an extension of the deadline.
- Do not rely on a third party's summary when the status entry states its own date.
A worked reading of a similar entry (Hypothetical)
Suppose an exchange posts a shutdown notice on day one, moves it to in progress on the same day, and closes it with a completed note on day twenty-one. A user who sees only the completed note has no picture of the deadline or the action required. A user who reads top to bottom sees the warning first if the page orders entries newest-first.
For illustration only, if a reader checks the page on day ten and the cutoff falls on day nineteen, that leaves a nine-day window between the check and the deadline. This is a Hypothetical example, not a figure drawn from the entry.
Timeline reading checklist
- Identify the earliest entry and the latest entry separately.
- Confirm the time zone used in each timestamp; this entry uses PDT.
- Find any explicit user action and the date attached to it.
- Distinguish a network shutdown by a project team from an exchange outage.
- Note whether the completed notice explains the reason; here it does not restate the cause.
What the source does not say
The entry does not state what happens to balances held past the cutoff, whether any conversion or credit occurs, or what the withdrawal options were before the deadline. It does not give a reason for the project team's decision to shut down the network.
It also does not explain the interval between the Oct 7 in progress entry and the Oct 27 completed entry. No amount of funds affected, no number of users, and no process for late claims are given. Readers should not assume any of these details from the entry alone.