Productboard Outage History

25 incidents recorded over the last 365 days, 24 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 Productboard Incident

Productboard incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 26, 2026Changes made on boards taking too long to applyThe problem has been resolved, the system is back to normal operation.1h 31mResolved
Sep 14, 2026Productboard Spark is unavailableThis incident has been resolved.3 minResolved
Aug 5, 2026Unexpected AI credit usage on some Spark workspacesThe issue causing repeated LLM calls and unintended AI credit consumption has been fixed and deployed. Affected customer credits were refunded, and the service is operating normally.2h 46mResolved
Jun 22, 2026Elevated error rate across ProductboardThis incident has been resolved. We apologize for the disruption and thank you for your patience.1h 19mResolved
Jun 7, 2026Newly Created Boards InaccessibleThis incident has been resolved. Newly created boards are now fully accessible and operating as expected. We apologize for any disruption this may have caused.3h 15mResolved
May 16, 2026Scheduled Database MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Apr 22, 2026Filtering on boards is not availableThis incident has been resolved. Filtering on Boards is now fully available and functioning as expected. Thank you for your patience while we worked to resolve this issue.56 minResolved
Apr 14, 2026Productboard doesn't load or shows errorsProductboard is fully operational now.55 minResolved
Mar 3, 2026Board Performance IssuesThe incident has been fully resolved. Please contact support@productboard.com if you continue to have any issues.2h 7mResolved
Mar 3, 2026Documents don't loadThis incident has been resolved.1h 19mResolved
Mar 2, 2026Productboard components may not loadThe incident has been fully resolved1h 16mResolved
Mar 2, 2026Payment processing disruptionThis incident has been resolved.2h 42mResolved
Feb 23, 2026System performance delaysThis incident has been resolved.1h 3mResolved
Feb 13, 2026Productboard is unavailableThis incident has been resolved.1h 25mResolved
Feb 12, 2026Degraded Insights Analysis in SparkThis incident has been resolved.3h 6mResolved
Feb 5, 2026Delays When Saving Changes for Selected ActionsThe backlog has now been fully processed and new actions will process normally. We appreciate your patience and apologize for any inconvenience this caused.25 minResolved
Feb 2, 2026Jira Integration OutagePerformance of the Jira integration continues to improve as the backlog shrinks and the service is currently stable. If you continue to encounter issues, please reach out to support@productboard.com. Thank you for your…2h 27mResolved
Jan 29, 2026Productboard is downThis incident has now been resolved.2 minResolved
Jan 26, 2026Email delivery issues to Outlook addressesThis incident has been resolved.43h 26mResolved
Jan 21, 2026Delay for some customers when taking actions.This incident has now been mitigated.26 minResolved
Dec 5, 2025Productboard Service DegradationThis incident has been resolved.22 minResolved
Dec 4, 2025Elevated Latency on Query EngineThis incident has been resolved.9 minResolved
Nov 19, 2025Delays in Old Boards Synchronization and UpdatesThis incident has been resolved.1h 0mResolved
Nov 18, 2025We're experiencing degraded performanceThis incident has been resolved.6h 36mResolved
Nov 14, 2025Delays on boards.This incident has been resolved.1h 47mResolved

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 Productboard 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 Productboard 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 Productboard 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 Productboard outage in this window ran 1d 19h, against a mean recovery of 3h 18m. If you depend on Productboard 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.