Famly Outage History
5 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 Famly Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 16, 2026 | Famly is not working for some usersWe’re now confident the problem we’ve identified was fixed, and so we’re closing this incident. If you’re still seeing any problems, please drop our customer team a message. | 1h 53m | Resolved |
| Jul 4, 2026 | Database maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| May 20, 2026 | Famly is not working correctlyThe issues have been solved for today, we unfortunately haven't found the root cause, but have implemented some mitigations, we hope it will reduce the impact while we investigate further, but it might cause issues… | 6h 33m | Resolved |
| May 19, 2026 | Famly is not working correctlyWe’re now confident the problem we’ve identified was fixed, and so we’re closing this incident. If you’re still seeing any problems, please drop our customer team a message. | 43 min | Resolved |
| Dec 9, 2025 | Famly is not working for some users. Data appears inconsistentWe’re now confident the problem we’ve identified was fixed, and so we’re closing this incident. If you’re still seeing any problems, please drop our customer team a message. | 11 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 Famly 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 Famly 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 Famly 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 Famly outage in this window ran 6h 33m, against a mean recovery of 2h 16m. If you depend on Famly 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.