Skip to content

Outage tracker

MailerLite: incident history

The last 24 hours in detail, MailerLite's declared incident record, and our regional check results beside it.

← Back to MailerLite's check readings

We started checking MailerLite on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when MailerLite reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is MailerLite's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what MailerLite's own status page declared. Below it, any public chatter we saw about MailerLite and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what MailerLite's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about MailerLite in the last 24 hours, which is not evidence that nothing is wrong.
MailerLite's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is MailerLite's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention MailerLite next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%433
US-West99.69%325
Europe100.00%299
Asia-Pacific100.00%182

Their declared record

MailerLite's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Temporary service issuesMinor incident
Nov 4, 2026, 4:21 PM UTC to Nov 4, 2026, 4:46 PM UTC (26 min)resolved
their latest update (Nov 4, 2026, 4:46 PM UTC): This incident has been resolved. All systems are back to normal operations. We apologize for any inconvenience caused and appreciate your patience. A full post-mortem/internal review will be conducted to prevent future occurrences.
Investigating IssuesMajor outage
Feb 27, 2026, 4:49 PM UTC to Feb 28, 2026, 12:21 AM UTC (7h 32m)resolved
their latest update (Feb 28, 2026, 12:21 AM UTC): This incident is now fully resolved, and all systems have returned to normal operations. We sincerely apologize for the inconvenience this caused and deeply appreciate your patience. We are currently conducting a comprehensive post-mortem review to understand the root cause and…
Degraded PerformanceMinor incident
Feb 24, 2026, 4:07 PM UTC to Feb 24, 2026, 4:19 PM UTC (12 min)resolved
their latest update (Feb 24, 2026, 4:19 PM UTC): This incident has been resolved. All systems are back to normal operations. We apologize for any inconvenience caused and appreciate your patience.
Delays in stats and import processingAll systems operational
Dec 7, 2023, 10:11 AM UTC to Dec 7, 2023, 10:58 AM UTC (47 min)resolved
their latest update (Dec 7, 2023, 10:58 AM UTC): This incident has been resolved.
Database MaintenanceMinor incident
Nov 13, 2023, 9:16 AM UTC to Nov 13, 2023, 9:40 AM UTC (23 min)resolved
their latest update (Nov 13, 2023, 9:40 AM UTC): This incident has been resolved.
AI Features DegradedAll systems operational
Nov 8, 2023, 3:19 PM UTC to Nov 8, 2023, 7:36 PM UTC (4h 17m)resolved
their latest update (Nov 8, 2023, 7:36 PM UTC): This incident has been resolved.
Networking Latency IssueMinor incident
Nov 7, 2023, 10:04 AM UTC to Nov 7, 2023, 3:32 PM UTC (5h 28m)resolved
their latest update (Nov 7, 2023, 3:32 PM UTC): This incident has been resolved.
Networking Latency IssueMinor incident
Nov 7, 2023, 9:32 AM UTC to Nov 7, 2023, 9:46 AM UTC (14 min)resolved
their latest update (Nov 7, 2023, 9:46 AM UTC): This incident has been resolved.
Opens DelayedMinor incident
Aug 18, 2023, 12:23 PM UTC to Aug 18, 2023, 3:28 PM UTC (3h 5m)resolved
their latest update (Aug 18, 2023, 3:28 PM UTC): This incident has been resolved.
Emails DelayedMinor incident
Apr 24, 2023, 3:04 PM UTC to Apr 24, 2023, 3:30 PM UTC (26 min)resolved
their latest update (Apr 24, 2023, 3:30 PM UTC): Emails are now processing as normal

Showing the 10 most recent of 26 incidents MailerLite has declared in the history we hold.

These entries are MailerLite's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

MailerLite's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.