You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/analytics/account-and-zone-analytics/status-codes.mdx
+23-37Lines changed: 23 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,8 @@ The `Origin Status Code` can help you investigate issues on your origin. If your
18
18
19
19
Errors that originate from our edge servers (blank `502`, `503`, or `504` error page with just `Cloudflare`) are not reported as part of the error analytics.
20
20
21
+
You can filter out specific error(s) by selecting one or more in the legend. You can also exclude a particular error and it will no longer display as part of the graph.
22
+
21
23
:::note
22
24
23
25
Users may also see `100x` errors which are not reported. These will be displayed as either `403` or `409` (edge) errors.
@@ -27,56 +29,40 @@ Users may also see `100x` errors which are not reported. These will be displayed
27
29
28
30
***
29
31
30
-
## Edge Network errors
31
-
32
-
*`400` - Bad Request intercepted at the Cloudflare Edge (for example, missing or bad HTTP header)
33
-
*`403` - Security functionality (for example, Web Application Firewall, Browser Integrity Check, [Cloudflare challenges](/waf/reference/cloudflare-challenges/), and most 1xxx error codes)
34
-
*`409` - DNS errors typically in the form of 1000 or 1001 error code
35
-
*`413` - File size upload exceeded the maximum size allowed (configured in the dashboard under **Network** > **Maximum Upload Size**.)
36
-
*`444` - Used by Nginx to indicate that the server has returned no information to the client, and closed the connection. This error code is internal to Nginx and is **not** returned to the client.
37
-
*`499` - Used by Nginx to indicate when a connection has been closed by the client while the server is still processing its request, making the server unable to send a status code back.
38
-
39
-
***
32
+
## Common edge status codes
40
33
41
-
## Origin errors
34
+
-`400` - Bad Request intercepted at the Cloudflare Edge (for example, missing or bad HTTP header)
35
+
-`403` - Security functionality (for example, Web Application Firewall, Browser Integrity Check, [Cloudflare challenges](/waf/reference/cloudflare-challenges/), and most 1xxx error codes)
36
+
-`409` - DNS errors typically in the form of 1000 or 1001 error code
37
+
-`413` - File size upload exceeded the maximum size allowed (configured in the dashboard under **Network** > **Maximum Upload Size**.)
38
+
-`444` - Used by Nginx to indicate that the server has returned no information to the client, and closed the connection. This error code is internal to Nginx and is **not** returned to the client.
39
+
-`499` - Used by Nginx to indicate when a connection has been closed by the client while the server is still processing its request, making the server unable to send a status code back.
42
40
43
-
*`400` - Origin rejected the request due to bad, or unsupported syntax sent by the application.
44
-
*`404` - Only if the origin triggered a 404 response for a request.
45
-
*`4xx`
46
-
*`50x`
41
+
For more information, refer to [4xx Client Error](/support/troubleshooting/http-status-codes/4xx-client-error/).
47
42
48
43
***
49
44
50
-
## 503 errors
45
+
## Common origin status codes
51
46
52
-
We do count `503` errors from your origin that are passed as a response from the edge, though in this version 503 errors from the edge have multiple potential sources.
47
+
-`400` - Origin rejected the request due to bad, or unsupported syntax sent by the application.
48
+
-`404` - Only if the origin triggered a 404 response for a request.
49
+
-`4xx`
50
+
-`50x`
53
51
54
-
* Your origin server had a `503`. We received this from the origin and the status code was in the response from the on the edge
55
-
* WebSocket rate-limit error
52
+
For more information, refer to [4xx Client Error](/support/troubleshooting/http-status-codes/4xx-client-error/) and [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/).
56
53
57
54
***
58
55
59
56
## 52x errors
60
57
61
-
*`520` - This is essentially a "catch-all" response for when the origin server returns something unexpected, or something that is not tolerated/cannot be interpreted by our edge (that is, protocol violation or empty response).
62
-
*`522` - Our edge could not establish a TCP connection to the origin server.
63
-
*`523` - Origin server is unreachable (for example, the origin IP changed but DNS was not updated, or due to network issues between our edge and the origin).
64
-
*`524` - Our edge established a TCP connection, but the origin did not reply with a HTTP response before the connection timed out.
65
-
66
-
***
67
-
68
-
## Status codes
69
-
70
-
The status codes section shows:
58
+
-`520` - This is essentially a "catch-all" response for when the origin server returns something unexpected, or something that is not tolerated/cannot be interpreted by our edge (that is, protocol violation or empty response).
59
+
-`522` - Our edge could not establish a TCP connection to the origin server.
60
+
-`523` - Origin server is unreachable (for example, the origin IP changed but DNS was not updated, or due to network issues between our edge and the origin).
61
+
-`524` - Our edge established a TCP connection, but the origin did not reply with a HTTP response before the connection timed out.
62
+
-`525` - This error indicates that the SSL handshake between Cloudflare and the origin web server failed, either due to a network issue or a certificare issue at the origin.
63
+
-`526` - The certificate configured at the origin is not valid.
71
64
72
-
* The error code returned in the response
73
-
* The time-stamp for the "bucket" you selected
74
-
* The total count of that specific error code for that time-stamp
75
-
* The % of total requests that serves that error
65
+
For more information, refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/).
76
66
77
-
You can filter out specific error(s) by selecting one or more in the legend. Once you select an error it will be greyed out in the drop-down menu, and the error will no longer display as part of the graph.
0 commit comments