A quick note from the PulseWatch team

Summer break: development paused

Starting this month, the PulseWatch team will be taking a well-earned summer break. This means that all active development work, including features and improvements we've been working on, will pause until we're back in September.

📌 What this means for you No new feature releases, patches, or development updates will ship during this period. Everything currently in progress will resume exactly where it left off when the team returns. Nothing is being cancelled, just paused.

We know some of you have been looking forward to certain updates, and we genuinely appreciate your patience. The team has been heads-down for a while now, and this break is an important part of making sure we come back energized and ready to ship great things in Q3 and beyond.

🛑

Development paused

All in-progress features and updates are on hold for the duration of the break. We'll publish a full roadmap update when we return.

🔁

Back in September

The team returns September 1, 2026. Development will resume immediately, with priority given to the items already in progress.

The platform itself will continue running normally throughout the break. That said, we want to be upfront about one important limitation during this period.

Incident response: delayed during break Should any incidents or downtime occur while the team is away, please be aware that we will not be able to respond immediately. With the team offline, our usual response times will not apply. We will address any reported incidents as promptly as possible given the circumstances, but delays should be expected. We apologize in advance for any inconvenience this may cause and appreciate your understanding.

US cluster: still on v4.1

We're aware that the US cluster has not yet been updated to PulseWatch v4.2, and we want to be upfront about that. This is something we've been actively working to resolve, and it remains a priority for us.

⚠️ US Cluster Status The US cluster is currently running PulseWatch v4.1. Users on the US cluster do not yet have access to the features and fixes introduced in v4.2. The EU and other regions have already been updated successfully.

The rollout has taken longer than expected due to a compatibility issue we identified during the staged deployment process. Rather than push an unstable update, we made the call to hold and investigate properly. We think that was the right decision.

✅ What we're doing about it Our infrastructure team is actively working on the US cluster migration. We'll post a dedicated status update as soon as a migration window is confirmed. If you're on the US cluster and have questions in the meantime, feel free to reach out through the usual support channels.

We understand this is frustrating, especially if you've been waiting on v4.2 features specifically. We're not going to rush it and risk platform stability. But we treat it as a high priority and will share updates as soon as we have something concrete to share.

From the team

We're genuinely proud of what PulseWatch has become, and that's entirely thanks to the people who use it and push us to make it better. Taking this break isn't something we do lightly. It's something we do so that the work we come back to is thoughtful, high-quality, and worth your time.

Thank you for your continued trust and support. We'll see you in September.

A note from the CEO

👤
Luca CEO & Assistant Manager, PulseWatch

Hey. I just wanted to add something that I don't think gets said enough. I'm genuinely blown away by what this team has pulled off over the past couple of years. It impressed me. The amount of care and effort that's gone into PulseWatch, the late nights, the hard calls, the "let's just fix this properly" moments, it adds up. And I see it. I'm incredibly proud of every single person who's been part of this.

On the US cluster, I know it's been a wait, and I get it. It's not where we wanted to be right now. But here's what I can tell you: the deployment is coming. When it does go live, we'll have engineers standing by, ready to jump on anything that comes up. It won't be the same scale as our other clusters, so I want to be straight with you about that. There will be people watching, and they will respond. We will monitor the rollout after we switch it on.

And yes. Even though development is on pause for the summer, we are shipping v4.2.1 in the coming weeks. It's a focused release: more detailed Pings, better data, the kind of thing that makes the product genuinely more useful day to day. We're excited about it.

Anyway, thanks for being here. Thanks for using what we build. It means more than you know.

Luca, CEO
PW
PulseWatch TeamTransparent infrastructure, always. All posts →

Comments

Questions, corrections or thoughts on this post? Join the thread below.