Is Mimecast Down? How to Check Mimecast Email Security Status Right Now

Check current Mimecast status: statusfield.com/services/mimecast

Mimecast is enterprise email security infrastructure. When it goes down, organizations don't just lose a feature — they lose email filtering, business continuity, and sometimes the ability to send and receive email entirely. For IT teams and security operations, Mimecast uptime is as critical as the mail server itself.

Here's how to check the current status, identify what's broken, and build faster incident response when Mimecast has an outage.

Is Mimecast Down Right Now?

The fastest way to check: View live Mimecast status on Statusfield →

Statusfield monitors Mimecast continuously and shows real-time status for the core services — email processing, the continuity portal, URL rewriting, and the admin console. Updated every 5 minutes.

How to Check Mimecast Status

1. Statusfield (recommended for IT teams) statusfield.com/services/mimecast gives you real-time Mimecast component status with incident history. You can set up instant alerts so your team knows the moment something changes — before the help desk phones start ringing.

2. Mimecast's Official Status Page Mimecast maintains a status page at status.mimecast.com. It covers their primary data centers by region (US, EU, UK, AU, ZA) separately — important because Mimecast operates regional stacks. An EU outage won't necessarily appear as a global incident.

3. Mimecast's Administration Console If the status page shows operational but users are still having issues, open the Mimecast Administration Console and check the Message Center for delivery queues. Delayed or stuck messages in the queue confirm a processing issue even when the status page is green.

4. IT community channels Search Mimecast down on Twitter/X or Spiceworks. Enterprise IT forums often surface region-specific issues before they appear on the vendor status page.

What Actually Breaks During a Mimecast Outage

Mimecast is a multi-service platform. What breaks depends on which component fails.

An email processing outage is the highest-impact scenario — it disrupts every email in your organization simultaneously, both inbound and outbound.

Common Mimecast Failure Symptoms

Why Mimecast Goes Down

Mimecast handles billions of email messages daily. Their infrastructure is regional and complex — and several things can go wrong.

Regional stack issues. Mimecast operates separate infrastructure for US, EU, UK, Australia, and South Africa. An issue in one region — a database failure, a network change, a capacity spike — appears as an outage for customers in that region but not others. This is why Mimecast's status page shows region-by-region breakdowns.

Email volume spikes. Spam campaigns, large broadcast newsletters, and malware outbreak days generate sudden traffic spikes. Processing queues can back up even on healthy infrastructure, causing delayed delivery that users experience as an outage.

Software deployments. Mimecast ships updates to their processing and filtering infrastructure. Deployments occasionally cause brief disruptions as new code is rolled across their server fleet.

Upstream dependencies. Mimecast depends on cloud infrastructure and on your own mail server (Exchange, Microsoft 365, Google Workspace) being reachable at the other end. An issue with an upstream cloud provider in a specific region can cascade into Mimecast delivery failures even when Mimecast's own code is healthy.

Certificate and TLS issues. Enterprise email relies on TLS for secure delivery. Certificate expiration or TLS configuration changes can briefly break SMTP connections between Mimecast and your mail server or between Mimecast and external senders.

Threat intelligence updates. Mimecast continuously updates its threat intelligence — URL reputation databases, attachment sandbox signatures. Occasionally a bad signature update blocks legitimate email until the update is rolled back.

What To Do During a Mimecast Outage

For IT teams managing Mimecast for their organization, a clear incident response plan matters.

Immediately:

1. Check Statusfield and status.mimecast.com — confirm it's Mimecast, not your mail server or DNS
2. Log into the Mimecast Administration Console → check Message Center → Queue for stuck messages — this confirms whether the issue is inbound, outbound, or both
3. Check your region: if Mimecast's status page shows your region as degraded, you have your answer
4. Communicate to your users: a brief "email delivery is delayed — we're aware and investigating" message stops the help desk flood

Technical triage steps:

Confirm MX records are correct:

# Check your MX records still point to Mimecast
nslookup -type=mx yourdomain.com
# Should return something like: mail.yourdomain.com MX 10 eu-smtp-inbound-1.mimecast.com

Check if Mimecast's SMTP endpoints are reachable:

# Test TCP connectivity to Mimecast SMTP
telnet eu-smtp-inbound-1.mimecast.com 25
# If you can't connect, it's a Mimecast network issue or your firewall

Test outbound delivery: Send a test email to an external address (Gmail, etc.) and check the sending header. If the Mimecast relay is rejecting or not accepting, you'll see the failure in the SMTP logs of your mail server.

If the outage is sustained (>30 min):

• Emergency email bypass: If your organization has a Mimecast Email Continuity license, activate the continuity portal — this gives users a web-based inbox even when your mail server or Mimecast is down. Test this before you need it.
• Contact Mimecast support: Open a priority ticket if this is a full outage. Mimecast support has coverage for enterprise customers — check your contract for response-time terms.
• Temporary MX bypass (last resort): In an extended outage with no continuity option, some organizations temporarily point MX records directly to their Exchange/M365. This bypasses Mimecast filtering entirely — only do this if you accept the security trade-off and have documented the change.

After it resolves:

• Review the Message Center for any email that was queued and confirm it delivered
• Check that threat filtering is back to normal
• Add Statusfield monitoring so your team gets alerted the moment Mimecast status changes — before users start calling

Monitoring Mimecast Like an IT Pro

Mimecast is critical infrastructure. Treating it that way means monitoring it proactively.

1. Set up status monitoring — Statusfield tracks Mimecast status continuously and alerts your team the moment something changes. Set up notifications for email, Slack, or webhooks to route into your incident management system.
2. Watch the Message Center daily — Mimecast's built-in queue view shows you delivery volumes and hold rates. An unexpected spike in held messages often precedes a formal status incident.
3. Monitor outbound DKIM pass rates — a drop in DKIM pass rate can signal a signing outage that quietly causes delivery problems at receiving domains (especially Microsoft 365, which is increasingly strict about authentication).
4. Test continuity quarterly — Mimecast's Email Continuity is the critical safety net during mail server or Mimecast outages. Test activation and user access at least quarterly so it works when you need it.
5. Track Mimecast's regional status separately — if your organization spans regions, set up separate monitoring for each Mimecast region your users are in.

How to Get Instant Mimecast Outage Alerts

Enterprise IT teams typically learn about Mimecast outages from user complaints — help desk tickets, Teams messages, people walking to the IT desk. By then, the incident has already impacted dozens or hundreds of users.

Monitor Mimecast on Statusfield and get alerted the moment Mimecast status changes. Route notifications to email, Slack, or a webhook that opens an incident ticket automatically. Your team knows in seconds instead of minutes.

Start monitoring Mimecast →

Frequently Asked Questions

Is Mimecast down right now?

Check the live status at statusfield.com/services/mimecast for real-time Mimecast service status updated continuously.

Why is my email being delayed through Mimecast?

Email delays through Mimecast are usually caused by a processing queue backup (high inbound volume), an attachment sandbox backlog, or a partial infrastructure issue that doesn't trigger a full incident on the status page. Check Statusfield and the Message Center queue in your admin console.

Mimecast email continuity portal isn't loading — is Mimecast down?

The continuity portal has separate infrastructure from the email processing stack. Check status.mimecast.com for your region's continuity component specifically — it may show degraded even when core email processing is operational.

My outbound emails are failing DKIM validation — is this a Mimecast issue?

Possibly. If Mimecast handles your DKIM signing, a signing service outage will cause DKIM failures on outbound email. Check your region's status on Statusfield or contact Mimecast support. In the meantime, check whether the same DKIM signature appears in your email headers — if the d= domain is correct but the signature is invalid, it's a signing issue.

Mimecast is showing operational but users can't receive email — why?

Vendor status pages often show "operational" during partial or regional degradation. Mimecast's status page is regional — confirm you're checking the right region. Also check whether the issue is with Mimecast processing or with your own mail server accepting delivery from Mimecast: a Microsoft 365 or Exchange issue can look like a Mimecast delivery failure. Check Statusfield for an independent view.

How long do Mimecast outages typically last?

Minor incidents (processing delays, partial degradation) generally resolve faster than major infrastructure incidents (regional routing, deployments gone wrong). Full multi-regional outages are rare. Review your Mimecast contract for the specific SLA and credit provisions that apply to your account.

How do I get alerts when Mimecast goes down?

Set up Mimecast monitoring on Statusfield. You'll get instant notifications via email or webhooks the moment Mimecast status changes — so your IT team knows before your users start filing help desk tickets.

What's the difference between a Mimecast outage and my Exchange/Microsoft 365 being down?

Mimecast sits between the internet and your mail server. If Mimecast is down, inbound email queues at the sender or bounces, and your organization may not receive external email. If Exchange/M365 is down, Mimecast can still receive inbound email and queue it — then deliver it when your mail server recovers. Email Continuity lets users access a web inbox during an M365 outage even without Mimecast being down. Diagnose by checking both Statusfield Mimecast and the Microsoft 365 service health dashboard simultaneously.

Can Mimecast deliver email to my Exchange if Mimecast itself is down?

No. If Mimecast's core delivery infrastructure is down in your region, it cannot relay email to your mail server. Inbound email from external senders will queue at their sending mail servers (most SMTP servers retry for 24–72 hours) or bounce if the queue times out. Email Continuity is Mimecast's answer to this — it lets users access a separate Mimecast-hosted inbox as an emergency backup during an outage.