Mention Me Ltd Outage History
2 incidents recorded over the last 365 days, 2 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Mention Me Ltd Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | INC-3373 (PHP CVE-2026-109618 / 109619)We have now successfully applied the relevant PHP patches and we will continue to monitor our logs and systems to ensure everything remains stable. | 9h 22m | Resolved |
| Dec 6, 2025 | Significant delays in reportingAll reporting is now completed. We have also resolved the root cause. Customers should now be able to see the latest reporting in the platform. We'll be continue reviewing and ensure this does not happen again in the… | 6h 16m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Mention Me Ltd incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Mention Me Ltd Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Mention Me Ltd acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Mention Me Ltd outage in this window ran 9h 22m, against a mean recovery of 7h 49m. If you depend on Mention Me Ltd in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.