Cerbo Outage History

Cerbo is up right now

Cerbo had 32 outages in the last 2 years totaling 243h 32m of downtime, averaging 1.3 incidents per month.

There were 32 Cerbo outages since November 11, 2024 totaling 243h 32m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.cer.bo

Notice April 15, 2026

Reports of Slowness

Detected by Pingoru
Apr 15, 2026, 01:30 PM UTC
Resolved
Apr 15, 2026, 09:00 PM UTC
Duration
7h 30m
Timeline · 3 updates
  1. investigating Apr 15, 2026, 01:30 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 15, 2026, 05:56 PM UTC

    The slowness has improved, but we are still monitoring the issue.

  3. resolved Apr 16, 2026, 07:07 PM UTC

    The incident has been resolved. We made updates to improve how we roll out new features. While everything worked as expected at first, the system experienced issues handling higher traffic during peak hours, which led to the slowness

Read the full incident report →

Notice April 13, 2026

Slowness Reported

Detected by Pingoru
Apr 13, 2026, 03:15 PM UTC
Resolved
Apr 13, 2026, 03:34 PM UTC
Duration
18m
Timeline · 2 updates
  1. investigating Apr 13, 2026, 03:15 PM UTC

    We are currently investigating slowness that some Cerbo customers may be experiencing.

  2. resolved Apr 13, 2026, 03:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 16, 2026

A subset of clients are experiencing extreme slowness when navigating Cerbo

Detected by Pingoru
Jan 16, 2026, 05:04 PM UTC
Resolved
Jan 16, 2026, 09:35 PM UTC
Duration
4h 31m
Timeline · 4 updates
  1. investigating Jan 16, 2026, 05:04 PM UTC

    We are currently investigating this issue.

  2. identified Jan 16, 2026, 07:20 PM UTC

    We've identified network latency in one service region and are continuing to investigate. Next update in 60 minutes or when it's resolved.

  3. monitoring Jan 16, 2026, 07:55 PM UTC

    Application performance has been restored. We are continuing to monitor.

  4. resolved Jan 16, 2026, 09:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 7, 2026

500 Server Error

Detected by Pingoru
Jan 07, 2026, 05:03 PM UTC
Resolved
Jan 07, 2026, 05:34 PM UTC
Duration
31m
Timeline · 3 updates
  1. investigating Jan 07, 2026, 05:03 PM UTC

    We have been made aware of an outage currently affecting one of our clusters. We are actively investigating.

  2. identified Jan 07, 2026, 05:19 PM UTC

    The issue has been identified, and a fix is being implemented.

  3. resolved Jan 07, 2026, 05:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 17, 2025

Third Party Connections

Detected by Pingoru
Oct 17, 2025, 03:00 PM UTC
Resolved
Oct 17, 2025, 07:20 PM UTC
Duration
4h 20m
Affected: BluefinOther
Timeline · 2 updates
  1. identified Oct 17, 2025, 04:42 PM UTC

    We're experiencing an issue connecting to third party providers, impacting eRx and payments.

  2. resolved Oct 17, 2025, 07:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 10, 2025

Partial Outage

Detected by Pingoru
Sep 10, 2025, 06:32 PM UTC
Resolved
Sep 10, 2025, 07:13 PM UTC
Duration
40m
Timeline · 2 updates
  1. investigating Sep 10, 2025, 06:40 PM UTC

    We're currently investigating a service disruption for approximately 25% of our clinics.

  2. resolved Sep 10, 2025, 07:17 PM UTC

    At 11:32 am, we observed one region of clinics go offline. This was the result of an update that was inadvertently applied to multiple regions.

Read the full incident report →

Notice August 15, 2025

Networking Traffic Incident

Detected by Pingoru
Aug 15, 2025, 01:06 PM UTC
Resolved
Aug 15, 2025, 03:27 PM UTC
Duration
2h 21m
Timeline · 2 updates
  1. investigating Aug 15, 2025, 01:06 PM UTC

    We are looking into the incident where a small portion of clients are are down due to an internal networking issue.

  2. resolved Aug 15, 2025, 03:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 8, 2025

Scheduler Down

Detected by Pingoru
Jul 08, 2025, 12:30 PM UTC
Resolved
Jul 08, 2025, 01:05 PM UTC
Duration
34m
Timeline · 2 updates
  1. investigating Jul 08, 2025, 12:30 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 08, 2025, 01:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 23, 2025

Server Down

Detected by Pingoru
Jun 23, 2025, 08:03 PM UTC
Resolved
Jun 23, 2025, 09:00 PM UTC
Duration
56m
Timeline · 4 updates
  1. investigating Jun 23, 2025, 08:03 PM UTC

    We have been made aware of an outage currently affecting one of our clusters. We are actively investigating.

  2. identified Jun 23, 2025, 08:23 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 23, 2025, 08:51 PM UTC

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

  4. resolved Jun 23, 2025, 09:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 23, 2025

Outage - unable to log in. 504 Error occurring. Engineering Team is investigating.

Detected by Pingoru
Jun 23, 2025, 12:13 PM UTC
Resolved
Jun 23, 2025, 02:51 PM UTC
Duration
2h 38m
Timeline · 4 updates
  1. investigating Jun 23, 2025, 12:13 PM UTC

    We're aware and looking into the issue immediately.

  2. identified Jun 23, 2025, 01:29 PM UTC

    The issue has been identified! We have applied a fix and and are starting to see systems come back up after the restart. Currently monitoring.

  3. monitoring Jun 23, 2025, 01:33 PM UTC

    Monitoring the applied fix.

  4. resolved Jun 23, 2025, 02:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 20, 2025

Errors when attempting to pick up lab reports

Detected by Pingoru
Jun 20, 2025, 04:16 PM UTC
Resolved
Jun 20, 2025, 04:23 PM UTC
Duration
7m
Timeline · 2 updates
  1. investigating Jun 20, 2025, 04:16 PM UTC

    We are aware of an error which is keeping lab results from populating in the Lab Results block. We are currently investigating.

  2. resolved Jun 20, 2025, 04:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 17, 2025

Quest Order Sending Error: "Quest's servers refused the order"...

Detected by Pingoru
Jun 17, 2025, 03:29 PM UTC
Resolved
Jun 17, 2025, 04:05 PM UTC
Duration
35m
Affected: Quest Diagnostics
Timeline · 3 updates
  1. investigating Jun 17, 2025, 03:29 PM UTC

    We are currently investigating this issue.

  2. identified Jun 17, 2025, 03:49 PM UTC

    Quest has confirmed they are experiencing a widespread service disruption and are working to resolve the issue. No ETA is available at this time

  3. resolved Jun 17, 2025, 04:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 9, 2025

Outbound Fax Error

Detected by Pingoru
Jun 09, 2025, 03:41 PM UTC
Resolved
Jun 09, 2025, 04:43 PM UTC
Duration
1h 1m
Affected: Fax Services
Timeline · 3 updates
  1. investigating Jun 09, 2025, 03:41 PM UTC

    Interfax has confirmed an issue with their internal system. The error code -150 indicates it's temporary and the customer needs to try again shortly

  2. monitoring Jun 09, 2025, 03:42 PM UTC

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

  3. resolved Jun 09, 2025, 04:43 PM UTC

    This incident has been resolved by Interfax, all outbound faxes should be operational.

Read the full incident report →

Notice May 28, 2025

Update error causing eRx and other issues in one cluster

Detected by Pingoru
May 28, 2025, 02:01 PM UTC
Resolved
May 28, 2025, 05:43 PM UTC
Duration
3h 41m
Timeline · 3 updates
  1. investigating May 28, 2025, 02:01 PM UTC

    We are currently investigating this issue.

  2. identified May 28, 2025, 04:14 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved May 28, 2025, 05:43 PM UTC

    This incident has resolved, and the system is working correctly.

Read the full incident report →

Notice May 20, 2025

Errors when e-ordering via the CPL interface

Detected by Pingoru
May 20, 2025, 05:07 PM UTC
Resolved
May 23, 2025, 08:19 PM UTC
Duration
3d 3h
Timeline · 3 updates
  1. identified May 20, 2025, 05:07 PM UTC

    CPL has confirmed they are aware of the issue and are working towards a resolution.

  2. identified May 20, 2025, 05:09 PM UTC

    The issue appears to be primarily affecting customers in Texas.

  3. resolved May 23, 2025, 08:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 12, 2025

Unable to process payments via Clover Terminal - New Investigation.

Detected by Pingoru
May 12, 2025, 08:45 PM UTC
Resolved
May 14, 2025, 02:39 PM UTC
Duration
1d 17h
Timeline · 2 updates
  1. investigating May 12, 2025, 08:45 PM UTC

    Our development team is actively looking into the issues and errors customers are experiencing with the clover terminal. We apologize for the inconvenience and will provide an update soon.

  2. resolved May 14, 2025, 02:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2025

Zoom is experiencing a partial outage which can affect our services! Zoom's status page: https://status.zoom.us/

Detected by Pingoru
Apr 16, 2025, 07:45 PM UTC
Resolved
Apr 16, 2025, 09:11 PM UTC
Duration
1h 25m
Timeline · 3 updates
  1. investigating Apr 16, 2025, 07:45 PM UTC

    Zoom is investigating the issue. This is not due to Cerbo.

  2. identified Apr 16, 2025, 08:31 PM UTC

    Zoom stated a partial outage with their web portal and zoom meetings. Zoom phone and calling inbound and outbound are currently experiencing degraded performance. https://status.zoom.us/

  3. resolved Apr 16, 2025, 09:11 PM UTC

    Zoom has identified the issue impacting their service, and Cerbo Support is able to take support calls. Please resume contacting Cerbo Support as you normally would.

Read the full incident report →

Notice April 15, 2025

Reports of Chart Parts not working correctly

Detected by Pingoru
Apr 15, 2025, 05:28 PM UTC
Resolved
Apr 15, 2025, 06:41 PM UTC
Duration
1h 13m
Timeline · 3 updates
  1. identified Apr 15, 2025, 05:28 PM UTC

    We've identified an issue causing our chart part feature to not work correctly; our engineers are working on a resolution.

  2. monitoring Apr 15, 2025, 05:31 PM UTC

    A fix is being released, we will be monitoring results.

  3. resolved Apr 15, 2025, 06:41 PM UTC

    This incident has been resolved. We will continue to monitor results.

Read the full incident report →

Notice April 4, 2025

LabCorp Service Interruption and Scanner Issues

Detected by Pingoru
Apr 04, 2025, 01:46 PM UTC
Resolved
Apr 04, 2025, 02:16 PM UTC
Duration
30m
Timeline · 5 updates
  1. identified Apr 04, 2025, 01:46 PM UTC

    LabCorp is experiencing issues with their server which is effecting Cerbo's ability to send and receive labs at the moment. We are patiently waiting on a status update from LabCorp on when the issue will be resolved.

  2. identified Apr 04, 2025, 02:07 PM UTC

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

  3. identified Apr 04, 2025, 02:08 PM UTC

    Cerbo is currently investigating the reports on scanner issues along with the LabCorp issues.

  4. monitoring Apr 04, 2025, 02:14 PM UTC

    Both LabCorp and Scanner issues have be identified and resolved. We are continuing to monitor the situation.

  5. resolved Apr 04, 2025, 02:16 PM UTC

    The LabCorp and Scanner issues have been resolved. We apologize for the disruptions in service this morning. Please report any lingering issues to [email protected].

Read the full incident report →

Notice March 25, 2025

Telemedicine Not Working

Detected by Pingoru
Mar 25, 2025, 01:59 PM UTC
Resolved
Mar 25, 2025, 02:00 PM UTC
Duration
35s
Timeline · 2 updates
  1. identified Mar 25, 2025, 01:59 PM UTC

    We have identified an issue with a recent release that has affected our Telemedicine service. We are rolling back this release and this feature should be working shortly.

  2. resolved Mar 25, 2025, 02:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 24, 2025

Connectivity issues with Access Medical Labs

Detected by Pingoru
Feb 24, 2025, 06:12 PM UTC
Resolved
Feb 24, 2025, 07:49 PM UTC
Duration
1h 37m
Timeline · 3 updates
  1. identified Feb 24, 2025, 06:12 PM UTC

    Connectivity issues with Access Medical Labs which may impact Imported Lab Results and transmitting orders.

  2. monitoring Feb 24, 2025, 07:46 PM UTC

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

  3. resolved Feb 24, 2025, 07:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 20, 2025

Access Medical Lab service

Detected by Pingoru
Feb 20, 2025, 08:57 PM UTC
Resolved
Feb 21, 2025, 06:37 PM UTC
Duration
21h 39m
Timeline · 4 updates
  1. identified Feb 20, 2025, 08:57 PM UTC

    We are continuing to work on a fix.

  2. identified Feb 20, 2025, 08:57 PM UTC

    Connectivity issues with Access Medical Labs which may impact Imported Lab Results and transmitting orders.

  3. identified Feb 21, 2025, 02:33 PM UTC

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

  4. resolved Feb 21, 2025, 06:37 PM UTC

    This incident has been resolved and Imported Lab Results and transmitting orders are active.

Read the full incident report →