Frontify Outage History
5 incidents recorded over the last 365 days, 3 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 Frontify Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 11, 2026 | AI search functionality improvementThe search engine upgrade finished successfully and we are replying the last few updates to our search index. | 8h 0m | Scheduled |
| Jul 24, 2026 | Degraded PerformanceThis incident has been resolved. | 1h 58m | Resolved |
| Mar 12, 2026 | Degraded PerformanceThis incident has been resolved. | 33 min | Resolved |
| Jan 13, 2026 | Degraded PerformanceThis incident has been resolved. | 13 min | Resolved |
| Dec 21, 2025 | Search functionality improvementThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
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 Frontify 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 Frontify 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 Frontify 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 Frontify outage in this window ran 8h, against a mean recovery of 3h 45m. If you depend on Frontify 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.