Statuspage: AWS Third-Party Components being updated
Timeline of updates
- resolved
Today, we performed an update to our list of available AWS Third-Party Components in order to add new services and provide more regional granularity to some existing components. Some customers may have received a notification that a particular AWS component is "no longer available on the status page that was powering it." While the contents of that notification are correct in stating that the component will no longer receive updates, we wanted to provide more context on how to add a new, replacement component. Users receiving this notification may login and navigate to Components where the old component may be deleted. Then, in Components > Third-party > AWS, add any new, relevant components to their page in order to restore a component that will receive automatic updates. Our apologies for not providing advance notice of this maintenance event. For any questions, please contact support.
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 2020-07-17 19:23 UTC, resolved after 0 min, 1 update(s).
- Title
- AWS Third-Party Components being updated
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/m6qnh1jg8g42
Statuspage profileRecent Statuspage incidentsAll outages on July 17, 2020Statuspage in July 2020MarkdownJSON