Eventive Outage History

Eventive is up right now

Pingoru has recorded 25 incidents for Eventive: 2 in the last 12 months and 0 in the last 90 days.

Source: status.eventive.org

25incidents recorded
2last 12 months
0last 90 days
97 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Eventive in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202610 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 573 (0%)

Incidents, newest first

Critical May 22, 2026 Eventive API Outage –

Started May 22, 2026, 11:45 PM UTC· resolved May 22, 2026, 11:45 PM UTC

  1. resolved May 26, 2026, 08:12 PM UTC

    An API failure occurred during a planned API scale operation due to a configuration error with the scheduling software. This has since been fixed and the root cause has additionally been mitigated.

Read the full incident report →

Major November 4, 2025 Emails are delayed 3h 13m Virtual platform, Event websites, Payment processing, Organizer admin panel

Started Nov 04, 2025, 04:30 PM UTC· resolved Nov 04, 2025, 07:44 PM UTC

  1. investigating Nov 04, 2025, 04:30 PM UTC

    We are currently experienced delays with the sending of emails and mailings. All other functionality is working fine. We will update as we have further information

  2. resolved Nov 04, 2025, 07:44 PM UTC

    This incident has been resolved. All email functionality has returned to normal.

Read the full incident report →

Notice October 20, 2025 Elevated API Errors 12h 1m Virtual platform, Event websites, Payment processing, Organizer admin panel and 1 more

Started Oct 20, 2025, 02:30 PM UTC· resolved Oct 21, 2025, 02:32 AM UTC

  1. investigating Oct 20, 2025, 02:30 PM UTC

    We're experiencing an elevated level of API errors due to a widespread Amazon Web Services outage. Actions may continue to work intermittently. If an action fails, please wait a moment and try again.

  2. investigating Oct 20, 2025, 02:48 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 21, 2025, 02:31 AM UTC

    We are continuing to investigate this issue.

  4. resolved Oct 21, 2025, 02:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 25, 2025 Platform outage 10m Virtual platform, Event websites

Started Sep 25, 2025, 10:21 PM UTC· resolved Sep 25, 2025, 10:31 PM UTC

  1. investigating Sep 25, 2025, 10:21 PM UTC

    We are experiencing a platform wide outage and are actively investigating

  2. resolved Sep 25, 2025, 10:31 PM UTC

    The platform was down from 4:42 CDT to 5:28 CDT due to an issue with our server farm. This issue has been resolved.

Read the full incident report →

Major September 23, 2025 Service outage 8m

Started Sep 23, 2025, 02:34 PM UTC· resolved Sep 23, 2025, 02:42 PM UTC

  1. resolved Sep 23, 2025, 04:03 PM UTC

    There was a 9 minute service outage from 9:34am - 9:42am CDT involving an API service that failed to start. It was quickly resolved.

Read the full incident report →

Notice August 23, 2025 Order database outage 22m

Started Aug 23, 2025, 12:30 AM UTC· resolved Aug 23, 2025, 12:52 AM UTC

  1. resolved Aug 23, 2025, 01:18 AM UTC

    There was a short incident with the ordering database which causes a brief outage from 8:32pm EDT to 8:52pm EDT. This issue has been resolved and service has returned to normal

Read the full incident report →

Major December 9, 2024 Elevates Payment Intent Failure Rates 3h 9m Payment processing

Started Dec 09, 2024, 11:34 PM UTC· resolved Dec 10, 2024, 02:44 AM UTC

  1. investigating Dec 09, 2024, 11:34 PM UTC

    The issue has been resolved and payment processing has returned to normal.

  2. investigating Dec 10, 2024, 01:27 AM UTC

    The issue has been resolved and payment processing has returned to normal.

  3. resolved Dec 10, 2024, 02:44 AM UTC

    This incident has been resolved.

Read the full incident report →