Sherpa° Outage History
3 incidents recorded over the last 365 days, 3 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 Sherpa° Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 1, 2026 | Scheduled maintenance for internal systemsMaintenance has started | 9h 29m | Resolved |
| Sep 1, 2026 | Scheduled maintenance on internal servicesPartner integrations are not affected. Travellers may see slower response times when using Sherpa during the allocated maintenance window. | 23 min | Resolved |
| May 4, 2026 | Order Confirmation Check FailureThe order confirmation check failed during 11:16 am to 1:19 pm ET. Everything is back to normal now | 4 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 Sherpa° 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 Sherpa° 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 Sherpa° 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 Sherpa° outage in this window ran 9h 29m, against a mean recovery of 3h 19m. If you depend on Sherpa° 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.