Is TitanHQ down?
Last checked just nowNo incidents right now.
TitanHQ is operational right now. Last checked just now; the most recent incident resolved 36d ago.
Real-time TitanHQ status, recent outages, and incident history — pulled directly from TitanHQ's official status page at https://status.titan.email/ every 5 minutes. Pingoru tracks 11 TitanHQ services and has captured 3 incidents in the last 90 days (99.70% uptime). Get email, Slack, Discord, or webhook alerts the moment TitanHQ reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- POP/IMAP
Timeline · 2 updates
- monitoring · May 08, 2026, 02:49 AM UTC
We are currently experiencing intermittent network issues due to the recent AWS incident affecting the North Virginia (us-east-1) region. As a result, some of our services may experience intermittent impact. At this time, the systems appear to be stable; however, AWS is still actively mitigating the incident as per the status update published on the AWS Health Dashboard. We continue to closely monitor the situation and are taking all necessary steps to minimise any service impact.
- resolved · May 09, 2026, 03:29 AM UTC
The intermittent network issues related to the AWS incident affecting the North Virginia (us-east-1) region have now been resolved. AWS has officially marked the incident as resolved, and all impacted services are currently operating normally. Our monitoring also indicates stable platform performance. We appreciate your patience and understanding during this time.
Latest: The intermittent network issues related to the AWS incident affecting the North Virginia (us-east-1) region have now been resolved. AWS has officially marked the incident as resolv…
-
- Mail Send
Timeline · 2 updates
- investigating · Apr 03, 2026, 11:16 AM UTC
The issue happened due to a congestion issue in our gateway service.
- resolved · Apr 03, 2026, 11:16 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Login
Timeline · 4 updates
- investigating · Mar 30, 2026, 11:11 AM UTC
We are currently investigating this issue.
- investigating · Mar 30, 2026, 11:12 AM UTC
We are continuing to investigate this issue.
- investigating · Mar 30, 2026, 11:13 AM UTC
We are monitoring this issue.
- resolved · Mar 30, 2026, 11:14 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Started May 08, 2026, 02:49 AM UTC · Resolved May 09, 2026, 03:29 AM UTC · 1d
- Started Apr 03, 2026, 07:32 AM UTC · Resolved Apr 03, 2026, 08:26 AM UTC · 54m
- Started Mar 30, 2026, 10:00 AM UTC · Resolved Mar 30, 2026, 10:45 AM UTC · 44m