figshare.com Outage History

18 incidents recorded over the last 365 days, 6 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.

Live figshare.com status100.00% uptime history

Every Recorded figshare.com Incident

figshare.com incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Production releaseScheduled maintenance is currently in progress. We will provide updates as necessary.5h 0mScheduled
Oct 24, 2026Botnet floodResolved: Elevated traffic from automated clients, 24 October 2026 Summary: From about 05:00 UTC on 24 October, [figshare.com](http://figshare.com) received a large volume of automated requests from a distributed…1h 28mResolved
Oct 22, 2026Publishing and deposit failures (Oct 18–19, 2026)Between 11:50 UTC on 18 October and 04:40 UTC on 19 October, some users were unable to publish items from the review queue or deposit files through Elements, and saw errors (such as “530” on publish or HTTP 500 on file…-5978 minResolved
Sep 24, 2026Production releaseThe scheduled maintenance has been completed.4h 0mScheduled
Aug 27, 2026Production releaseThe scheduled maintenance has been completed.4h 0mScheduled
Jul 30, 2026Production releaseThe scheduled maintenance has been completed.4h 0mScheduled
Jun 25, 2026Production releaseThe scheduled maintenance has been completed.4h 0mScheduled
May 27, 2026Production releaseThe scheduled maintenance has been completed.4h 0mScheduled
Apr 29, 2026Production releaseThe scheduled maintenance has been completed.8h 0mScheduled
Mar 26, 2026Production releaseThe scheduled maintenance has been completed.4h 0mScheduled
Feb 26, 2026Production releaseThe scheduled maintenance has been completed.4h 0mScheduled
Jan 29, 2026Production releaseThe scheduled maintenance has been completed.4h 0mScheduled
Dec 22, 2025Website intermittent errorsThis incident has been resolved.6936h 15mResolved
Dec 19, 2025Website intermittent downtimeThis incident has been resolved.1h 21mResolved
Dec 18, 2025Website intermittent errorsThis incident has been resolved.12h 10mResolved
Dec 18, 2025Production releaseThe scheduled maintenance has been completed.4h 0mScheduled
Dec 16, 2025Intermittent errors on api.figshare.comThis incident has been resolved.1h 54mResolved
Nov 27, 2025Production releaseThe scheduled maintenance has been completed.4h 0mScheduled

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 figshare.com 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 figshare.com 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 figshare.com 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 figshare.com outage in this window ran 289d, against a mean recovery of 17d 4h. If you depend on figshare.com 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.