Statuspage: Errors when trying to use CSS pre-processors
Timeline of updates
- resolved
The third party we use to do the CSS pre-processing temporarily killed the service and we did not have a backup in place to account for it (nor did the code account for that possibility). The third party turned the service back on and the feature is back to functioning properly.
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: minor) posted by Statuspage, started 2016-02-10 17:19 UTC, resolved after 54 min, 1 update(s).
- Title
- Errors when trying to use CSS pre-processors
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/npkldmhbgmjh
Statuspage profileRecent Statuspage incidentsAll outages on February 10, 2016Statuspage in February 2016MarkdownJSON