fezpetersfield.com Status
- HTTP status
- 200
- Response time
- 391 ms
- Last checked
- Page title
- Turkish Restaurant & Meze Bar - Fez Petersfield
Free website status checker — check if any site is up or down in seconds. See HTTP status codes, response times, redirects, and page titles. No signup required.
The 10 websites our visitors check most often. Click any domain to see its latest status.
fezpetersfield.com was checked by WebsiteStatus on October 18, 2026 at 2:42 PM. The server responded with HTTP status code 200 and a response time of 391 ms. The current status is: Up & running. You can re-check this site at any time by clicking the "Re-check now" button above, or check another website from the home page.
Status codes in the 200-299 range indicate success. 200 OK is the most common and means the page loaded normally. 201 means a resource was created (common in API responses). 204 means the server processed the request but returned no content. WebsiteStatus reports any 2xx or 3xx code as "Up & running."
A response time under 200 milliseconds is excellent. Between 200 and 500 milliseconds is average for most websites. Anything over 1 second may feel slow to visitors. Response times above 3 seconds can hurt search rankings and user experience. WebsiteStatus measures the exact round-trip time in milliseconds.
A 502 Bad Gateway means a proxy or gateway server received an invalid response from the upstream server. A 503 Service Unavailable means the server is temporarily unable to handle the request, often due to maintenance or overload. Both are usually temporary. WebsiteStatus will report the exact code so you know what is happening.
DNS (Domain Name System) translates a human-readable domain name like example.com into a machine-readable IP address. If DNS resolution fails, your website will be unreachable even if the server itself is running perfectly. WebsiteStatus verifies DNS records as part of the check process to help you rule out DNS issues.
Yes, you can check any subdomain. Just type the full address including the subdomain (for example, blog.example.com). WebsiteStatus will resolve the DNS and check whether that specific subdomain is up and responding. Each subdomain gets its own results page.
The page title helps confirm that the server returned the correct content, not just any response. If a site returns a 200 status but the title says "Error" or "Database connection failed," you know the site is technically responding but broken. WebsiteStatus extracts the page title to give you a fuller picture of the site's health.