Glofox Outage History
1 incident recorded over the last 365 days, 1 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 Glofox Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Feb 17, 2026 | Partial degradationWe are pleased to report that our Vendor (AWS) has resolved their issue driving intermittent Latency impacting Glofox reporting has been resolved. All services are stable, and our systems are operating normally. We will… | 27h 21m | 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 Glofox 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 Glofox 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 Glofox 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 Glofox outage in this window ran 1d 3h, against a mean recovery of 1d 3h. If you depend on Glofox 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.