Hive Moderation Outage History
8 incidents recorded over the last 365 days, 8 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 Hive Moderation Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Mar 27, 2026 | Elevated Api ErrorsThis incident has been resolved. | 6h 41m | Resolved |
| Mar 12, 2026 | Async Task Submission Response Increased LatencySome customers may have experienced slower response times which, depending on their client timeout configuration, may have resulted in failed requests. Systems have returned to normal. | -3056 min | Resolved |
| Jan 21, 2026 | Brief outtageBrief connection error. Task submission failures possible. | -7536 min | Resolved |
| Jan 20, 2026 | NCMEC Reporting API is unreachableThis incident has been resolved. | 35 min | Resolved |
| Jan 15, 2026 | Brief Data outageBrief Database Connection Lost | -44 min | Resolved |
| Dec 9, 2025 | Async Submission Processing Delays - Callback And Actions DelayOur data processing infrastructure is running behind which caused delay in callbacks sent and actions ran. No data has been lost and the system has caught up. | -186 min | Resolved |
| Dec 8, 2025 | Partial Task Submission OuttagePartial outtage to Async Task requests. | -1399 min | Resolved |
| Nov 7, 2025 | Issues Loading DashboardThis incident has been resolved. | 49 min | 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 Hive Moderation 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 Hive Moderation 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 Hive Moderation 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 Hive Moderation outage in this window ran 6h 41m, against a mean recovery of 2h 42m. If you depend on Hive Moderation 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.