FreeConference 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 FreeConference Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 28, 2026 | Email Service DisruptionBetween **May 28, 2026, at 15:30 UTC** and **May 29, 2026, at 03:30 UTC**, our platform experienced an email delivery outage. During this 12-hour window, our system emails failed to send. | 7h 28m | Resolved |
| Feb 27, 2026 | FreeConference.com Service DisruptionThis incident has been resolved as of 02/27/2026 15:50 UTC | 58 min | 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 FreeConference 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 FreeConference 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 FreeConference 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 FreeConference outage in this window ran 7h 28m, against a mean recovery of 4h 13m. If you depend on FreeConference 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.