Foleon Outage History
10 incidents recorded over the last 365 days, 4 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 Foleon Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Resolve PHP VulnerabilityScheduled maintenance is currently in progress. We will provide updates as necessary. | 1h 0m | Scheduled |
| Oct 21, 2026 | Preventative PHP Vulnerability MitigationThis incident has been resolved. | 3h 36m | Resolved |
| Oct 20, 2026 | Analytics dashboard not loadingThis incident has been resolved. | 19 min | Resolved |
| Sep 9, 2026 | Public Preview Access IssueThis incident has been resolved. | 1h 26m | Resolved |
| Aug 13, 2026 | Scheduled database maintenance — rolling restarts expectedThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| May 12, 2026 | Scheduled database maintenance — brief rolling restarts expectedThe scheduled maintenance has been completed. | 20 min | Scheduled |
| Apr 29, 2026 | MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 25, 2026 | MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 28, 2026 | Scheduled Maintenance — CDNThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Dec 17, 2025 | Media Library IssueThis incident has been resolved. | 1h 2m | 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 Foleon 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 Foleon 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 Foleon 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 Foleon outage in this window ran 3h 36m, against a mean recovery of 1h 19m. If you depend on Foleon 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.