rewindex

CompaniesStatuspageIncidents

Statuspage: Incident History page is not paginating correctly

No impact listedStatus: resolvedStarted Resolved (5.7 h)1 updatemetastatuspage.com (opens in new tab)

Timeline of updates

  1. resolved

    This incident has been resolved. After further investigation, we confirmed that this was only impacting component groups with showcased children components. Viewing that specific component on the uptime page would have silently failed to update the displayed uptime data.

From Statuspage’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on metastatuspage.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Statuspage, started 2018-02-13 17:39 UTC, resolved after 5.7 h, 1 update(s).

Title
Incident History page is not paginating correctly
Vendor
Statuspage
Date
URL
https://rewindex.com/company/statuspage/incidents/c33dv5d73fty

Statuspage profileRecent Statuspage incidentsAll outages on February 13, 2018Statuspage in February 2018MarkdownJSON