Bigeye Outage History

Bigeye is up right now

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

Source: status.bigeye.com

44incidents recorded
2last 12 months
0last 90 days
60 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Bigeye 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 202611 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 521 (0%)

Incidents, newest first

Critical May 26, 2026 UI Outage 38m UI

Started May 26, 2026, 08:42 PM UTC· resolved May 26, 2026, 09:21 PM UTC

  1. investigating May 26, 2026, 08:42 PM UTC

    We're experiencing an elevated level of service errors from the Bigeye Platform UI and are currently looking into the issue. API users are not affected. Next update: 30 minutes

  2. monitoring May 26, 2026, 09:12 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 26, 2026, 09:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 17, 2026 Elevated API Errors 1h 21m API, UI

Started Feb 17, 2026, 04:10 PM UTC· resolved Feb 17, 2026, 05:32 PM UTC

  1. investigating Feb 17, 2026, 04:10 PM UTC

    We're experiencing an elevated level of service errors from the Bigeye Platform and are currently looking into the issue. This affects both UI and API users. Next update: 30 minutes

  2. investigating Feb 17, 2026, 04:40 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 17, 2026, 05:10 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Feb 17, 2026, 05:11 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Feb 17, 2026, 05:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 3, 2025 Elevated API and UI Errors 9m API, UI

Started Jun 03, 2025, 03:34 PM UTC· resolved Jun 03, 2025, 03:44 PM UTC

  1. investigating Jun 03, 2025, 03:34 PM UTC

    We're experiencing an elevated level of service errors from the Bigeye Platform and are currently looking into the issue. This affects both UI and API users. Next update: 30 minutes

  2. resolved Jun 03, 2025, 03:44 PM UTC

    The incident has been resolved. All services are back online and healthy.

Read the full incident report →

Major May 1, 2025 Scheduled Deltas not running on time 1h 17m API, UI

Started May 01, 2025, 12:53 AM UTC· resolved May 01, 2025, 02:11 AM UTC

  1. investigating May 01, 2025, 12:53 AM UTC

    Scheduled Deltas are not running on time and we are currently looking into the issue. Next update: 2 hours

  2. resolved May 01, 2025, 02:11 AM UTC

    The incident has been resolved. All services are back online and healthy.

Read the full incident report →

Notice April 25, 2025 Scheduled delta runs did not run – API, UI

Started Apr 25, 2025, 07:00 PM UTC· resolved Apr 25, 2025, 07:00 PM UTC

  1. resolved May 01, 2025, 02:23 AM UTC

    Scheduled Delta runs stopped running from April 16th ~5pm PST -> April 25 @ 12pm PST This only affected scheduled Delta runs. Manually run deltas (via UI or API) were unaffected. This outage notification is being posted after the problem was found and corrected.

Read the full incident report →

Critical February 14, 2025 Elevated UI Errors 25m API, UI

Started Feb 14, 2025, 11:54 PM UTC· resolved Feb 15, 2025, 12:20 AM UTC

  1. investigating Feb 14, 2025, 11:54 PM UTC

    We're experiencing an elevated level of service errors from the Bigeye Platform UI and are currently looking into the issue. API users are not affected. Next update: 30 minutes

  2. monitoring Feb 15, 2025, 12:00 AM UTC

    A fix has been deployed and we are monitoring the resolves to ensure the outage has been fully resolved.

  3. resolved Feb 15, 2025, 12:20 AM UTC

    The incident has been resolved. All services are back online and healthy.

Read the full incident report →