No impact incident

figshare.com: Publishing and deposit failures (Oct 18–19, 2026)

Oct 22, 2026, 15:08 UTC

started

11:30 UTC

resolved October 18, 2026

—

duration

Current status of figshare.com: Operational — live figshare.com status

Timeline

Oct 18, 2026, 11:30 UTC
resolved
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.

Updates as published by figshare.com (original).

Honeycomb 16:06 UTC · Email notifications for SLOs, Triggers, and Anomaly Detection not sending
Ohio University 16:04 UTC · Proctorio Not Functioning with Canvas Classic Quizzes
PubNub 16:02 UTC · Errors and Latency for Presence in FRA and BOM
Twilio 16:01 UTC · Intelligent Alerts Delivery Issues
Deepgram 16:00 UTC · Elevated 5xx Errors
Wikimedia 15:56 UTC · Maintenance
Telnyx 15:43 UTC · Partial Service Degradation Affecting US Traffic
Chargebee 15:43 UTC · Subject: Security Notice: No Impact from PHPshell Zero-Day Vulnerability
WiscNet 15:43 UTC · [2307287] Walworth J1 School District - 400650 - Down
Cloudflare 15:33 UTC · Cloudflare Workers API Latency
Zapier 15:29 UTC · Security updates in progress for third-party software components
GitHub 15:28 UTC · Project updates delayed
IPRoyal 15:26 UTC · Connectivity issues affecting some Brazil ISP proxies
LCN 15:23 UTC · PHP security vulnerabilities – customer update
3DSOutscale 15:20 UTC · [US-WEST-1] OOS Incident