Mailosaur Outage History

Mailosaur is up right now

Pingoru has recorded 29 incidents for Mailosaur: 1 in the last 12 months and 0 in the last 90 days.

Source: status.mailosaur.com

29incidents recorded
1last 12 months
0last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Mailosaur in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 515 (0%)

Incidents, newest first

Minor February 26, 2026 SMS deliverability issues for some customers 3h 9m API

Started Feb 26, 2026, 09:08 AM UTC· resolved Feb 26, 2026, 12:18 PM UTC

  1. identified Feb 26, 2026, 09:08 AM UTC

    We’re aware of an issue affecting a small subset of customers that is preventing SMS messages from being delivered to their accounts. Our team is actively investigating, and we expect to restore normal service as soon as possible.

  2. resolved Feb 26, 2026, 12:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 11, 2025 Some customers unable to forward emails 41m SMTP (25), SMTP (2525), SMTP (587), SMTP (25) with STARTTLS and 2 more

Started Aug 11, 2025, 10:10 AM UTC· resolved Aug 11, 2025, 10:52 AM UTC

  1. monitoring Aug 11, 2025, 10:10 AM UTC

    We're aware of an issue affecting some customers who are attempting to send emails to external addresses. As a result of a false-positive inclusion of one of our IP addresses in a blocklist, connections to some mail services are being rejected. The IP in question has since been removed from the list, but it may take several hours for this to propagate to other mail services. We are continuing to monitor this issue and will update when we're comfortable that this has been fully resolved.

  2. resolved Aug 11, 2025, 10:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 5, 2025 Service outage –

Started Aug 05, 2025, 11:00 PM UTC· resolved Aug 05, 2025, 11:00 PM UTC

  1. resolved Aug 06, 2025, 07:02 AM UTC

    Some customers were affected for several hours in certain regions due to a sustained performance degradation of our services. Services experienced significant activity increase, with a delayed scale up resulting in an inability to handle all API calls. This issue has now been resolved, we apologies to all those impacted by this.

Read the full incident report →

Major June 12, 2025 Investigating issues with authentication and API services 1h 24m SMTP (25), POP3 (110), App, SMTP (2525) and 6 more

Started Jun 12, 2025, 06:55 PM UTC· resolved Jun 12, 2025, 08:20 PM UTC

  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.

Read the full incident report →