Thanks to @quine.de you can now declare Phare resources as NixOS config. Check out the documentation 👉 docs.phare.io/integrations...

Phare NixOS Module (Community) - Phare Documentation

Declare and manage Phare resources with infrastructure as code using the community-built NixOS module.

docs.phare.io

quine.de@quine.de · 4d ago

phare-nix lets you declare your @phare.io uptime monitors as NixOS config. Turn on monitoring for a service with one switch, reconciled to @phare.io on every rebuild. Check it out at: codeberg.org/pSub/phare-nix

Today is the 4th anniversary of my first commit on @phare.io 🎂🎉

🚧 Scheduled Maintenance Windows One of the most requested feature of the past few months is finally here, whether you're upgrading databases, shipping breaking API changes, or rebooting a server, keeping your users in the loop before and during downtime makes all the difference.

Phare's analytics stack just went 100% European 🇪🇺. More privacy-friendly, lighter on JavaScript, built with @vemetric.com analytics and @bunny.net Edge Scripts. buff.ly/QzoLh5U

Privacy-first analytics on the European edge with Vemetric and Bunny.net

How Phare replaced PostHog with Vemetric and Bunny.net Edge Scripts to get lightweight product analytics, keep all data in Europe, and focus on organization-level metrics.

phare.io

🧹 Tidy up your status page with component groups You can now organize your monitors into customizable, collapsible groups to your status page visitors a clearer view of system health. Drag and drop monitors into groups, reorder sections, and collapse groups directly on your public status pages.

🫣 Keep your uptime data private You can now restrict access to your status page using up three access controls, available now to all Scale plan customers. 🧵

It was about time to add proper Uptime Monitoring + a Public Status page for Vemetric :D Powered by phare.io 🙌

Happy to announce that Phare is now part of @infobip.bsky.social Startup Tribe. Leveraging their product stack and global network we'll allow taking Phare's alerting capabilities to the next level with worldwide SMS & voice coverage, ensuring you know immediately when your infrastructure breaks.

Phare's incident AI summary and post-mortems are now powered by Mistral Small 4 😸

Phare just hit 500 hosted status pages. 🎉 This is a big milestone and the craziest part is that this number will more than double before the end of the year. Cheers to everyone using it, on to the next 500.

Phare status pages just got a big upgrade 🌗 You can now fully customise the design with flexible colours, layout styles, and... dark mode is finally here! There’s also a full uptime and incident history view, plus a new RSS feed for pushing updates straight into Slack.

You can now pull Phare monitor data into SquaredUp and build dashboards alongside the rest of your stack. This makes it easier to share monitor status, track health, and keep everything in one place. Thanks to the @squaredup.com team for the collaboration. 👉️ Check it out here: buff.ly/pEjs8N8

The long-awaited first-party Phare Terraform provider is now in beta and ready for you to automate your monitoring setup with infrastructure as code.

🤖 Phare got a lot more programmable! You can now create organization-scoped API keys that give you access to all the projects in your org, perfect for small teams, or infrastructure provisioning (is that a spoiler?).

⏱️ More control over incident timing in Phare Incidents can now be created with precise start and end times, adjusted if detection was late, or created for events that already happened. You can also choose what kind of update is published at creation time, with full flexibility to add more later.

Phare was selected to join @bunny.net Hopstart program and placed 1st 🥇 in the first cohort ! It’s great validation from a European company that builds serious infrastructure and supports people shipping genuine products. 👉 phare.io/blog/phare-j...

Phare joins Bunny.net Hopstart

Phare joins Bunny.net’s Hopstart program and places 1st in the first cohort. Learn how Bunny.net helps power fast status pages, edge uptime monitoring, TLS management, and DDoS protection for Phare.

phare.io

bunny.net@bunny.net · 8mo ago

Announcing the three founders selected for HopStart Cohort No. 1: 🥇 Nicolas Beauvais of Phare 🥈 Adam Lacey of Split Hero 🥉 Carlos Effio of uDocz Find out more about what they’re building and how to apply for HopStart on our blog. Link in the replies👇

🏗️ Webhooks in Phare just got a serious upgrade Payload schemas now support loops and clearer templating, all default schemas were revamped to expose more data out of the box.

Happy to partner with @ilert.bsky.social on this native integration to provide on-call teams with AI-first incident management. Even better, this is a partnership between two European companies, strengthening the observability stack in Europe 🇪🇺 Big thanks to the ilert team for the collaboration 🙌

ilert@ilert.bsky.social · 8mo ago

🔁 ilert now has a native integration with @phare.io! Teams can pair Phare’s Uptime monitoring with ilert’s AI-first incident management to reduce MTTR, improve reliability, and meet strict GDPR and security requirements – all while keeping data in the EU. www.ilert.com/integrations...

💰 Curious about Phare’s business metrics? An open stats dashboard is now live, showing real numbers: user registrations, monitors created, alert volume, revenue, costs, all in the open. Check it out here : phare.io/open

Earlier this month, Phare migrated its billing from Stripe to Paddle for proper VAT handling, and fewer US dependencies. The billing experience was also improved, with better cost forecasting and clearer payment flows. Same price, same features. A solid start to 2026 🥳

🇫🇷🥖 Phare launches: Le Uptime Monitoring A brand-new monitoring region is now live in France, humming with that signature hon hon hon server noise. Expect uptime as fast as a TGV*, incidents that dramatically shout “SACRE BLEU”, and a special Parisian luxury experience…

🎨 New in Phare: Refreshed Dashboard Design  The dashboard got a proper with full-width layouts, a search box to quickly find that monitor hiding on page 3, and filters to narrow things down to exactly what you need.  A small UI refresh, but a massive quality-of-life boost 👌

The pure bliss of running on 100% European 🇪🇺 infrastructure is that nobody notices when you go down, but you can still brag about being up when everyone else is affected by the Cloudflare outage.

🤯 New in Phare: Incident AI Incidents now come with AI-generated summaries and post-mortems, automatically giving you a clear overview of what happened, no manual write-ups required. Powered by Mistral’s Magistral Small model, and it’s already available on all plans!

🧠 Smart Incident Merging is here Reduce alert noise with Smart Incident Merging. Similar incidents are automatically grouped together within a configurable time window, helping you stay focused without drowning in duplicate notifications.

🔔 New in Phare: Ntfy integration You can now send incident alerts straight to your Ntfy application. The integration supports custom server hostnames, topic-based alerts, and access token authentication, and it works with all existing alert events from day one.

🧵 New in Phare: Slack threads for incident alerts It took a bit longer to roll this out, Slack’s validation process is… thorough 😅 All incident notifications for the same incident now land in a dedicated Slack thread, keeping your main channels clear and easy to follow.

🧵 New in Phare: Discord threads for incident alerts All incident notifications for the same incident now land in a dedicated Discord thread, keeping your main channels clear and easy to follow. You’ll just need to reinstall the integration once to grant thread permissions.

📩 New in Phare: Email threads for incident alerts Email notifications about the same incident are now grouped into a single email thread, so you can follow the full conversation without digging through clutter. One incident = one thread = clean and simple 👌

📣 New in Phare: Alert rule filtering for incident events You can now set alert rules to only trigger for specific incident types. That means cutting down the noise from manual incidents, or sending alerts to different channels, or even integrations.