Skip to main content
Mimecast logo

Is Mimecast Down?

No — Mimecast is up

Reachable from all 8 checked regions

Average response time: 1132ms

Last checked · checks run every 6 hours

Official status page: https://status.mimecast.com

Mimecast uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1134ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 69 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

69-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 47 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 39 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

cdg
861ms
DNS 141ms TCP 14ms TLS 19ms TTFB 617ms
dfw
1069ms
DNS 224ms TCP 60ms TLS 63ms TTFB 876ms
ewr
640ms
DNS 334ms TCP 37ms TLS 44ms TTFB 537ms
fra
859ms
DNS 135ms TCP 2ms TLS 4ms TTFB 580ms
gru
1541ms
DNS 622ms TCP 2ms TLS 13ms TTFB 1200ms
iad
396ms
DNS 292ms TCP 3ms TLS 4ms TTFB 388ms
jnb
2570ms
DNS 907ms TCP 0ms TLS 4ms TTFB 1918ms
lax
1127ms
DNS 302ms TCP 2ms TLS 15ms TTFB 672ms

What Mimecast does

Mimecast sits in front of an organisation's email, filtering inbound messages for spam, phishing and malware before they reach Microsoft 365 or Google Workspace, and archiving what passes. It also provides URL and attachment protection, remediation tools and security awareness training. Because it sits in the mail path rather than beside it, an incident affects delivery itself rather than one feature of a mailbox.

What an outage looks like

Inbound mail stops arriving while the mailbox itself works, so Outlook looks healthy and simply goes quiet. Outbound messages queue or return delivery delay notices. Links rewritten by URL protection fail to open, attachments stay held in scanning, and the administration console is unreachable for releasing held mail. Mimecast runs separate regional grids, so one region can be degraded while the others deliver normally.

What to do about it

Check status.mimecast.com and find your grid first: the US, US B, UK, South African, Australian, German, Canadian and Offshore grids are reported separately, each with its own Email Processing, Threat Protection, Web Security, Authentication and Administration Console components. Mail addressed to a queued service is generally retried by the sending server rather than discarded, so wait before asking senders to resend and create duplicates.

Is it down for everyone, or just you?

If this page says Mimecast is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Mimecast outage FAQ

Is my email lost during a Mimecast outage?
Almost never. Mail transfer is built around retries: a sending server that cannot deliver holds the message and tries again over hours or days rather than discarding it, so the backlog usually delivers on its own once Mimecast recovers. Ask senders to wait rather than resend, because a resend during a queue produces two copies when the original attempt finally succeeds.
Which Mimecast grid am I on?
Your administrator knows, and it is worth establishing before an incident rather than during one. Mimecast operates separate regional grids and publishes each one's components separately on status.mimecast.com, so the page can show most of the platform operational while the grid your organisation actually uses is degraded. Reading that page without knowing your grid is how a real incident gets mistaken for a green light.
Does a Mimecast outage mean Microsoft 365 is down?
No, and the reverse holds too. Mimecast filters mail on its way to Microsoft 365 or Google Workspace, so the two fail independently. Your mailbox, calendar and chat can all work normally while nothing new arrives, which is the most confusing shape this incident takes. Check the Microsoft 365 service health dashboard separately before deciding which side is at fault.
Why do links in old emails stop working?
Because URL protection rewrites links to point at Mimecast, which checks the destination at the moment you click rather than when the mail arrived. While that component is degraded the rewritten link fails even though the destination site is fine, and the effect reaches back through your whole mail history rather than just today's messages. It resolves without any action once Web Security is operational.
Can I still release a message from quarantine?
Not while the Administration Console or Remediation is affected, since the console and the end-user digest depend on the same service. Held messages stay held rather than being discarded, so releasing them after recovery works normally and nothing needs re-scanning. If a genuinely urgent message is stuck, ask the sender to route it another way rather than waiting on the queue.

How we measure this

  • We request Mimecast's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Mimecast publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Mimecast goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required