Skip to main content
Solved

External Status Page – Can incident history be limited to the last 30 days?

  • June 8, 2026
  • 3 replies
  • 22 views

Forum|alt.badge.img

Hello,

We're using PagerDuty External Status Pages and have noticed that the public status page displays incident history going back several years (currently back to January 2022).

Our goal is to show only the most recent 30 days of incident history to customers.

I've reviewed the External Status Page settings and documentation but haven't found an option to:

  • Limit visible incident history to the last 30 days
  • Automatically hide incidents older than 30 days
  • Configure a retention period for publicly displayed incidents
  • Delete or archive older incidents from the status page

Could anyone confirm:

  1. Is there a supported way to restrict incident history visibility to the last 30 days?
  2. Is there an API endpoint or administrative action that can remove older incidents from an External Status Page?
  3. Are there any roadmap plans for configurable incident history retention on External Status Pages?

Any guidance or best practices would be appreciated.

Thank you.

Best answer by maria_yarotska

Hey Igovi,

There is currently no native setting to automatically restrict, archive, or filter the rolling incident history on your PagerDuty External Status Pages. While you can limit performance metrics to 30 days in the settings, the incident timeline naturally acts as a permanent historical ledger. The only way to remove them is for an admin to manually delete or un-publish those specific historic posts from the Status Page interface (see how).

As a good practice to keep your timeline clean moving forward, you might want to consider limiting status page posts exclusively to major events (P3/P1) rather than minor operational blips.

I’ve passed this use case along to our Product team as a feature request for configurable history retention. Let me know if you need help with any other settings!

3 replies

maria_yarotska
Forum|alt.badge.img
  • Community Manager 💚
  • Answer
  • June 8, 2026

Hey Igovi,

There is currently no native setting to automatically restrict, archive, or filter the rolling incident history on your PagerDuty External Status Pages. While you can limit performance metrics to 30 days in the settings, the incident timeline naturally acts as a permanent historical ledger. The only way to remove them is for an admin to manually delete or un-publish those specific historic posts from the Status Page interface (see how).

As a good practice to keep your timeline clean moving forward, you might want to consider limiting status page posts exclusively to major events (P3/P1) rather than minor operational blips.

I’ve passed this use case along to our Product team as a feature request for configurable history retention. Let me know if you need help with any other settings!


Forum|alt.badge.img
  • Author
  • New Member 👋
  • June 9, 2026

Hi Maria, Thank you very much for the quick reply and the tips. Insted of manually deleting the posts, I tried it via API. However when I listed the status page posts, the response JSON doesnt seem to contain the information about time and date. It would be great if you can pass that as a case for the statuspages api endpoints.

I have another question too, Is it possible to add an About section to the external status pages as with atlassian status pages?


maria_yarotska
Forum|alt.badge.img
  • Community Manager 💚
  • June 9, 2026

You are very welcome! I will pass along your feedback regarding the missing date/time stamps to our developer tools team.
To answer your second question: no, it is currently not possible to add an "About" section or text block to PagerDuty External Status Pages.
The closest alternatives to add more context include uploading a custom image to the header or footer, setting up a custom navigation bar, or inserting relevant links. You can find the steps to customize these sections in the PagerDuty External Status Page Documentation.