ChangeNOW incident

Temporary delays with processing HBAR, TON, KAS and others

Major Resolved View vendor source →

ChangeNOW experienced a major incident on June 9, 2026 affecting Withdrawals and Exchange Processing and 1 more component, lasting 22d 23h. The incident has been resolved; the full update timeline is below.

Started
Jun 09, 2026, 12:27 AM UTC
Resolved
Jul 02, 2026, 12:25 AM UTC
Duration
22d 23h
Detected by Pingoru
Jun 09, 2026, 12:27 AM UTC

Affected components

WithdrawalsExchange ProcessingHedera Hashgraph (HBAR)Casper (Mainnet) (CSPR)Toncoin (TON)Ondo (ONDO)Kaspa (KAS)Hyperliquid (HyperEVM) (HYPE)

Update timeline

  1. identified Jun 09, 2026, 12:27 AM UTC

    Hello there, Currently we experience temporary delays with processing few tokens, due to the delays by our liquidity provider. Affected assets: xtz,icx,hbar,egld,steth,grt,mbox,celo,xdc,cspr,op,ton,boba,ctc,gods,injerc20,flr,velo,lmwr,kas,wldop,coremainnet,mnterc20,ethlna,pol,mntmainnet,hntsol,prime,wemixmainnet,manta,ondo,ena,aiozerc20,mew,ethfi,usde,ponke,safe,brettbase,mog,render,ath,l3,sundog,popcat,degen,mogbase,hmstr,cgptbsc,carv,puffer,dbr,grass,taiko,tai,mplx,tokenerc20,swell,ol,chillguy,morpho,apex,major,zrc,kmno,arty,zerebro,virtualbase,hype,sonic,animeerc20,plume,toshi,vvv,gps,xter,zig,obt,order,bera,cookiebase,b3,cookiebsc,avl,diam,alch,flock,red,roam,sosoerc20,bmt,a8,mavia,br,kilo,partibase,maviabase,sosobase,corn,fhebsc,ferc20,hyperbsc,hypererc20,signbsc,doodsol,zkjerc20,laerc20,avlerc20,spkerc20,spkbsc,newterc20,icntbase,pumpsol,eraerc20,usdeton,homebase,vinubsc,sderc20,camperc20,usd1trc20,nomerc20,xanerc20,yberc20,metsol,recallbase,assethub,elizaossol,mon,pieversebsc,wetsol,skrsol,literc20,usdcmon,birbsol,usaterc20,triabsc,aaplxsol,aztecerc20,googlxsol,coinxsol,metaxsol,hoodxsol,roboerc20,amznxsol,mcdxsol,usdserc20,edgeerc20,basederc20,usdcmnt,bsbbsc,usdcseievm,deepsui,billerc20 During this time, you may notice that the status on the exchange page stays stuck on "exchanging" or "sending to you." Our team is aware of the issue and we are already on it! We will notify you once the issue is resolved.

  2. resolved Jul 02, 2026, 12:25 AM UTC

    This incident has been resolved.