Mempool.space's node issues

[paid2]

I don't know if anyone else noticed,

But for the 3 last hours mempool.space has stopped working. Balances are not updated for my addresses and they missed some blocks. They are still online, but infos are not updated. Last block on mempool.space is 824139 while with my node 824160.

We should be carefull and don't rely on it until their node is reconnected again

[F2b]

Weird, for me it seems fine. Last block: 824162.

I'm waiting for a recent tx to be visible in their mempool, tho (actually two of them, but I can see the first one; it was half an hour ago).

Edit: in the mempool size graph, however, for about two hours, all of the 1sat/vB tx were missing. Idk if it's related or not.

[Sunderland]

Looks fine for me now, I can see the block updating from 82461 to 82462. Maybe restart the browser? or close then reopen the Mempool page?



Edit: yeah I can see the issue now, thanks F2b and Zaguru12

[Zaguru12]

Looks fine for me now, I can see the block updating from 82461 to 82462. Maybe restart the browser? or close then reopen the Mempool page?

OP was actually right on the mempool.space not updating some infos I actually had same issue from here, I was constantly reconnecting it but it wasn’t working. It is just some minutes after the OP opened a thread that it started working fine. As for the OP this is part of the reason why running your own node is mostly advice so you don’t depend on third parties

[apogio]

Hello.

It was definetely their node's issue. Personally I run mempool explorer on my node and it worked perfectly during that time. So it's not a problem with the app, but rather with the underlying node.

It is ok now, as far as I can see.

[DaveF]

Considering the crazy usage their entire page / domain has to get with so many people hitting the page over and over and the fact that it's a free service with no ads it's kind of impressive how well it does hold up.
But, over the years it has 'burped' before usually it's back in a few minutes.

Would be interesting to know their usage stats and what they do have on the back end running everything.

-Dave

[NotATether]

Next time you can see if the issue is present on the development version of the website which is https://mempool.ninja, it is made by the people behind mempool.space as a testing ground for new changes, so it is possible that fixes appear here first, before they are pushed to the main site.

It was definetely their node's issue. Personally I run mempool explorer on my node and it worked perfectly during that time. So it's not a problem with the app, but rather with the underlying node.

It is difficult to see how a bitcoin node could miss so many blocks from peers unless it was a network issue, in which case it would make perfect sense.