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 & uptime monitoring - the core of PulseStack
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 £15/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 measures response time on every check so you catch 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 after
consecutive-failure threshold
GET https://acme.example/api [frankfurt]
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 Enterprise.
Wire up Email, Slack, Teams, PagerDuty, Telegram and more.
Share live uptime and incident history with your customers.
Five 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.
Detect record changes and resolution failures.
Never lose a domain to a missed renewal date.
HTTP and API monitors support custom request headers. All 8 types 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. SMS and voice come as an add-on and 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, from every region, 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 engine rankings. Studies show that 88% of online consumers are less likely to return to a site after a bad experience, and Google factors site reliability into search rankings.
PulseStack™ checks your website as frequently as every 30 seconds from 7 global monitoring locations. 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 to every 5 minutes for less critical pages.
Endpoint Guardian supports HTTP/HTTPS monitoring, SSL certificate tracking, TCP port monitoring, keyword and content verification, domain expiry alerts, ICMP ping tests, API endpoint monitoring, DNS resolution checks, and response time tracking. All monitor types can be combined for comprehensive coverage of your entire web infrastructure.
You can receive alerts through 16+ channels including email, SMS text messages, Slack, Discord, Microsoft Teams, PagerDuty, Telegram, phone calls, webhooks, OpsGenie, and more. Configure escalation rules so the right team members are notified at the right time, and set consecutive failure thresholds to avoid false alarms.
Yes, PulseStack™ offers a generous free plan that includes up to 50 monitors with no credit card required. Free monitors check every 3 minutes from multiple locations and include email alerts. Paid plans unlock 30-second check intervals, SMS alerts, advanced integrations, and more monitoring locations.
Yes, PulseStack™ monitors your website from 7 locations across North America, Europe, and Asia. Multi-location monitoring helps you detect regional outages, CDN issues, and geo-specific problems that single-location monitoring would miss. Each check runs simultaneously from all configured locations.
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 when it slows down beyond your configured thresholds.
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 validate response content, making it perfect 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.