Error page error page - is it necessary?

Question

Google

Today I caught on googlemail such a charming phenomenon as the error page of the error page .
The screenshot is attached:

The point is that separate servers are responsible for returning the error page, and if an unexpected error has already occurred on them, such an “error page of the error page” is issued.
And now the question is - do you think it makes sense in not so large projects to generate error pages on separate servers, or are static pages enough?
Have you had projects where dynamic error pages were appropriate and necessary?

Answer 1

In my experience, the most dynamic error page contained the %page_url% insert.
And about the error on the back-end, I think that the 500th is enough.

Answer 2

I don’t know, of course, but personally, such a mistake would clearly cheer me up, and not spoil it (especially You Win!). And a satisfied customer... even if he didn't get what he wanted

Answer 3

If the framework/application uses templates/handlers/some code that can throw an exception to output errors, it is quite logical to put a top handler with code like
if (!output_started) { header("$protocol 500 Fatal Error"); }
die("Fatal Error");

Answer 4

Sorry, I could not resist:

Caught personally =)