figshare.com logo

Is figshare.com Down?

SaaSLive status, outages, and incident history

No. figshare.com is up right now.

Every monitored figshare.com system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment figshare.com breaks

figshare.com is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official figshare.com status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

figshare.com Status Summary

As of 13:07 UTC on 9 November 2026, figshare.com is operational. PulsAPI checked figshare.com's official status page and found 14 of 14 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for figshare.com, counting degraded performance as up. The latest incident, "Botnet flood", was on Oct 24, 2026 and lasted 1h 28m.

Cite as: PulsAPI, “figshare.com status”, checked 9 November 2026, 13:07 UTC. https://www.pulsapi.com/services/figshare-com

figshare.com Component Status

The main figshare.com systems on this page. All 14 are operational right now.

14operational
Authentication » PALogin
Operational
Authentication » SSOLogin
Operational
Data Services » Search & browse
Operational

11 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Data Services » Stats API, Storage » Download, Storage » File ingest/migration, Storage » File viewers, Storage » Upload, Systems » API, Systems » Website, Systems » Widgets, Tasks » DOI minting, Tasks » Feed management, Tasks » File conversion and preview.

See all of them free

Component statuses may change independently during partial outages.

Recent figshare.com Outages & Incidents

Incident history from the official figshare.com status page, including resolution updates.

Botnet floodResolved Oct 24, 2026 · 1h 28mResolved

Resolved: 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 network of clients. At its peak, traffic to our site was roughly seven times the overnight level. Impact: Degraded performance across the website \(slowness and intermittent errors\). Response: We identified the traffic pattern and deployed a targeted filtering rule at our web application firewall at about 12:30 UTC. Traffic returned to normal levels within minutes, and we monitored for a further hour to confirm it stayed there. Status: Resolved. Traffic levels have been stable since about 13:00 UTC. Next steps: We are reviewing our traffic filtering to catch similar automated traffic earlier, and we will keep monitoring. --- [2026-10-24T16:54:35.885+03:00] (resolved) This incident has been resolved. --- [2026-10-24T15:29:32.546+03:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-24T15:28:30.287+03:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-10-24T15:25:58.368+03:00] (investigating) We are currently investigating this issue.

Publishing and deposit failures (Oct 18–19, 2026)Resolved Oct 22, 2026Resolved

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 upload). Some items and drafts also did not appear in the interface. A backlog of background replication messages had built up in our message broker and filled its disk. The broker then stopped processing new messages. Data was delayed rather than lost. We cleared the backlog and restored service at 04:40 UTC on 19 October. Search-backed views caught up by about 08:00 UTC on 19 October. We have since added monitoring, alerting and additional capacity to prevent a recurrence.

figshare.com Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a figshare.com incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 4 days with incidentsNov 9

Going further back: figshare.com uptime by month and every recorded figshare.com outage.

Live figshare.com Outage Reports

Problems reported by engineers using figshare.com. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No figshare.com problems reported yet.

Something wrong with figshare.com on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About figshare.com

figshare.com exposes 19 monitored components on its status page at status.figshare.com — Website, Search & browse and Upload among them. Follow figshare.com downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured figshare.com uptime at 100.00%. Response times, incident history, and SLA tracking for figshare.com are available on the PulsAPI dashboard.

figshare.com Status FAQ

Is figshare.com down right now?

The verdict at the top of this page comes from the latest poll of the official figshare.com status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if figshare.com is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until figshare.com recovers.

How do I check figshare.com uptime history?

PulsAPI tracks figshare.com uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever figshare.com changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect figshare.com outages?

PulsAPI reads the official figshare.com status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual figshare.com components?

Yes. PulsAPI monitors 14 individual figshare.com components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when figshare.com goes down?

Yes. Create a free account and subscribe to figshare.com: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with figshare.com to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot figshare.com problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor figshare.com?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so figshare.com plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track figshare.com with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services