LIVE STATUS
Is it down right now?
Live checks for popular AI tools, developer platforms, cloud services, and communication products.
START WITH THE SYMPTOM
Browse by problem
Start with the type of failure you are seeing, then move from the symptom to the underlying cause and verification step.
DNS & Domain Errors
Practical guidance for distinguishing local DNS problems from domain-wide failures, checking records and nameserver delegation, and knowing when DNS is not the cause of a website error.
Explore guides → ERROR CATEGORYHTTP & Server Errors
Practical guides to HTTP 5xx responses and connection-level failures, with a structured way to identify whether the cause is the browser, network, proxy, web server, application or backend dependency.
Explore guides → ERROR CATEGORYRedirect Errors
Troubleshooting guidance for redirect loops, excessive redirect chains, and conflicting HTTP, HTTPS, hostname, application, proxy, or server rules.
Explore guides → ERROR CATEGORYSSL & Security Errors
Troubleshooting guides for SSL certificate and TLS errors that stop browsers from establishing a trusted HTTPS connection with a website.
Explore guides → ERROR CATEGORYWordPress Errors
Troubleshooting guidance for WordPress failures, including plugin-related 500 errors, the White Screen of Death, database connection problems, and exhausted PHP memory.
Explore guides →EDITORIAL LIBRARY
Featured error guides
Practical explanations for the error codes and failures that most often stop a site or application from working.
403 Forbidden Error: What It Means and How to Fix It
An HTTP 403 Forbidden response means the server understood the request but refuses to authorize access to the requested resource. The request may be blocked by…
Read diagnosis →HTTP 5xx Server Errors: Meaning, Diagnosis and Fixes
An HTTP 5xx response means a server or intermediary could not complete an otherwise valid request. Identify the exact status code and the layer that generated …
Read diagnosis →HTTP 4xx Client Errors: Meaning, Diagnosis and Fixes
An HTTP 4xx response means the server or an intermediary could not fulfill a request as received. Identify the exact status code first, then check the URL, met…
Read diagnosis →WordPress Login Page Keeps Redirecting in a Loop
A WordPress login redirect loop is usually caused by mismatched `siteurl` and `home` values, stale login cookies, or a disagreement about HTTPS between WordPre…
Read diagnosis →Cloudflare Error 1020 / 1015: Access Denied & Rate Limited
Cloudflare Error 1020 means a Cloudflare firewall, WAF or security rule denied the request. Error 1015 means the request matched a configured rate limit. Visit…
Read diagnosis →NET::ERR_CERT_AUTHORITY_INVALID (Untrusted Certificate)
`NET::ERR_CERT_AUTHORITY_INVALID` means the browser cannot establish a trusted chain from the website’s certificate to a certificate authority trusted by your …
Read diagnosis →ERR_EMPTY_RESPONSE
`ERR_EMPTY_RESPONSE` means the connection was established but closed before the browser received usable HTTP response headers or body data. Test the failing UR…
Read diagnosis →WordPress REST API Returning 404
A WordPress REST API 404 usually means the request is not being routed to the REST API, rewrite rules are stale, or a security layer is deliberately hiding the…
Read diagnosis →Mixed Content Warning After Enabling HTTPS
A mixed content warning means an HTTPS page is requesting one or more resources over insecure HTTP, such as an image, script, stylesheet, font, or iframe. Use …
Read diagnosis →DIAGNOSTIC METHOD
How we diagnose website errors
- Identify the symptom. Start with the exact HTTP, DNS, SSL, redirect, or application error.
- Locate the failing layer. Separate browser, DNS, TLS, proxy/CDN, web server, application, and database failures.
- Test the smallest useful hypothesis. Use targeted checks instead of changing several production settings at once.
- Apply the fix and verify it. A configuration change is not finished until the original failure is gone and the expected response is back.
- Know when to stop. If the evidence points to infrastructure you cannot safely change, the guide tells you when outside help is appropriate.
EDITORIAL STANDARD
Why erriscope.com?
The site is built around diagnosis rather than generic content: direct answers first, concrete causes, platform-specific fixes, verification steps, and clearly separated live connectivity checks. Published editorial content is kept separate from live service telemetry, and the public pages link to official status or documentation sources when they are useful.
WHEN YOU NEED AN ANSWER NOW
Check the site first. Then fix the right layer.
Use the checker for reachability, then use the error library for the actual diagnosis and verification steps.