Omnivore Outage History

Omnivore is up right now

Pingoru has recorded 50 incidents for Omnivore: 5 in the last 12 months and 0 in the last 90 days.

Source: status.omnivore.io

50incidents recorded
5last 12 months
0last 90 days
62 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Omnivore 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 202600 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 524 (0%)

Incidents, newest first

Minor March 20, 2026 Increase in Degraded Locations 1h 17m API

Started Mar 20, 2026, 04:26 PM UTC· resolved Mar 20, 2026, 05:44 PM UTC

  1. investigating Mar 20, 2026, 04:26 PM UTC

    Today around 14:52 UTC, we observed a spike in the number of locations that are flapping between 'online' and 'degraded'. We are currently working to diagnose the issue and restore agent connectivity back to normal levels. We will provide further updates as soon as we have more information to share.

  2. monitoring Mar 20, 2026, 04:53 PM UTC

    Around 16:30 UTC, we applied a change and observed that the number of locations flapping between 'online' and 'degraded' dropped back to baseline levels. We will continue monitoring this issue to make sure our systems remain stable.

  3. resolved Mar 20, 2026, 05:44 PM UTC

    We continue to observe location status stability.

Read the full incident report →

Minor January 22, 2026 Low Ticket Volume for Brink Locations 1h 20m Brink

Started Jan 22, 2026, 07:35 PM UTC· resolved Jan 22, 2026, 08:55 PM UTC

  1. investigating Jan 22, 2026, 07:35 PM UTC

    We are experiencing issues polling tickets for all Brink locations. This started at approximately 17:15 UTC and is ongoing. During this time, we are seeing a lower than expected volume of tickets for all of our Brink locations. Brink is aware of the issue and is working to resolve. We will post updates as they become available.

  2. monitoring Jan 22, 2026, 08:24 PM UTC

    Brink has addressed the issue and we are seeing an influx of new tickets as we move to recover tickets missed during the window. We will continue to monitor and post another update once levels get back to normal.

  3. resolved Jan 22, 2026, 08:55 PM UTC

    We have observed ticket volume return to baseline levels.

Read the full incident report →

Critical December 5, 2025 Omnivore Connectivity Issue 11m API, Brink, Webhooks, Aloha Cloud Connect and 5 more

Started Dec 05, 2025, 09:15 AM UTC· resolved Dec 05, 2025, 09:27 AM UTC

  1. investigating Dec 05, 2025, 09:15 AM UTC

    We are seeing issues occurring with our 3rd-party cloud connectivity provider. This affects most Omnivore systems to varying degrees. We will update further as we have additional details.

  2. monitoring Dec 05, 2025, 09:21 AM UTC

    Connectivity to all services have recovered to normal levels. We are continuing to monitor.

  3. resolved Dec 05, 2025, 09:27 AM UTC

    This incident has been resolved

Read the full incident report →

Minor November 5, 2025 Missing API Activity 44m API/Webhook Activity

Started Nov 05, 2025, 08:52 PM UTC· resolved Nov 05, 2025, 09:36 PM UTC

  1. resolved Nov 05, 2025, 09:48 PM UTC

    Today at 20:52 UTC, we identified an issue with a change to our Request Indexer service that was released yesterday at 20:04 UTC. This change was rolled back at 21:36 UTC. The issue caused all API Requests made between the initial release and the rollback to not display in API Activity. The issue is currently remediated and we are evaluating options to repopulate the missing data.

Read the full incident report →

Major October 20, 2025 Impacts due to AWS outage 9h 6m API, AWS ec2-us-east-1, API/Webhook Activity, Brink and 7 more

Started Oct 20, 2025, 04:41 PM UTC· resolved Oct 21, 2025, 01:48 AM UTC

  1. monitoring Oct 20, 2025, 04:41 PM UTC

    Around 07:11 UTC this morning, Amazon Web Services began experiencing an outage (https://health.aws.amazon.com/health/status). The Omnivore team was alerted at 07:24 UTC and has been monitoring ever since. So far, we haven't seen any clear signal of disruption in Omnivore services other than the following: * ~2.4k agents have entered a degraded state. They are not going offline, so API calls to these locations are succeeding, however customers may be experiencing slower than normal response times. * The Brink API experienced elevated error rates from 15:21-15:41 UTC. Omnivore customers would have also seen an elevated error rate for Brink locations and possibly delayed webhooks. We will continue to monitor for new impacts and will send out updates as needed.

  2. monitoring Oct 20, 2025, 05:50 PM UTC

    Around 17:07 UTC the number of degraded agents returned to baseline levels. We have not observed any other spikes in the error level for Brink API. We are currently not seeing any other areas of concern, but since AWS's incident is still open, we will continue monitoring all of our services for new issues.

  3. monitoring Oct 20, 2025, 07:46 PM UTC

    Around 19:27 UTC, we observed a spike in the error rate for our calls to the Toast API, approaching a 100% failure rate. At this time there are no actions we can take and we will continue to monitor the situation.

  4. monitoring Oct 20, 2025, 08:55 PM UTC

    We are still seeing a near 100% error rate for the Toast integration. We will continue to monitor for improvement.

  5. monitoring Oct 20, 2025, 10:16 PM UTC

    We are still seeing a near 100% error rate for the Toast integration. For further updates, check the Toast status page (https://status.toasttab.com).

  6. resolved Oct 21, 2025, 01:48 AM UTC

    At 00:03 UTC on 10/21 error levels for the Toast integration returned to baseline. As this was the last remaining impacted Omnivore service, we are marking this incident as resolved.

Read the full incident report →

Critical September 11, 2025 Omnivore API Outage 2h 15m API, Brink, Webhooks, Aloha Cloud Connect and 6 more

Started Sep 11, 2025, 05:05 PM UTC· resolved Sep 11, 2025, 07:21 PM UTC

  1. investigating Sep 11, 2025, 05:05 PM UTC

    Around 16:47 UTC, the edge nodes serving the Omnivore API went offline. We are currently investigating and hope to provide a better update once we have more information.

  2. identified Sep 11, 2025, 05:12 PM UTC

    We have identified the trigger to be a bad patch that was released. This patch caused all of our edge servers to become unhealthy. We are currently working to rollback the edge servers to a known good state.

  3. identified Sep 11, 2025, 05:13 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Sep 11, 2025, 05:14 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Sep 11, 2025, 05:45 PM UTC

    We have partially restored some traffic to Omnivore API. We are still working on full resolution and stabilization.

  6. identified Sep 11, 2025, 06:45 PM UTC

    We are seeing traffic approaching baseline levels. Webhooks have begun firing again. We are still working to improve stability.

  7. monitoring Sep 11, 2025, 06:53 PM UTC

    A fix has been implemented, with all edge nodes now back in rotation and reporting healthy. We will continue to monitor for any further impacts.

  8. resolved Sep 11, 2025, 07:21 PM UTC

    Omnivore API and webhooks have been restored to full functionality.

Read the full incident report →

Critical March 5, 2025 NCR CloudConnect API - Increased error rate 3h 30m Aloha Cloud Connect

Started Mar 05, 2025, 07:39 PM UTC· resolved Mar 05, 2025, 11:09 PM UTC

  1. monitoring Mar 05, 2025, 07:39 PM UTC

    Beginning around 19:20 UTC, we began seeing an increased number of timeouts when calling the NCR CloudConnect API impacting ticket and clock entry reads. All API calls to fetch ticket and clock entry data are failing and webhooks may be delayed until service is restored. We are reaching out to our NCR contacts. We will continue to monitor for the issue to resolve. There are no further technical actions we can take to resolve the issue at this time.

  2. monitoring Mar 05, 2025, 08:43 PM UTC

    At this time, we have no further updates from NCR regarding an estimated resolution. We will continue to monitor the situation and update as soon as the situation changes.

  3. monitoring Mar 05, 2025, 10:29 PM UTC

    NCR posted an update to their statuspage at 22:13 UTC indicating they have found a possible solution and are working on stabilizing services. Omnivore calls to the NCR CloudConnect API began seeing a return to more normal error rates at 22:10 UTC and have been maintaining those rates since. We will continue to monitor error rates until NCR has confirmed they have resolved the issue.

  4. resolved Mar 05, 2025, 11:09 PM UTC

    NCR has marked their ordering components as operational and Omnivore has continued to see normal error rates since recovery.

Read the full incident report →

Critical November 21, 2024 Omnivore API - Ticket Writes Failing 12m API

Started Nov 21, 2024, 07:47 PM UTC· resolved Nov 21, 2024, 07:59 PM UTC

  1. identified Nov 21, 2024, 07:47 PM UTC

    We have identified an issue where writes to the Omnivore API are failing 100% of the time. We are implementing actions to recover. During this time, API reads will still function normally. We will provide updates as they are available.

  2. monitoring Nov 21, 2024, 07:53 PM UTC

    We have implemented a fix and are observing successful API writes. We will continue to monitor.

  3. resolved Nov 21, 2024, 07:59 PM UTC

    API has resumed normal functionality

Read the full incident report →