Finout Outage History
11 incidents recorded over the last 365 days, 11 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 Finout Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 6, 2026 | Issues logging in into the applicationThis incident has been resolved. | 25 min | Resolved |
| Oct 5, 2026 | Slowness and periodic failures.The issue has been completely resolved | 43 min | Resolved |
| Oct 2, 2026 | Slow Queries and intermittent failures.The incident has been resolved | 49 min | Resolved |
| Sep 23, 2026 | App may be intermittently unavailableThe incident has been resolved | 6 min | Resolved |
| Jul 30, 2026 | The finout app fails to loadThe issue has been resolved | 12 min | Resolved |
| Jul 16, 2026 | Billy and MCP are down.This Incident has been resolved. | 45 min | Resolved |
| Jul 16, 2026 | Application is inaccessibleThe issue has been resolved. | 5h 15m | Resolved |
| Jun 15, 2026 | Billy Chat Service is currently down.The issue was down to a third-party package not pinned down to a specific version which caused a compatibility conflict with our server package. the issue is now resolved and the package version is pinned. | 3h 5m | Resolved |
| May 18, 2026 | Billy AI Assistant is down.We’ve recently refactored our internal API’s to have a more consistent signature. One of the old API signatures was used internally by Billy’s server and was not tested properly. Billy Service relies on that API… | -61 min | Resolved |
| Jan 9, 2026 | We are experiencing Slowness in the ApplicationThe issue has been resolved. We're back to full performance. | 1h 11m | Resolved |
| Nov 18, 2025 | Login page is unavailable and application may not load as expectedThis incident has been resolved. | 2h 19m | 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 Finout 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 Finout 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 Finout 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 Finout outage in this window ran 5h 15m, against a mean recovery of 1h 29m. If you depend on Finout 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.