Altmetric Outage History
20 incidents recorded over the last 365 days, 7 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 Altmetric Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Dec 29, 2026 | Periodic maintenanceAltmetric core infrastructure will be undergoing periodic updates and maintenance during this time window. No extended downtime is expected as part of this maintenance but occasional brief interruptions to Altmetric… | 8h 0m | Scheduled |
| Nov 24, 2026 | Periodic maintenanceAltmetric core infrastructure will be undergoing periodic updates and maintenance during this time window. No extended downtime is expected as part of this maintenance but occasional brief interruptions to Altmetric… | 8h 0m | Scheduled |
| Oct 27, 2026 | Periodic maintenanceScheduled maintenance is currently in progress. We will provide updates as necessary. | 8h 0m | Scheduled |
| Sep 29, 2026 | Periodic maintenanceScheduled maintenance is currently in progress. We will provide updates as necessary. | 8h 0m | Scheduled |
| Sep 18, 2026 | Altmetric Details API functionality degradationNo further outages have been detected so the incident is now considered resolved. | 14h 5m | Resolved |
| Sep 18, 2026 | Configuration change maintenanceConfiguration changes have now been deployed without any detectable issues. We will continue to monitor for any problems throughout the remainder of the maintenance window. | 8h 0m | Scheduled |
| Aug 25, 2026 | Periodic maintenanceScheduled maintenance is currently in progress. We will provide updates as necessary. | 8h 0m | Scheduled |
| Aug 11, 2026 | Delay across all attention sourcesThe processing backlog has cleared and attention sources are updating normally again. | 13h 11m | Resolved |
| Aug 6, 2026 | Delay in news mention collectionNews mention collection is running normally again. Some remaining content from the outage period is still being reprocessed by our upstream provider, so a small number of mentions from that window may continue to appear… | 162h 27m | Resolved |
| Jul 29, 2026 | Data processing delayIssues have been resolved and data stream is now fully caught up. | 18h 37m | Resolved |
| Jul 28, 2026 | Periodic maintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Jun 30, 2026 | Periodic maintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Jun 17, 2026 | Periodic maintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| May 26, 2026 | Data processing delaysThis incident has been resolved. | 133h 12m | Resolved |
| May 26, 2026 | Periodic maintenanceThe scheduled maintenance has been completed. | 10h 0m | Scheduled |
| Apr 28, 2026 | Periodic maintenanceThe scheduled maintenance has been completed. | 10h 0m | Scheduled |
| Mar 31, 2026 | Periodic maintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Feb 1, 2026 | Altmetric Explorer & Altmetric Details Pages unavailableThis incident has been resolved. | 4h 22m | Resolved |
| Nov 25, 2025 | Periodic maintenanceThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Nov 18, 2025 | Cloudflare CDN global incidentCloudflare has now confirmed that their services have returned to normal operation. Altmetric applications are also operating normally so we are closing this incident. | 5h 58m | 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 Altmetric 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 Altmetric 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 Altmetric 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 Altmetric outage in this window ran 6d 18h, against a mean recovery of 22h 60m. If you depend on Altmetric 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.