Historial de interrupciones de Olo

1. August 26, 2026 at 11:29 AM UTCinvestigating

   Estamos investigando un problema con nuestros oleoductos de datos que pueden causar datos obsoletos en partes de Dashboard y reportando.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 22, 2026 at 8:45 PM UTCinvestigating

   Estamos investigando un problema con nuestros oleoductos de datos que pueden causar datos obsoletos en partes de Dashboard y reportando.

2. August 22, 2026 at 8:49 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. August 22, 2026 at 8:53 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. August 23, 2026 at 12:14 AM UTCmonitoring

   Seguimos viendo avances en la tramitación de la acumulación de datos. Seguimos supervisando cualquier otra cuestión.

5. August 23, 2026 at 3:38 AM UTCresolved

   Se ha resuelto el problema con nuestras tuberías de datos, tanto Dashboard como los datos de presentación de informes están actualizados.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 14, 2026 at 4:06 PM UTCinvestigating

   Estamos investigando un problema con nuestros oleoductos de datos que pueden causar datos obsoletos en partes de Dashboard y reportando.

2. July 14, 2026 at 4:06 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 14, 2026 at 5:54 PM UTCresolved

   Se ha resuelto el problema con nuestras tuberías de datos, tanto Dashboard como los datos de presentación de informes están actualizados.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 13, 2026 at 4:48 PM UTCidentified

   Menu Dieciocho eventos Seis están procesando más lento de lo normal, se ha identificado el problema y se está implementando una solución.

2. July 13, 2026 at 5:23 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 13, 2026 at 6:48 PM UTCresolved

   Menu Eighty Sixing procesos funcionan normalmente, este incidente se ha resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 11, 2026 at 2:22 AM UTCinvestigating

   Estamos investigando problemas con el Menú Ocho Seis. Proporcionaremos actualizaciones cuando estén disponibles.

2. July 11, 2026 at 2:49 AM UTCmonitoring

   Estamos observando ochenta y seis eventos procesando a través de nuestros sistemas, las marcas podrían experimentar algunos retrasos mientras trabajamos a través del atraso de eventos. Los ingenieros están monitoreando activamente este tema, proporcionaremos actualizaciones cuando estén disponibles.

3. July 11, 2026 at 4:59 AM UTCresolved

   Ocho eventos de Sixing se están procesando a través de nuestros sistemas como se esperaba, este incidente se ha resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 4, 2026 at 11:53 PM UTCinvestigating

   Estamos investigando una interrupción en el orden de capacidades para Switchboard y proporcionará actualizaciones a medida que estén disponibles.

2. July 5, 2026 at 12:05 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 5, 2026 at 2:35 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 29, 2026 at 12:16 AM UTCinvestigating

   Estamos experimentando un nivel elevado de errores de API y actualmente estamos investigando el problema.

2. June 29, 2026 at 12:28 AM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. June 29, 2026 at 12:46 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. June 29, 2026 at 1:28 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 28, 2026 at 10:51 PM UTCinvestigating

   Estamos experimentando una interrupción del servicio con DoorDash que causaría problemas con las órdenes de Rails. Proporcionaremos actualizaciones cuando estén disponibles.

2. June 28, 2026 at 11:24 PM UTCinvestigating

   Estamos experimentando una interrupción del servicio con DoorDash que causaría problemas con las órdenes de Rails y actualizaciones de Courier Status. Proporcionaremos actualizaciones cuando estén disponibles.

3. June 29, 2026 at 12:30 AM UTCmonitoring

   El servicio con DoorDash ha vuelto a la normalidad y estamos monitoreando activamente en este momento.

4. June 29, 2026 at 1:25 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 21, 2026 at 7:42 PM UTCinvestigating

   We're detecting elevated errors processing orders through NCR Cloud. Ordering may be affected at locations using NCR Cloud as their point of sale provider.

2. June 21, 2026 at 10:03 PM UTCmonitoring

   We are seeing orders being processed successfully through NCR. We are continuing to monitor the situation.

3. June 21, 2026 at 10:21 PM UTCresolved

   This incident has been resolved.

1. June 16, 2026 at 2:11 PM UTCinvestigating

   We are experiencing a service disruption with DoorDash that would cause problems with Rails orders. We will provide updates as they become available.

2. June 16, 2026 at 2:21 PM UTCinvestigating

   We are continuing to investigate this issue.

3. June 16, 2026 at 3:24 PM UTCidentified

   DoorDash has identified the issue and is implementing a fix.

4. June 16, 2026 at 3:54 PM UTCmonitoring

   Service with DoorDash has returned to normal and we are actively monitoring at this time.

5. June 16, 2026 at 4:24 PM UTCresolved

   This incident has been resolved.

1. June 10, 2026 at 5:14 PM UTCidentified

   FreedomPay has identified an issue on their end.

2. June 10, 2026 at 5:20 PM UTCresolved

   This incident has been resolved.

1. June 7, 2026 at 12:42 AM UTCinvestigating

   We are experiencing a service disruption with Postmates that would cause problems with Dispatch. We will provide updates as they become available.

2. June 7, 2026 at 1:16 AM UTCresolved

   This incident has been resolved.

1. June 3, 2026 at 3:17 PM UTCinvestigating

   We are investigating a known issue with the Serve iOS and Android app, we will provide updates as they become available.

2. June 3, 2026 at 5:27 PM UTCinvestigating

   We are continuing to investigate the issue, we will provide updates as they become available.

3. June 3, 2026 at 9:45 PM UTCidentified

   The issue has been identified and our engineering team is working through a fix. We will provide updates as they become available.

4. June 4, 2026 at 12:13 AM UTCidentified

   Our engineering team is continuing to work on a fix for this issue. We will provide updates as they become available.

5. June 4, 2026 at 1:10 AM UTCmonitoring

   A fix has been implemented and we're observing the results on our end. We'll provide updates as they become available.

6. June 4, 2026 at 1:36 AM UTCresolved

   This incident has been resolved.

1. May 30, 2026 at 5:33 PM UTCinvestigating

   We are experiencing a service disruption with Doordash that would cause problems with Dispatch. We will provide updates as they become available.

2. May 30, 2026 at 5:52 PM UTCidentified

   We've identified that only quotes and deliveries for Doordash are impacted. All other DSP's appear operational.

3. May 30, 2026 at 6:25 PM UTCmonitoring

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

4. May 30, 2026 at 6:35 PM UTCresolved

   This incident has been resolved.

1. May 13, 2026 at 12:54 PM UTCinvestigating

   We are investigating an issue with our data pipelines which may cause outdated data in parts of Dashboard and reporting.

2. May 13, 2026 at 1:02 PM UTCidentified

   The issue has been identified and a backlog in reporting data is currently being processed. Customers may experience stale or missing data from their scheduled and Dashboard reports.

3. May 13, 2026 at 3:07 PM UTCmonitoring

   Reporting data is current and we are experiencing recovery.

4. May 13, 2026 at 3:18 PM UTCresolved

   This incident has been resolved.

1. May 12, 2026 at 4:24 PM UTCidentified

   Paytronix has identified an issue on their end.

2. May 12, 2026 at 4:32 PM UTCmonitoring

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

3. May 12, 2026 at 7:51 PM UTCresolved

   This incident has been resolved.

1. May 12, 2026 at 1:59 PM UTCinvestigating

   We're currently investigating an issue generating short links in Switchboard. Users may experience errors when attempting to pay with SMS. Operators should use Pay by Email as a workaround. We will provide updates as they become available.

2. May 12, 2026 at 4:38 PM UTCinvestigating

   We are continuing to investigate this issue.

3. May 12, 2026 at 6:43 PM UTCidentified

   The provider for our SMS links has confirmed that the issue is occurring within their system, and we are awaiting resolution.

4. May 12, 2026 at 8:15 PM UTCmonitoring

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

5. May 12, 2026 at 8:41 PM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 1:04 AM UTCinvestigating

   We are investigating a disruption in ordering capabilities due to an AWS outage and will provide updates as they become available.

2. May 8, 2026 at 2:17 AM UTCmonitoring

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

3. May 8, 2026 at 6:44 AM UTCresolved

   This incident has been resolved.

1. April 27, 2026 at 6:35 PM UTCinvestigating

   We're detecting elevated errors processing payments through Paymentech. Ordering may be affected at locations using Paymentech as their payment provider.

2. April 27, 2026 at 7:30 PM UTCmonitoring

   We are seeing Paymentech transactions return to normal and continue to monitor the situation.

3. April 27, 2026 at 7:41 PM UTCresolved

   This incident has been resolved.

1. April 21, 2026 at 7:01 PM UTCinvestigating

   We're detecting elevated errors processing payments through NCR. Ordering may be affected at locations using NCR as their payment provider.

2. April 21, 2026 at 7:23 PM UTCidentified

   NCR has identified the cause and is making the necessary changes to resolve the issue.

3. April 21, 2026 at 8:20 PM UTCmonitoring

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

4. April 21, 2026 at 8:37 PM UTCresolved

   This incident has been resolved.