Mailosaur incident

Investigating issues with authentication and API services

Major Resolved View vendor source →

Mailosaur experienced a major incident on June 12, 2025 affecting SMTP (25) and POP3 (110) and 1 more component, lasting 1h 24m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2025, 06:55 PM UTC
Resolved
Jun 12, 2025, 08:20 PM UTC
Duration
1h 24m
Detected by Pingoru
Jun 12, 2025, 06:55 PM UTC

Affected components

SMTP (25)POP3 (110)AppSMTP (2525)POP3 (995)APISMTP (587)SMTP (25) with STARTTLSSMTP (2525) with STARTTLSSMTP (587) with STARTTLS

Update timeline

  1. identified Jun 12, 2025, 06:55 PM UTC

    We are experiencing issues with authentication and core services related to an upstream issue with Google Cloud services (https://status.cloud.google.com/) We will provide updates as soon as we have them, but hope to have normal service resumed shortly.

  2. identified Jun 12, 2025, 07:05 PM UTC

    The following update has been provided by Google - "Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2025-06-12 12:15 PDT with current details." Incident page: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

  3. identified Jun 12, 2025, 07:14 PM UTC

    A further update has been provided by Google - "Our engineers are continuing to mitigate the issue and we have confirmation that the issue is recovered in some locations. We do not have an ETA on full mitigation at this point." Incident page: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

  4. monitoring Jun 12, 2025, 07:33 PM UTC

    Google have now resolved the issue affecting our services - we are continue to monitor the situation.

  5. resolved Jun 12, 2025, 08:20 PM UTC

    This incident has now been resolved.