Économie
Paxos resumes processing crypto withdrawals on Ethereum
Paxos reported delays at 00:01 UTC on November 9. It announced that processing had resumed at 00:13 UTC and declared the incident resolved at 00:54 UTC.

Customers could submit requests during the slowdown
Paxos reported delays processing crypto withdrawals on Ethereum at 00:01 UTC on November 9. In its first status update, the company said customers could continue submitting requests. Processing could take longer than usual. The report concerned the withdrawal service provided by Paxos. The update gives no indication of a network-wide Ethereum interruption and lists no affected tokens.
The operator identified two affected access points for transfers, its dashboard and its v2 API. The dashboard lets users request and track operations through an interface. The API lets an application communicate with the transfer service. Paxos listed both channels to describe the scope of the incident within its service. The update gives no count of delayed requests for either channel.
Processing resumed before the incident was closed
At 00:13 UTC, twelve minutes after its first message, Paxos said it had applied a fix and resumed processing withdrawals on Ethereum. The team then began monitoring the incident. According to the operator, that step meant processing was underway again. The update gives no figure for how quickly queued requests were processed or how long any individual request waited.
Paxos declared the incident resolved at 00:54 UTC. Fifty-three minutes elapsed between the first message and the public closure, including forty-one minutes of monitoring after the resumption announcement. That duration measures the time between published updates. It gives no precise start time for the slowdown and establishes no fifty-three-minute wait for every request submitted during that window.
Tracking a request and its confirmation on Ethereum
In a withdrawal service, receiving a request, processing it through the intermediary, and confirming it on the network are separate steps. An interface can accept a request while the service that processes it is running behind. Once a transaction is sent to Ethereum, confirmation depends on the network. Paxos’s updates locate the issue in withdrawal processing and do not specify whether any transactions had already been broadcast.
The public incident report gives no technical cause, count of affected withdrawals, or maximum delay for users. It records when Paxos announced the return of processing and when the operator closed the incident. For an individual operation, its status in the dashboard or API remains the reference provided by Paxos. If a transaction has been broadcast, its identifier can be used to track its status on Ethereum.
