Free tool · Availability
WordPress Uptime Checker
The WordPress uptime checker tests whether your public website responds from BugShield's server right now. Use it to investigate an outage or compare a connection problem with what an external check sees.
Free WordPress uptime check
Free to use without an account. View the result here and choose whether to receive it by email.
What the tool covers
Check whether a site responds now
A single public request, its HTTP status and the time taken to receive the response.
An external connection
BugShield makes a request from its server, giving you another view of a problem that could otherwise be limited to your browser, network or location.
HTTP response status
When the site responds, the report shows its HTTP status. Successful responses, server errors and access restrictions need different follow-up checks.
Request duration
The result records how long the request and response took from this scanner. It is a single measurement, not a page speed score or a record of visitor experience.
Understand the limits
This is a point-in-time check from one location. It does not measure historical uptime, a service-level agreement or availability for every visitor.
Understanding your result
Work out what the availability result establishes
Start with the response status and compare it with the exact problem reported by visitors. A site can answer an HTTP request while an important feature remains broken.
Confirm the page behind a successful response
Open the affected address and confirm that the expected content appears. Test the form, login or checkout involved in the original report, because this tool does not complete those journeys.
Put blocked requests in context
An access restriction or request limit can apply to this scanner without affecting all visitors. Ask your host to compare the result with security rules and access logs before changing a firewall.
An error helps focus the outage investigation
Save the result, note the time and check your host's service status. If failures recur, use ongoing monitoring to establish when they happen and how long they last.
Separate a local problem from a public response
A site that fails on your connection can still respond elsewhere. Enter the address that is failing and compare this result with a private browser window and a different network. Keep the time and exact error message when asking your host to investigate.
Read the response before choosing a fix
A successful response means our request received a page, but that page can still contain an application error. A blocked request can reflect a security rule. Server errors and connection failures need investigation alongside your host's status page and server logs.
Use monitoring for an uptime record
A single request cannot tell you how long an outage lasted or calculate a monthly uptime percentage. Continuous monitoring records repeated checks over time. If you need alerts or evidence of recurring downtime, use an ongoing monitoring service.
Questions about this tool
Is this a live WordPress uptime check?
Yes. It makes a request when your job runs and reports the response from BugShield's server at that time.
Can this calculate my monthly uptime percentage?
No. That needs a history of checks and an agreed measurement method. This tool performs one availability check.
Why does the checker fail when my site opens for me?
A firewall, regional restriction, bot rule or temporary connection problem can treat our request differently. Compare the reported error with your host's logs.
Does an HTTP 200 response mean checkout works?
No. It means the server returned a successful HTTP response. A working page can still have broken forms, payments or account features.
Can I email the availability result?
Yes. Use the optional email form after starting the check. For repeated checks and outage alerts, arrange continuous monitoring separately.
Free website widget
Add this tool to your website
Let visitors use the WordPress Uptime Checker on your own page, including the option to email their results. Copy the code into an Elementor HTML widget or a WordPress Custom HTML block, then preview the published page.
Get the embed code
The widget fits the width of its container. Increase the height value if you want more of the report visible at once; longer results can be scrolled inside the widget.
BugShield hosts and runs the tool. Results and email addresses stay inside the widget and are not shared with the page embedding it. If your editor removes the code or your site blocks external widgets, ask your website administrator to allow frames from bugshield.co.uk.
Need help with the next step?
A BugShield developer can review the findings and help you decide what your WordPress site needs.
Explore WordPress support