SAFEQ Outage History
SAFEQ is up right nowPingoru has recorded 27 incidents for SAFEQ: 27 in the last 12 months and 17 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 | 2 | 1 of 744 (0%) |
| June 2026 | 5 | 29 of 720 (4%) |
| July 2026 | 2 | 52 of 744 (7%) |
| August 2026 | 6 | 11 of 744 (1%) |
| September 2026 | 5 | 72 of 720 (10%) |
| October 2026 | 4 | 2 of 744 (0%) |
| November 2026 | 3 | 3 of 166 (2%) |
Incidents, newest first
Minor May 27, 2026 Incident - DE Datacenter: Email delivery issue. 20m Embedded [DE] (HP), Embedded [DE] (Konica Minolta), DE Data Center (Scanning), Embedded [DE] (Ricoh) and 4 more
Started May 27, 2026, 09:49 AM UTC· resolved May 27, 2026, 10:09 AM UTC
- investigating May 27, 2026, 09:49 AM UTC
We are currently investigating an issue where emails are not being sent from our DE data center using the default messaging configuration. Notifications, alerts, and other outbound emails relying on this default service are affected and may be delayed or undelivered. **Who is affected:** Customers on OTC clusters using the **default messaging configuration.** **Who is not affected:** Customers who have configured their own messaging service (e.g., custom SMTP server or third-party email provider). Email delivery through your own configuration continues to operate normally. Our engineering team is actively working on a resolution. Updates will follow on this channel.
- resolved May 27, 2026, 10:09 AM UTC
This incident has been resolved.
Minor May 13, 2026 Incident - UK Datacenter: Degraded Service 1h 2m UK Data Centre (Printing), UK Data Centre (Authentication), UK Data Centre (Web Portal)
Started May 13, 2026, 07:46 AM UTC· resolved May 13, 2026, 08:48 AM UTC
- investigating May 13, 2026, 08:14 AM UTC
We are investigating alerts that we have received, and our UK Data Center may be degraded.
- identified May 13, 2026, 08:42 AM UTC
We identified the issue in the UK Data Center. We're currently working to get this resolved as efficiently as possible.
- resolved May 13, 2026, 08:48 AM UTC
This incident has been resolved.