Santiment Outage History
17 incidents recorded over the last 365 days, 17 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Santiment Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Improved on-chain metrics for Polygon native token (МАTIC / POL) | 59h 0m | Resolved |
| Oct 30, 2026 | Improved on-chain metrics for Avalanche tokens | 58h 0m | Resolved |
| Oct 28, 2026 | Improved on-chain metrics for Optimism tokens | 57h 0m | Resolved |
| Oct 20, 2026 | Ethereum Top Holders Update | 10h 0m | Resolved |
| Oct 6, 2026 | Social metrics recalculation | 14h 0m | Resolved |
| Sep 9, 2026 | Social metrics incomplete for Sep 9–10 – on-going recomputation | 13h 30m | Resolved |
| Aug 31, 2026 | Investigating — Delayed and missing metrics | 5h 30m | Resolved |
| Aug 27, 2026 | Scheduled infrastructure maintenance | 9h 0m | Resolved |
| Aug 26, 2026 | Scheduled infrastructure maintenance | 13h 0m | Resolved |
| Aug 19, 2026 | Scheduled maintenance - social metrics and youtube | 8h 0m | Resolved |
| Aug 14, 2026 | Scheduled maintenance — social metrics | 6h 0m | Resolved |
| Aug 13, 2026 | Scheduled Maintenance — Analytics & Reporting | 2h 0m | Resolved |
| Jul 31, 2026 | Scheduled Maintenance: Data Metrics Recalculation | 6h 0m | Resolved |
| Jul 30, 2026 | Cluster Upgrade | 2h 0m | Resolved |
| Jun 19, 2026 | Scheduled recompute social dominance metrics | 9h 0m | Resolved |
| Jun 17, 2026 | Planned upgrades to our infrastructure | 11h 0m | Resolved |
| Jun 8, 2026 | Scheduled maintenance: Stablecoin trade volume metrics temporarily unavailable | 5h 0m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Santiment incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Santiment Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Santiment acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Santiment outage in this window ran 2d 11h, against a mean recovery of 16h 57m. If you depend on Santiment in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.