Give Lively Outage History
7 incidents recorded over the last 365 days, 7 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 Give Lively Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 22, 2026 | PHP VulnerabilityGive Lively is not affected by the recent ‘php2shell’ PHP vulnerability. Our platform, donation tools, and payment processing don’t run on PHP. Under our IT Security Framework, we continuously monitor for… | 0 min | Resolved |
| Aug 25, 2026 | Give Lively is experiencing outages.Our engineers have confirmed the platform is performing as expected and the service interruption has been resolved. Thank you so much for your patience. | 3h 10m | Resolved |
| Apr 3, 2026 | Reports of issues affecting our platformThis incident has been resolved. All pages and services are functioning normally again. Thank you for your patience and understanding. To receive future notifications by email or Slack whenever Give Lively creates… | 3h 1m | Resolved |
| Mar 26, 2026 | Payment Form on Event Ticketing Pages experiencing loading issuesOur engineers have deployed a fix for the issue preventing the Payment Form on our Event Ticketing pages and Widgets from loading. Thank you for your patience. | 13 min | Resolved |
| Mar 3, 2026 | Reports of issues affecting our platformThis incident has been resolved. All pages and services are functioning normally again. The total degraded service time was around three hours. Thank you for your patience and understanding. To receive future… | 1h 2m | Resolved |
| Feb 12, 2026 | Text Codes experiencing service issues across multiple carriersText Code service to Verizon users has been restored. Thank you for your patience. | 3333h 39m | Resolved |
| Jan 9, 2026 | Customer Support platform experiencing IssuesIntercom has resolved their service outage. Our Customer Support team is able to respond to chats and emails again. Thank you for your patience! | 48 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 Give Lively 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 Give Lively 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 Give Lively 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 Give Lively outage in this window ran 138d 21h, against a mean recovery of 19d 21h. If you depend on Give Lively 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.