Mark what changed, right on the graph
Add an annotation for a deploy, a config change or a migration, and it appears on your response time chart at that exact minute. The next time the line moves, the reason is already sitting beside it.
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Add an annotation for a deploy, a config change or a migration, and it appears on your response time chart at that exact minute. The next time the line moves, the reason is already sitting beside it.
A jump from 1,700 ms to 2,900 ms is just a number until you know what happened at a quarter past eleven. With the deploy marked on the chart, the question mostly answers itself before anyone opens a terminal.
Mark the change, then mark the rollback. What sits between the two markers is the evidence: how long the regression really lasted, whether the revert landed, and what normal looked like before any of it started.
Nobody remembers why response times stepped up last spring. The annotation does, along with whatever you wrote in the description: the reason, the ticket, the link to the release.
Trusted by teams at companies around the world
"Pulsetic made monitoring something I barely think about anymore. The interface is clean and the tracking is real-time, so I can glance at my site’s performance and get back to work."
Senior Software Engineer at ASML
"Pulsetic is easy-to-use and simple to get started. As an agency, I like that it includes unlimited status pages, because I can create one for each of my clients. Pulsetic includes every alert channel that I want, and advanced settings that give me greater confidence in the uptime. I can require that a response include certain text and respond within a certain timeframe in order for a site to be considered online. This gives me assurance that we would be notified if there were major performance issues or a bad deployment that made the site unusable. These features come with every paid plan, so our monthly bill is predictable. The API is a huge bonus on the teams plan. We have used it to add maintenance windows for certain monitors automatically based on events that happen in other software we use."
CEO at NorthBuilt
"Pulsetic’s monitoring is easy to set up via their super clean, user-friendly UI. I was up and running within only a few minutes. A helpful knowledge base is available for webmasters to refer to if needed. Pulsetic’s pricing is also some of the most competitive in the industry. I highly recommend them for emerging and established agencies alike."
Owner at Sporulate Design
"Pulsetic is easy to set up and integrate. You don’t need much time to get it running. The interface is clear and simple. It’s easy to see what’s going on at a glance. The design looks great, too. I had no trouble finding what I needed and monitoring my sites is straightforward. If you want a simple tool that works well, Pulsetic is a good choice."
CEO at MBDC Media
"The monitoring tool we’ve been waiting for. Super easy to set up monitoring, customizable status page design, and access to notifications across Slack, email and SMS. Pulsetic is awesome."
CEO at Siena AI
"Tens of thousands of business owners from around the world rely on our service, and Pulsetic is the best platform there is to ensure we communicate any downtimes clearly and swiftly to our customers to avoid panic and disappointment. Getting setup on Pulsetic not only been smooth and easy but super joyful too, the design is stunning and customisable unlike any other monitoring platform we’ve used."
Founder, CEO at Plutio
"Pulsetic cut down our uptime monitoring work a lot. We automated uptime tracking and SLA reporting, which took a chunk of manual effort out of our monthly and annual reports. The Slack and email alerts let the team jump on problems quickly, and the API is what really sold us, since we point a dedicated health-check endpoint at it and pull uptime data straight into our internal workflows."
Treasurer, Fundacion Jorge Luis Borges
"There’s an easy way for you to monitor your online project. After all the hard work you have put into going live, you want to make sure that things keep running smoothly while you focus on the next project."
Founder at nineLemon
"Pulsetic is fast and genuinely easy to use. The UI is clean and has the features we actually needed, the status pages look good, and being able to route alerts to several channels was a real plus for us."
Founder at Qurioos
"Pulsetic helps us monitor all of our websites and webapps over at Pairing.dev. Before we used it, we had no idea how often services (e.g. heroku) were offline. Now we have complete control over it."
Founder at Pairing.dev
"Using Pulsetic is a big win for us! Our dev team can now deliver faster, with zero time spent monitoring our website uptime. Plus the interface is great and analytics proper."
Head of Marketing at AbstractAPI
Three fields and a few seconds. Nothing to install, and nothing to change on your website.
Open the response time chart on any monitor and start a new annotation.
Set the date and time, give it a short title, and add details if they help.
It shows on the chart at that exact moment, across every monitoring location.
Anything that might explain a change in the line, whether it came from you or from somebody else.
The obvious one, and the one that pays for itself fastest. Ship, mark it, and the next time a graph steps up you know in seconds whether your release belongs on the suspect list or can be ruled out.
A server resize, a new cache rule, a DNS change, a tweak to a CDN setting. These almost never cause an incident, which is exactly why they get forgotten. They do quietly set a new baseline.
A provider migration, a third-party API version bump, a hosting maintenance window. When the change was not yours, the annotation is what stops the team spending an hour debugging its own code.
A campaign launch, a launch-day feature, a sale. Response time under load only means something next to the reason the load turned up in the first place.
Mark every deploy and config change on the response time chart, so the next latency regression starts with a suspect list instead of a guess.
Watch your release land on the graph and know within seconds whether the slowdown started with your code.
Keep a dated record of what changed and when, so post-incident reviews start from facts rather than recollection.
Build the habit early: a chart carrying your own history is worth far more than one that only shows the last week.
Need access for more than one person? Pulsetic is for you. Easily manage access controls with specific rights and permissions for individual users, so you can collaborate without compromising on security.
With Pulsetic’s API, you’ve got complete control: you can add custom statistics, monitors & automations, create bespoke rules and maintain granular control over who can access or modify monitoring information. Best suited for developers in scale-up or large enterprises.
Notes you place on a monitor's response time chart at a specific moment in time. You give an annotation a date, a short title and optional details, and it appears on the graph as a marked point in time, next to the lines it explains.
Anything that could explain a change in the graph. Deploys and releases are the obvious ones, but infrastructure changes, cache and CDN settings, DNS updates, provider migrations, third-party API upgrades and traffic events like a campaign launch are all worth marking. If you would mention it in a post-incident review, it belongs on the chart.
They do different jobs. A maintenance window tells Pulsetic not to alert you during planned work. A status page update tells your users what is going on. An annotation is context for you and your team on the response time chart, and it is the only one of the three that is designed to still be useful months later, when someone asks why the graph changed shape.
Yes. The date and time are yours to set, so you can mark a change after the fact and it lands at the right point on the chart. That matters during an incident, when the deploy usually gets remembered long after it went out.
No. An annotation is a note on the chart. It does not pause a monitor, change a check interval or stop an alert from firing. If you want to suppress alerts during planned work, use a maintenance window instead.
No. Annotations live in your Pulsetic dashboard and need no code, no agent and no change to your website. You add one from the response time chart of any monitor you already have.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.