Linkfire 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 Linkfire Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Workspace analytics is unavailableThis incident is now resolved and workspace analytics is fully available again. Although Snowflake recovered from their incident overnight, the service that powers our workspace analytics did not reconnect on its own… | 13h 5m | Resolved |
| Sep 11, 2026 | Landing pages unavailableAll systems continue to be stable since we entered in the monitoring period. Therefore, the incident is now considered to be fully resolved. | 2h 9m | Resolved |
| Jun 30, 2026 | Issue with LoginAll systems are working as intended. Apologies for any inconvenience experienced. | 2h 11m | Resolved |
| Apr 1, 2026 | Issues with Link scanningThe backlog is now clear and all operations have returned to normal. We have verified that no data loss occurred. | 48 min | Resolved |
| Mar 19, 2026 | Delays in link creation and scanningAll systems are now operating normally. Thank you for your patience throughout this disruption. | 1h 2m | Resolved |
| Mar 18, 2026 | Link creation and scanning are unavailableAll systems are operating normally and we are confident in the stability of the service. Thank you for your patience throughout this disruption. | 1h 13m | Resolved |
| Feb 12, 2026 | Intermittent Session Logouts in the SuiteThe underlying capacity issues affecting the authentication service have been resolved. All systems are now operating normally, and the Suite is fully stable. We apologize for the disruption and appreciate your… | 1h 47m | Resolved |
| Dec 3, 2025 | Degraded performance with creating and updating linksThe system has been stable and, therefore, the issue has been resolved. | 2h 5m | 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 Linkfire 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 Linkfire 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 Linkfire 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 Linkfire outage in this window ran 13h 5m, against a mean recovery of 3h 3m. If you depend on Linkfire 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.