Pitchero Outage History
2 incidents recorded over the last 365 days, 2 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 Pitchero Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Potential security issue affecting Pitchero CoreThis incident has been resolved. We will continue to monitor our systems over the coming days. | 25h 58m | Resolved |
| Nov 19, 2025 | Video transcoding failingThis incident has been resolved. | 219h 11m | 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 Pitchero 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 Pitchero 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 Pitchero 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 Pitchero outage in this window ran 9d 3h, against a mean recovery of 5d 2h. If you depend on Pitchero 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.