Phare Uptime

Monthly update for #Phare Uptime: September 2026

🌐 940 Active organizations (+35)
📈 65M Monthly uptime checks (+7M)
📄 708 Active status pages (+31)
🥰 72 customers (+5)
💰 €416 MRR (+€48)

Today is the 4th anniversary of my first commit on #Phare Uptime

~3900 commits, 500 millions uptime checks, ~2500 users that created an account, and too many weekends spent coding.

Monthly update for #Phare Uptime: August 2026

🌐 905 Active organizations (+27)
📈 58M Monthly uptime checks (+5M)
📄 677 Active status pages (+45)
🥰 67 customers (+9)
💰 €368 MRR (+€49)

Still slow, but still growing.

Replaced #Phare Uptime analytics stack to use #Vemetric over the weekend.

I went the extra mile and added a middleware with an EU-bound edge-script to anonymize IP addresses and used it as a proxy to run it all from a phare.io domain. It's more privacy-friendly, and way lighter on JavaScript bundle size than the previous PostHog implementation.

I documented the whole process here:
👉 https://phare.io/blog/privacy-first-analytics-on-the-european-edge-with-vemetric-and-bunny-net/

Fun anecdote: I exhausted my Vemetric free plan in less than 48h due to an uptime agent error that sent a false-positive notification to hundred of users 🙈

After almost two months of inactivity on #Phare Uptime, I finally shipped something: monitor group support for startus pages 😎

Monthly update for #Phare Uptime: July 2026

🌐 878 Active organizations (+65)

📈 53M Monthly uptime checks (+2M)

📄 632 Active status pages (+42)

🥰 58 customers (+6)

💰 €319 MRR (+€6)

For some reason, the last week of July saw a big jump in subscriptions with 5 new customers, and SEO traffic is picking up again, did Google change the algorithm again?

Monthly update for #Phare Uptime: June 2026

🌐 813 Active organizations (-26)
📈 51M Monthly uptime checks (=)
📄 590 Active status pages (+11)
🥰 54 customers (+2)
💰 €313 MRR (+€9)

Who could have foreseen that not working on the product for two months would reduce growth 😱

Monthly update for #Phare Uptime: May 2026

🌐 839 Active organizations (+8)

📈 51M Monthly uptime checks (-1M)

📄 579 Active status pages (+37)

🥰 52 customers (+5)

💰 €304 MRR (+€22)

Weird month overall, less traffic than earlier this year, and lost a few non-paying users due to an ongoing incident with my hosting provider. Paid customers did not churn, so there's that, and I passed €300 MRR!

Add private status pages to #Phare Uptime with three access controls:

IP allowlist: Grant automatic access to specific IP addresses or CIDR ranges. Requests from listed addresses bypass all other checks, making it the most seamless option for office networks or VPN exit nodes.

Access token: Append a secret token query parameter to any status page URL to grant access, great for programmatic access. Works on the main page, feeds, and badge endpoints. When a browser visits with a valid token, a session cookie is set for 1 hour, so subsequent visits don't need the token.

Access password: Visitors are prompted with a login screen before they can view the page. Simple and effective for internal pages shared with team members or customers.

This was a productive weekend 🤗

Monthly update for #Phare Uptime: April 2026

🌐 831 Active organizations (+44)
📈 52M Monthly uptime checks (+8M)
📄 542Active status pages (+41)
🥰 47 customers (+7)
💰 €282 MRR (+€42)

Back in December I migrated #Phare Uptime billing backend to #Paddle to let them handle VAT compliance for me.

While I was at it, I wanted to improve the billing experience for my customers with calendar-month billing cycles, on top of the existing flat subscription + metered billing that define Phare's pricing.

It was all doable, but exposed some interesting gaps in Paddle's API along the way. The implementation has been running in production for 3 months now without issues. If you're building metered billing on Paddle, I wrote up my findings and the workarounds I landed on for a clean implementation:

https://phare.io/blog/what-paddle-doesnt-tell-you-about-implementing-metered-billing/

Monthly update for #Phare Uptime: March 2026

🌐 787 Active organizations (+57)
📈 44M Monthly uptime checks (+2M)
📄 501 Active status pages (+47)
🥰 40 customers (+12)
💰 €240 MRR (+€54)

Kind of crazy to think I now host more than 500 status pages, and even more to think this number will double before the end of the year

Guess who discovered how to properly use pointers in GO ?

oh well

Added a Captcha on #Phare Uptime registration page, based on Altcha, self-hosted, it's actually just a few lines of codes. No dependency on third party services, no user IP sent to Californian tech bros, virtually 0 impact on human users.

And you can't see it unless you act like a bot 🤖

Two weeks of reworking every page for better information density, adding a search engine and filters, finally live in production ✌️

Reworked all pages layout of Phare over the past 2 weeks, added search / filters and many small goodies.

A ton of work to make, but I'm in love with the results.

Maybe I should refocus my SEO efforts

Finally seeing some sustained growth after changing #Phare Uptime pricing strategy