Justuno Outage History
4 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 Justuno Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 17, 2026 | Issue affecting some Justuno merchant websites caused by missing header data and recent updateJustuno released an update at 8:15am PST July 17th that caused some sites to experience blocking elements. The issue was identified and an update was released at 9:48am PST July 17th to resolve it. | 0 min | Resolved |
| Mar 17, 2026 | Profile DB is experiencing a load issueThis incident has been resolved | 23 min | Resolved |
| Mar 16, 2026 | Session report data from March 13-14th 2026 may be incomplete and cannot be recovered.During a migration, some session related data was lost for 3/13/2026 and 3/14/2026. This only affects some session related reporting for those date ranges. | 0 min | Resolved |
| Feb 5, 2026 | App syncs data gapA new security rule we put in place in our cloudflare system to help block bots which ended up disrupting an internal route used for signing payloads meant for syncing out collected form data to connected apps. This… | -11964 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 Justuno 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 Justuno 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 Justuno 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 Justuno outage in this window ran 23 min, against a mean recovery of 8 min. If you depend on Justuno 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.