Teleport: Delayed usage reporting
Affected components: Cloud Service
Timeline of updates
- identified
We identified a backlog in processing usage events. Usage dashboards may currently show lower totals than actual usage. We’re working to clear the backlog and will update affected historical totals afterward. We’ll share another update as we make progress.
- resolved
The backlog has been cleared and usage updated.
Changes Rewindex caught on this incident
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-09 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
78d993aaa29fc7f8…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.teleport.sh (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Teleport, started 2026-11-09 23:25 UTC, resolved after 17 h, 2 update(s); edited after publishing.
- Title
- Delayed usage reporting
- Vendor
- Teleport
- Date
- URL
- https://rewindex.com/company/teleport/incidents/wtx6whffnf2v
Teleport profileRecent Teleport incidentsAll outages on November 9, 2026Teleport in November 2026MarkdownJSON