500 server error page template for SaaS

What does this 500 server error page template include?

A heading confirming the team is investigating the server error, a short paragraph explaining the request failed, a retry button and a status page link, and an inline incident block with a status dot, incident title, status label, elapsed time, affected scope description, and a newest first list of timestamped engineer update entries.

How is a 500 error page different from a 404 error page?

A 500 error page shows when the server received the request but encountered an error completing it. The visitor knows the product exists and something went wrong on the server side. A 404 error page shows when the page they requested was not found at that URL. The 500 page focuses on the incident and what the team is doing about it. The 404 page focuses on helping the visitor navigate to what they were looking for.

What goes in the incident block on a 500 error page?

The incident title describing what is failing, a status label such as Investigating or Monitoring, the time elapsed since first detection, a brief paragraph naming what is affected and what continues to serve normally, and a newest first list of timestamped engineer update entries. Populate these from your incident management system or update them manually.

Which other templates pair with this 500 error page?

The 500 error page and the maintenance page both communicate that the product or a component is currently unavailable. The status page template in the library is the dedicated page where teams publish incident updates, track component uptime, and post maintenance schedules. A product shipping any of these three pages benefits from having all three together.

Which templates make up the full status kit?

Five templates cover the status and launch surfaces of a SaaS product: the 404 error page for page not found URLs with helpful navigation links, the 500 error page for server errors with an inline incident status block and update log, the maintenance page for scheduled downtime with a progress bar and an email notification form, the coming soon page for announcing a launch date with feature preview cards and an email capture form, and the waitlist landing page for collecting early access signups with a queue position, a progress bar, and a referral link.