TeamSnap Outage History
9 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 TeamSnap Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 4, 2026 | SERVICE ALERT: Email deliverability IssueThe email delivery issue has been resolved, and emails are now being delivered as expected. | 2h 22m | Resolved |
| Sep 9, 2026 | Scheduled Database maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Sep 5, 2026 | Scheduled Database maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Sep 1, 2026 | Planned Database maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Feb 3, 2026 | SquadLocker maintenanceThe scheduled maintenance has been completed. | 3h 30m | Scheduled |
| Feb 2, 2026 | [2026-02-01] Scheduled MaintenanceThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Jan 11, 2026 | [2026-01-10] Scheduled MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Dec 5, 2025 | SERVICE ALERT: Login Issues Due to Cloudflare OutageCloudflare services are currently operating normally. They are no longer observing elevated errors or latency across the network and the incident has been resolved. | 1h 15m | Resolved |
| Nov 18, 2025 | ⚠️ SERVICE ALERT: Login Issues Due to Cloudflare Outage ⚠️Cloudflare services are currently operating normally. They are no longer observing elevated errors or latency across the network and the incident has been resolved. | 4h 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 TeamSnap 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 TeamSnap 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 TeamSnap 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 TeamSnap outage in this window ran 4h 9m, against a mean recovery of 2h 12m. If you depend on TeamSnap 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.