mempool.space down?

[logfiles]

It's my favorite block explorer when I want visualized the average fee rates of the previously mined blocks and the position of the unconfirmed transaction in the mempool. I have been trying to access it for some time now with no success. Is anybody else having the same problem?

[TryNinja]

Yes, it's down. It seems like there is something wrong with their SSL certificate.

Meanwhile, you can use this fork: https://mempool.emzy.de/

[ABCbits]

I just checked it (at 09:58:53 AM GMT) and looks like the SSL certificate problem is already fixed.

On a side note, they have .onion mirror at http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/ which doesn't use SSL certificate

[logfiles]

A bump to this post.

It appears the clearnet domain of mempool.space has been down for several hours now. Not sure what is causing that, maybe DDoS attacks. Meanwhile, anyone who still loves to use mempool.space can still access it through;
Tor - http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/
Or the forked versions
1. https://mempool.emzy.de/
2. https://mempool.orangefren.com/

[TryNinja]

A bump to this post.

It appears the clearnet domain of mempool.space has been down for several hours now. Not sure what is causing that, maybe DDoS attacks. Meanwhile, anyone who still loves to use mempool.space can still access it through;
Tor - http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/
Or the forked versions
1. https://mempool.emzy.de/
2. https://mempool.orangefren.com/

I didn't notice it was down, but I did find strange that it was taking longer than usual to load.

Maybe I'll release a fork under bitlist later.

[nc50lc]

It appears the clearnet domain of mempool.space has been down for several hours now. Not sure what is causing that, maybe DDoS attacks. Meanwhile, anyone who still loves to use mempool.space can still access it through

Right now, sometimes it loads slowly; sometimes not, with "can't be reached" error.
And when it connects, it'll somehow get disconnected due to the "reconnecting" note near its header after a while.

But several "isdown" websites say that it's accessible.
The clearnet website is also accessible via Tor browser.

ISP or region specific probably.

[rat03gopoh]

Or the forked versions
1. https://mempool.emzy.de/
2. https://mempool.orangefren.com/

Thanks, I need that

ISP or region specific probably.

This makes sense. After changing my ISP, one of the problems was having difficulty accessing mempool even on different devices. I previously created a bot (for personal use) that notified me of recommended TX fees from the mempool. However, this issue discouraged me from updating the code to allow it to read recommended fees of less than ~1 sat/vB. My bot has been quite helpful for the time being.

[ABCbits]

Or the forked versions
1. https://mempool.emzy.de/
2. https://mempool.orangefren.com/

It's good to have some alternative. But FYI both website use older version, since both recommend 1 sat/vB as no priority while mempool.space recommend 0.2 sat/vB.

Maybe I'll release a fork under bitlist later.

I've no idea about your hardware to run bitlist, but mempool for production/lots of traffic is very demanding. Make sure to read https://github.com/mempool/mempool/tree/master/production.

[elda34b]

It's good to have some alternative. But FYI both website use older version, since both recommend 1 sat/vB as no priority while mempool.space recommend 0.2 sat/vB.

Do you know any up to date fork? I checked from my end and it seems mempool.space is still inaccessible. I tried looking around GitHub forks and some of them do host their own website, but I'm not sure if the community has a preferred alternative for mempool.space or not.

[salad daging]

It's good to have some alternative. But FYI both website use older version, since both recommend 1 sat/vB as no priority while mempool.space recommend 0.2 sat/vB.

Do you know any up to date fork? I checked from my end and it seems mempool.space is still inaccessible. I tried looking around GitHub forks and some of them do host their own website, but I'm not sure if the community has a preferred alternative for mempool.space or not.

It seems like this is an ISP problem that is limited, because I myself cannot access mempool.space unless I use a scrape proxy, while currently only using memepool.space from the other fork shared above.

I don't know if memepool.space is also part of the official fork?

How it looks

[nc50lc]

I don't know if memepool.space is also part of the official fork?

(lol) it's using comic sans.

Anyways, there are no "official" forks of it since anyone can host their own mempool.space blockexplorer and author doesn't endorse specific forks.
Be careful though since some of those may not be as private as the original, use those alternatives at your own discretion.

[ABCbits]

It's good to have some alternative. But FYI both website use older version, since both recommend 1 sat/vB as no priority while mempool.space recommend 0.2 sat/vB.

Do you know any up to date fork? I checked from my end and it seems mempool.space is still inaccessible. I tried looking around GitHub forks and some of them do host their own website, but I'm not sure if the community has a preferred alternative for mempool.space or not.

I don't, besides it's not easy to know whether other hosted Mempool is actually up to date unless you know all recent changes. Although yesterday and today i can access mempool.space without any problem. I wonder if something wrong with your internet connection or mempool.space selectively block certain IP/device as security measure.

[NotATether]

Maybe I'll release a fork under bitlist later.

I've no idea about your hardware to run bitlist, but mempool for production/lots of traffic is very demanding. Make sure to read https://github.com/mempool/mempool/tree/master/production.

And this is why I am still baffled at my persistent stubbornness of configuring servers with 32GB RAM.

I've had 64GB offered to me, as promos, with discounted prices, but my reaction was always the same "I don't need that much RAM".

Now the RAM shortage apocalypse is going to kick me in the balls.