1403
Blocked by a firewall or WAF
Your origin is healthy but a rule, an IP block or a bot filter is turning real visitors away. PulseStack classifies the 403 as blocked so you look at access rules, not application logs.
Website and uptime monitoring
PulseStack runs HTTP and HTTPS checks from multiple locations, classifies every status code and measures response time on every hit - so a 403, a 429 or a 5xx never slips past you. Checks as often as every 30 seconds.
Free plan - 5 monitors, no card required. Paid plans from GBP 9/mo with a 14-day trial.
Live HTTP request from our network - the same check PulseStack runs as often as every 30 seconds.
Live check - run any URL through PulseStack right now.
"Up or down" is not enough. A page can return a 200 and still be broken, or return a 403 that only your customers see. PulseStack tells you which of these is happening.
Your origin is healthy but a rule, an IP block or a bot filter is turning real visitors away. PulseStack classifies the 403 as blocked so you look at access rules, not application logs.
A traffic spike or a runaway integration trips your rate limiter and legitimate requests start bouncing. Flagged as rate-limited, so you know to raise limits or shed load rather than restart servers.
A bad deploy, an exhausted connection pool or an out-of-memory worker starts returning 500s and 502s. Classified as a server error the moment it appears, with the exact code captured in the incident.
The page still loads, but response time is climbing towards a timeout. PulseStack records and charts response time from every location so you can spot the slide before it becomes an outage.
A PulseStack check does more than confirm a connection. It records the HTTP status code, classifies it, measures the round-trip time and writes it to your uptime history. That record is what turns a raw failure into an incident you can act on.
GET https://acme.example/ [london]
status 200 OK -> healthy
time 182 ms -> ok
GET https://acme.example/ [new-york]
status 429 Too Many.. -> RATE_LIMITED
time 91 ms
action incident opened, 2 of 3
locations failing
GET https://acme.example/api [sydney]
status 503 Service.. -> SERVER_ERROR
time timeout
alert Slack + PagerDuty firedNo agent to install, no config file. Add a URL and PulseStack starts watching.
Paste any HTTP or HTTPS endpoint. That is the whole setup.
From 5 minutes on Free down to 30 seconds on Pro, Team and Enterprise.
Wire up Email, Slack, Teams, PagerDuty, Telegram and more.
Share live uptime and incident history with your customers.
5 monitors free, no card, no trial clock. Upgrade only when you outgrow it.
HTTP is the heart of PulseStack, but the same dashboard watches everything else your service depends on.
Full page and endpoint checks with status-code classification.
Confirm expected text is present, not just a 200 response.
Reachability at the transport layer for any host.
Watch a specific port for an open, listening service.
Hit REST and GraphQL endpoints with custom request headers.
Catch cron jobs and workers that stop checking in.
HTTP and API monitors support custom request headers. All 9 types, including SSL certificate, DNS record and domain expiry monitors, are available from the Starter plan up.
A regional CDN fault or a geo-specific firewall rule can take you down for half your customers while everything looks fine from your desk. PulseStack runs checks from multiple locations, so those faults surface - and a single lonely blip does not page you.
Eight native channels, no glue code. Email is included on every plan, and SMS alerts are included on Team and Enterprise.
No fake competitor prices, no invented benchmarks. Just where each approach lands.
Tighten the interval as you grow. Annual billing saves 20% on every paid plan.
Watch every client site from one dashboard, publish a branded status page for each and prove uptime without a spreadsheet.
Classify 403s, 429s and 5xx the moment they appear, route alerts to Slack or PagerDuty and keep a clean incident history.
Get an email the second checkout starts failing, with checks from London, New York and Sydney, so a bad deploy or CDN rule never costs you a quiet weekend.
Website monitoring is the practice of continuously checking your website's availability, performance, and correct functioning from multiple locations around the world. You need it because even a few minutes of downtime can cost you customers, revenue and search visibility, and without monitoring you usually hear about an outage from a customer rather than an alert.
URL monitoring checks one specific web address on a schedule, such as your home page, a login page or a checkout step, and alerts you when it stops returning a healthy response. PulseStack™ requests the URL exactly as you enter it, path included, from London, New York and Sydney, and records the status code and response time on every check. Keyword monitors, from the Starter plan, can also confirm that a word or phrase still appears on the page.
PulseStack™ checks your website as frequently as every 30 seconds from 3 monitoring locations: London, New York and Sydney. This means issues are detected within seconds of occurring, not minutes or hours. You can configure check intervals per monitor, from 30 seconds for critical endpoints (Pro and above) to every 5 minutes for less critical pages.
Endpoint Guardian supports all nine PulseStack™ monitor types: HTTP/HTTPS, keyword, TCP ping, port, API, heartbeat, SSL certificate, DNS record and domain expiry, with response times recorded and charted per location. All monitor types can be combined for comprehensive coverage of your entire web infrastructure.
You can receive alerts through 8 native channels: email, SMS text messages, Slack, Discord, Microsoft Teams, PagerDuty, Telegram and webhooks, with Zapier and Google Chat connecting through webhooks. Failed checks are re-tested a few seconds later and a monitor is only marked down when at least two of the three locations fail, so you avoid false alarms.
Yes, PulseStack™ offers a free plan that includes up to 5 HTTP monitors with no credit card required. Free monitors check every 5 minutes from multiple locations and include email alerts. Paid plans unlock faster checks (every 60 seconds on Starter and every 30 seconds from Pro upward), all monitor types and advanced integrations, with SMS alerts included on Team and Enterprise.
Yes, PulseStack™ monitors your website from 3 locations across Europe, North America and Australia: London, New York and Sydney. Multi-location monitoring helps separate genuine outages from regional network problems, and catches CDN or geo-specific problems that hit more than one region. Each check runs from all three locations, and a monitor is only marked down when at least two of them fail.
Uptime monitoring checks whether your website is accessible and returning the correct HTTP status code (like 200 OK). Performance monitoring goes deeper, tracking response times, page load speeds, and time to first byte. PulseStack™ provides both: we alert you when your site goes down, and record response times on every check so you can see it slowing down in the per-location charts.
Search engines like Google factor website reliability and speed into their ranking algorithms. Frequent downtime signals to crawlers that your site is unreliable, which can cause your pages to drop in search results. SSL certificate issues, slow response times, and 5xx errors all negatively impact SEO. PulseStack™ helps you catch and fix these issues before they affect your rankings.
Absolutely. PulseStack™ can monitor any HTTP/HTTPS endpoint including REST APIs, GraphQL endpoints, webhooks, and microservices. You can configure custom HTTP methods (GET, POST, PUT, DELETE), set custom headers and authentication, send request bodies, and check for the expected status code, making it a good fit for API health monitoring.
When PulseStack™ detects your website is down, it immediately verifies the issue from multiple locations to rule out false positives. If the outage is confirmed, it sends alerts through your configured channels within seconds. An incident is automatically created with a timeline, and when the site recovers, you receive a recovery notification with the total downtime duration.
Multi-location HTTP checks, real status-code classification and instant alerts - starting free, no card required.