Tactico Outage History
Tactico is up right nowPingoru has recorded 4 incidents for Tactico: 4 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 8 of 744 (1%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 559 (0%) |
Incidents, newest first
Minor August 7, 2026 Email notifications not being sent 8h 10m pro.tactico App
Started Aug 07, 2026, 10:59 PM UTC· resolved Aug 08, 2026, 07:09 AM UTC
- investigating Aug 07, 2026, 10:59 PM UTC
Email notifications were not sent as expected due to an incorrect technical configuration within the notification service. This prevented outbound email events from being processed successfully during the affected period. The issue was identified, the configuration was corrected, and email delivery was restored. We are reviewing the surrounding deployment and configuration controls to reduce the risk of a similar issue recurring.
- identified Aug 08, 2026, 05:02 AM UTC
third party integration affecting service
- monitoring Aug 08, 2026, 06:04 AM UTC
Monitioring fix
- resolved Aug 08, 2026, 07:09 AM UTC
Resolved. Services all running correctly.
Minor February 27, 2026 Ask tactico AI feature performace 19h 40m pro.tactico App
Started Feb 27, 2026, 11:44 AM UTC· resolved Feb 28, 2026, 07:24 AM UTC
- investigating Feb 27, 2026, 11:44 AM UTC
Users are reporting performance issues with the Ask tactico. AI feature when asking a question/generating a prompt. Feature is still working, but responses may be slower.
- identified Feb 27, 2026, 11:46 AM UTC
Engineering team identified significant peak in user requests. Technical solution being prepared.
- resolved Feb 28, 2026, 07:24 AM UTC
Resolved
Minor January 10, 2026 Minor performance issues reported 4m
Started Jan 10, 2026, 04:50 PM UTC· resolved Jan 10, 2026, 04:55 PM UTC
No vendor updates were posted for this incident.