bigtincan Outage History
8 incidents recorded over the last 365 days, 8 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 bigtincan Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Brainshark LatencyThis incident has been resolved. | 3h 49m | Resolved |
| Oct 26, 2026 | Brainshark LatencyThis incident has been resolved. We will continue monitoring this issue. | 3h 57m | Resolved |
| Oct 1, 2026 | Content Hub - Email Delivery IssueThis incident has been resolved. All emails are sending properly now. | 5h 32m | Resolved |
| Sep 29, 2026 | Content Hub IOS Mobile app not loadingThis incident has been resolved. | 25 min | Resolved |
| Sep 29, 2026 | Content Hub Loading SlowlyThis incident has been resolved. | 44 min | Resolved |
| Sep 10, 2026 | Customer branded LinksThis incident has been resolved. | 1h 59m | Resolved |
| Sep 10, 2026 | We are currently experiencing login issues with the ClearSlide platform.This incident has now been resolved | 20 min | Resolved |
| Aug 31, 2026 | Slowness convertingSlowness converting some documents in content HUB | 7h 9m | 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 bigtincan 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 bigtincan 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 bigtincan 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 bigtincan outage in this window ran 7h 9m, against a mean recovery of 2h 59m. If you depend on bigtincan 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.