To view this content, you must be a member of Electroverse's Patreon
Already a qualifying Patreon member? Refresh to access this content.
Since 1970, land thermometers show roughly twice the warming seen over the oceans. Ferdinand Meeus, a chemist and IPCC-listed expert reviewer, argues the gap is largely artificial.
Unlock does not work. koekkoek27@ziggo.m
I’m digging into why Peter.
Best,
Cap
I finally got, first site access and later, unlock privilege. Thank you, Cap. This must be driving you crazy. Good luck w/ your site security. I hate hackers. Oh! I see my avatar pic.
Cap, In response to your 2059 msg. From your Electroverse Down post, I can access the last 2 days articles.
Fantastic!
I can access via the new link – – Patreon login works too. Thanks, Cap!
Today, just now, I was able to access this page. Yesterday, when this first came out, I wasn’t.
Good to hear!
Thank you for the update.
Today’s EV entry page attempt says “This site can’t be reached,” so I am trying this comment to see if it processes.
The comment got through okay.
Please let me know how if you now have access to the content.
Best,
Cap
I am inside EV, because I had it still opened in a tab. Attempting to go to electroverse.info via a new tab still fails. Looks like I can access whatever is listed on this page, like videos & whatever other EV pages are displayed. The page I am on now is the April 24 page.
I was able to open a new EV entry page by right-clicking on ELECTROVERSE at the very top of the page and choosing “open in a new tab”
From AI:
Here’s a clean, technical summary they will understand immediately:
Subject: electroverse.info unreachable — DNS failure confirmed
I can still access Electroverse through an already‑open page, and the backend is functioning normally (comments work, admin replies come through). But accessing the domain directly returns “This site can’t be reached.”
External monitors also report the domain as down.
I tested the Cloudflare IPs directly:
The IPs respond with Cloudflare error 1003 and SSL protocol mismatch, which confirms:
This strongly indicates a DNS‑level issue, not a server outage.
Please check:
The site is functioning — the DNS path to it is broken.
Thank you for your help Jay.
I will get onto this Monday.
Best,
Cap
EV seems to be functioning; we just can’t get to it.
The website call is being intercepted or some such, like these things the AI suggested, I guess. I know little about it.
Was hoping the AI could look under the surface and specify the precise interruption.
On to next week!
(I am not being recognized now when posting)
You probably already know these things…
The admin needs to check:
1. Nameserver configuration at the registrarAre the Cloudflare nameservers still listed correctly?
2. Cloudflare DNS dashboardAre the A/AAAA/CNAME records still present?
3. DNSSEC settingsIf DNSSEC is enabled but misconfigured, SERVFAIL is the exact symptom.
4. Registrar account for unauthorized changesDNS hijacking attempts often target the registrar.
5. Cloudflare statusCloudflare may be blocking or rate‑limiting DNS queries.
Cloudflare blacklists many VPN addresses. Use Cloudflare and necessarily limit views.