2xx Success
HTTP 226 IM Used
The server fulfilled a GET request and the response is the result of one or more instance manipulations, such as a delta against a version the client already has, applied to the current resource. Part of HTTP delta encoding, which was never widely deployed.
Defined in RFC 3229, section 10.4.1(opens in a new tab)
//_01 Uptime checks
Is 226 up or down for a monitor?
Uptimecheck HTTP monitor
Default settings
Up. By default an Uptimecheck HTTP monitor accepts 200–399 as up, so a 226 counts as up. With a keyword check, the page must also contain the word you set.
Is it down? checker
Free, at /is-it-down/
Up: the checker counts any answer below 500 as the site answering.
//_02 Causes and fixes
Why you see 226 and what to do
Typical causes
- A client and server that both support delta encoding (A-IM and IM headers).
If you run the site
- Nothing to fix.
If you’re a visitor
- You won’t see it in a browser.
Know the moment your site stops answering as it should
An Uptimecheck monitor requests your page as often as every minute, checks the status code against the ones you expect, confirms a failure with a second check and then alerts you.
14-day free trial · No credit card required
Questions
What does HTTP 226 mean?
The server fulfilled a GET request and the response is the result of one or more instance manipulations, such as a delta against a version the client already has, applied to the current resource. Part of HTTP delta encoding, which was never widely deployed.
Does an uptime monitor count 226 as down?
Up. By default an Uptimecheck HTTP monitor accepts 200–399 as up, so a 226 counts as up. With a keyword check, the page must also contain the word you set.
Downtime is obsolete.
Set up your first monitor in under a minute, or look around the live demo first.
14-day free trial · No credit card required