Mailprotector logo

Is Mailprotector Down?

SecurityLive status, outages, and incident history

No. Mailprotector is up right now.

Every monitored Mailprotector system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Mailprotector breaks

Mailprotector is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Mailprotector status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Mailprotector Status Summary

As of 18:17 UTC on 14 November 2026, Mailprotector is operational. PulsAPI checked Mailprotector's official status page and found 10 of 10 components operational, with no active incidents. The latest incident, "Microsoft 365 service disruption affecting Shield and CloudFilter", was on Nov 12, 2026 and lasted 25h 10m.

Cite as: PulsAPI, “Mailprotector status”, checked 14 November 2026, 18:17 UTC. https://www.pulsapi.com/services/mailprotector

Mailprotector Component Status

The main Mailprotector systems on this page. All 10 are operational right now.

10operational
Bracket Encrypted Email
Operational
CloudFilter and SafeSend Email Security
Operational
CloudMail Hosted Email
Operational

7 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Issue Notice, Management Console, Radar, SecureStore Archiving, Service Announcements, Shield, XtraMail Continuity.

See all of them free

Component statuses may change independently during partial outages.

Recent Mailprotector Outages & Incidents

Incident history from the official Mailprotector status page, including resolution updates.

Microsoft 365 service disruption affecting Shield and CloudFilterResolved Nov 12, 2026 · 25h 10mResolved

Microsoft reports broad recovery and says it has addressed the underlying issue. It continues to restore service for any remaining affected customers and regions. Mail flow for both Shield and CloudFilter has been operating at normal delivery times. Shield’s Microsoft 365 mailbox notifications are also healthy. --- [2026-11-13T11:18:14.898-05:00] (monitoring) Microsoft reports sustained improvement and continues to address remaining issues. CloudFilter delivery to Microsoft 365 has improved significantly. Previously delayed messages are continuing to be delivered as the queue clears. Shield mail delivery has returned to normal. We’re also restoring the connections that notify Shield about changes in some Microsoft 365 mailboxes. Until those connections are restored, some mailbox activity may take longer to appear in Shield. We’re monitoring both services as recovery continues. --- [2026-11-13T09:09:48.312-05:00] (monitoring) Microsoft reports that its email queues have significantly decreased and are approaching normal levels. It continues to restore affected infrastructure and investigate remaining issues. Shield mail flow has returned to normal delivery times, and its mail queues have caught up. Some Shield feature notifications are still being processed and may be delayed. CloudFilter continues to deliver queued messages to Microsoft 365, though Microsoft is still temporarily deferring some deliveries. We’re continuing to monitor the situation. --- [2026-11-13T08:13:50.980-05:00] (monitoring) Delivery to Microsoft 365 from both Shield and CloudFilter has improved significantly, and delayed messages are being delivered. Shield’s connection to Microsoft 365 mailboxes also appears to be working again. We’re processing the backlog of queued email and mailbox notifications, and some delays may continue while we catch up. Microsoft reports broader improvement in North America and sustained improvement across much of Europe, but says intermittent issues and delivery delays may continue. We’re continuing to monitor the situation. --- [2026-11-12T20:18:16.182-05:00] (identified) Microsoft is testing a configuration change to address an overwhelmed process on affected servers. It has also begun reverting a recent network configuration change and is monitoring the results. Microsoft has not yet confirmed that service has recovered. Shield’s access to Microsoft 365 mailboxes and email delivery to Microsoft 365 through both Shield and CloudFilter remain affected. We’re continuing to monitor the impact and will share updates as more information becomes available. --- [2026-11-12T16:58:17.257-05:00] (identified) Microsoft continues to restart and validate affected servers as it works to restore service. Shield’s access to Microsoft 365 mailboxes and email delivery to Microsoft 365 through both Shield and CloudFilter remain affected. Our changes to isolate Microsoft-bound traffic have improved mail flow to other providers. We’re continuing to monitor the situation and will share updates as more information becomes available. --- [2026-11-12T15:09:55.428-05:00] (identified) We’ve made changes to isolate traffic destined for Microsoft 365 and reduce delays for mail going to other providers. Delivery to Microsoft 365 remains affected. We’re continuing to monitor mail flow. --- [2026-11-12T14:42:53.477-05:00] (identified) Microsoft has begun redistributing connection traffic and restarting affected servers to reduce the impact of its ongoing service disruption. Some connectivity issues and email delivery delays may continue while Microsoft works to restore service. We’re continuing to monitor the impact on Shield and CloudFilter and will share updates as we learn more. --- [2026-11-12T13:38:10.424-05:00] (identified) Microsoft is investigating an Exchange Online issue affecting mailbox access in the Americas. Microsoft is tracking the issue as EX1550543. We’re seeing Microsoft Graph API errors that are affecting Shield’s ability to access Microsoft 365 mailboxes. We’re also seeing Microsoft’s servers temporarily defer messages from Shield and CloudFilter, resulting in email delivery delays for affected Microsoft 365 customers. This issue originates with Microsoft and is not caused by Shield or CloudFilter. Our team is monitoring the impact and investigating options to mitigate delivery delays. We’ll share updates as we learn more.

CloudFilter outbound relay delaysResolved Oct 28, 2026 · 17h 59mResolved

Outbound emails from CloudFilter's relay are performing as expected. This incident is resolved. --- [2026-10-28T18:58:02.953-04:00] (monitoring) We will continue to monitor the outbound relay. --- [2026-10-28T17:31:57.474-04:00] (investigating) We are investigating the outbound relay delays and connection refusals. The team has added resources to the outbound pool to alleviate the immediate impact.

Connection time outs or rate limiting reportedResolved Oct 20, 2026 · 6h 17mResolved

This incident has been resolved. --- [2026-10-20T14:55:01.372-04:00] (monitoring) The queues are caught up, and we are observing normal mail flow at this time. The rate limiting experienced this morning was a response to abusive mail volume that was exacerbated by the reduction in Microsoft servers communicating with Shield. We will continue to monitor our queues through the business day to ensure processing is stable. --- [2026-10-20T14:21:18.000-04:00] (identified) It appears that a reduction in the number of Microsoft servers communicating with Shield this morning contributed to the per-server volume spike. The team has mitigated the connection timeouts and rate limits, and the queues are draining. We do not have an exact time for when the queues will be emptied, but it appears it should be within the hour, most likely sooner. We are continuing to investigate with a priority of restoring stable and expected mail flow. --- [2026-10-20T13:21:07.287-04:00] (investigating) We are continuing to investigate this issue. --- [2026-10-20T12:32:31.478-04:00] (investigating) We are investigating reports of connection timeouts or rate limiting with some domains using Shield. This is not affecting all mail flow.

Mailprotector Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Mailprotector incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% average · 2 days with incidentsNov 14

Live Mailprotector Outage Reports

Problems reported by engineers using Mailprotector. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Mailprotector problems reported yet.

Something wrong with Mailprotector on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Mailprotector

Mailprotector's status page at status.mailprotector.com lists 10 components, such as Bracket Encrypted Email, CloudFilter and SafeSend Email Security and CloudMail Hosted Email. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Mailprotector's side or yours.

Mailprotector Status FAQ

Is Mailprotector down right now?

The verdict at the top of this page comes from the latest poll of the official Mailprotector status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Mailprotector is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Mailprotector recovers.

How do I check Mailprotector uptime history?

PulsAPI tracks Mailprotector uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Mailprotector changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Mailprotector outages?

PulsAPI reads the official Mailprotector status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Mailprotector components?

Yes. PulsAPI monitors 10 individual Mailprotector components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Mailprotector goes down?

Yes. Create a free account and subscribe to Mailprotector: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Mailprotector to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Mailprotector problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Mailprotector?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Mailprotector plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Mailprotector with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services