HTTP 427 Unassigned

HTTP 427 is currently unassigned in the IANA registry and should not be emitted by modern applications.

What this status code means

This status code value is currently unassigned in the IANA registry and should not be used in production APIs.

Who should act first

Client request or identity context is usually the first place to fix.

What to check first

  • Capture exact request path, method, and headers.
  • Verify authentication and authorization context.
  • Validate payload schema and content type.

How it differs from similar codes

Reference and next step

Specification: RFC 9110.

Read the full troubleshooting guide for HTTP 427 · Open the 4xx hub · Compare adjacent codes