Skip to main content
MailerLite logo

Is MailerLite Down?

No — MailerLite is up

Reachable from all 8 checked regions

Average response time: 228ms

Last checked · checks run every 6 hours

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

MailerLite uptime

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

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

30-day history

33-day clean streak
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 31 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, 24 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, 31 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 30 checks
Oct 1: 100.00% uptime, 29 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: no data
Sep 13 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.

ams
87ms
DNS 32ms TCP 2ms TLS 9ms TTFB 86ms
arn
136ms
DNS 54ms TCP 1ms TLS 6ms TTFB 135ms
cdg
88ms
DNS 26ms TCP 2ms TLS 7ms TTFB 77ms
dfw
320ms
DNS 45ms TCP 1ms TLS 8ms TTFB 204ms
ewr
223ms
DNS 19ms TCP 2ms TLS 8ms TTFB 223ms
fra
103ms
DNS 41ms TCP 2ms TLS 8ms TTFB 103ms
gru
618ms
DNS 168ms TCP 2ms TLS 7ms TTFB 416ms
iad
254ms
DNS 31ms TCP 1ms TLS 7ms TTFB 165ms

What MailerLite does

MailerLite is email marketing software for creators and small businesses: subscriber lists, campaign sending, automation sequences, landing pages and signup forms. Businesses run their newsletters and their automated welcome and purchase sequences on it, so it is the dependency behind both scheduled sends and the emails triggered by activity on their own websites.

What an outage looks like

Campaigns will not send, or sit in a sending state without progressing. Automation sequences stop triggering, so welcome emails and follow-ups never reach new subscribers. Signup forms on your own site fail to record subscribers. Landing pages hosted by MailerLite return errors. Click tracking links inside already-delivered emails stop redirecting.

What to do about it

Read status.mailerlite.com, which reports website, App, Email sending, Landing pages and websites, Links and tracking, API and integrations, Subscriber management and Automations as separate components, with the older Classic product grouped apart. Check the one matching your symptom rather than the headline. Hold off resending a stuck campaign until Email sending is operational, since a partial send can otherwise deliver twice.

Is it down for everyone, or just you?

If this page says MailerLite 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

Brevo
Brevo
Klaviyo
Klaviyo
ActiveCampaign
ActiveCampaign
Mailjet
Mailjet

MailerLite outage FAQ

My campaign says it sent but subscribers did not receive it. Is MailerLite down?
Check Email sending on status.mailerlite.com, which is a separate component from the App you scheduled the campaign in, so the interface can report a send that the sending layer never completed. Delivery delays also come from the receiving mail provider rather than from MailerLite. Look at the campaign's own delivery figures before resending, because resending is what creates duplicates.
Do links in emails I already sent stop working during an outage?
They can. Links and tracking is its own component on status.mailerlite.com, and click tracking rewrites links in your emails to route through MailerLite, so an incident there can break links inside messages delivered days earlier. That is one of the few ways a MailerLite outage reaches subscribers who are not expecting anything new from you.
Will subscribers who sign up during an outage be lost?
Possibly, if the submission never reached MailerLite. Subscriber management and API and integrations are separate components, so a form can fail while campaigns send normally. If the signup form sits on your own website, check whether it records submissions anywhere else before assuming the addresses can be recovered after the incident.
Does an outage affect automations that should have triggered?
Automations is its own component, so sequences can stall while ordinary campaigns send. Whether a delayed trigger fires late or is skipped depends on the sequence, so check that automation's own activity for the affected window rather than assuming it caught up. Subscribers who joined during the gap are the ones worth verifying first.
Is it MailerLite or my own sending domain?
Compare scope. Problems with your domain authentication, such as SPF, DKIM or DMARC records, affect only your account's mail and usually show as deliverability failures rather than a stuck send. A MailerLite incident affects many accounts at once and is published on status.mailerlite.com. Check the status page first, then your own domain records.

How we measure this

  • We request MailerLite'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 MailerLite 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 MailerLite 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