Add More Details in status page #2000

New issue

Closed

opened 2026-02-28 02:39:44 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 02:39:44 -05:00

Owner

Originally created by @jaainil on GitHub (Mar 13, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

Please add more details in status page like which error code happened on during the down time and details like a incident happened on this particular date.

✔️ Solution

In solution we can add drop down menu to see details on which time the site was down and what happened what was the response time and all in status page.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @jaainil on GitHub (Mar 13, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description Please add more details in status page like which error code happened on during the down time and details like a incident happened on this particular date. ### ✔️ Solution In solution we can add drop down menu to see details on which time the site was down and what happened what was the response time and all in status page. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:39:44 -05:00

closed this issue
added the
feature-request

A:status-page

A:incidents
labels

deekerman commented

2026-02-28 02:39:51 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 4, 2023):

@oyy-jainil
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #862. I have updated said issue to include the small adendum from this issue
⇒ I am going to close this as a duplicate.

@CommanderStorm commented on GitHub (Dec 4, 2023): @oyy-jainil We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #862. I have updated said issue to include the small adendum from this issue ⇒ I am going to close this as a duplicate.