BigLeaf Outage History

BigLeaf is up right now

Pingoru has recorded 51 incidents for BigLeaf: 7 in the last 12 months and 2 in the last 90 days.

Source: status.bigleaf.net

51incidents recorded
7last 12 months
2last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking BigLeaf 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 202612 of 720 (0%)
May 202600 of 744 (0%)
June 202614 of 720 (1%)
July 202611 of 744 (0%)
August 202600 of 744 (0%)
September 202613 of 720 (0%)
October 202614 of 516 (1%)

Incidents, newest first

Minor October 21, 2026 Network Performance Issues - NYC 3h 34m Gateway Cluster: New York, NY

Started Oct 21, 2026, 06:17 PM UTC· resolved Oct 21, 2026, 09:51 PM UTC

  1. monitoring Oct 21, 2026, 06:17 PM UTC

    A subset of customers served out of the NYC region may have experienced some packet loss and congestion 12:53PM EDT to 1:16PM EDT to due to an upstream network provider issue. At this time the issues have stabilized while our Network Operations group continues to monitor.

  2. monitoring Oct 21, 2026, 06:18 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Oct 21, 2026, 06:53 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 21, 2026, 09:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 11, 2026 Bigleaf Cloud Connect Dashboard DOWN 2h 56m Web Dashboard

Started Sep 11, 2026, 01:34 PM UTC· resolved Sep 11, 2026, 04:31 PM UTC

  1. investigating Sep 11, 2026, 01:34 PM UTC

    We are currently investigating connectivity to the Bigleaf Cloud Connect Dashboard. Network connectivity should not affected.

  2. identified Sep 11, 2026, 02:22 PM UTC

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

  3. monitoring Sep 11, 2026, 02:52 PM UTC

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

  4. resolved Sep 11, 2026, 04:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Bigleaf Cloud Connect Dashboard and API functionality 1h 16m Web Dashboard, Other

Started Jul 08, 2026, 04:55 PM UTC· resolved Jul 08, 2026, 06:11 PM UTC

  1. investigating Jul 08, 2026, 04:55 PM UTC

    We are currently investigating an issue with Bigleaf Cloud Connect Dashboard reporting on CPE and API functionality. Note: Network traffic and connectivity should not be impacted.

  2. resolved Jul 08, 2026, 06:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 30, 2026 Network Performance Issues - ATL 2h 6m Gateway Cluster: Atlanta, GA

Started Apr 30, 2026, 05:53 PM UTC· resolved Apr 30, 2026, 08:00 PM UTC

  1. investigating Apr 30, 2026, 05:53 PM UTC

    We are currently investigating network congestion issues that are impacting a small subset of sites connected to our ATL gateway cluster. To verify if your site is impacted after logging into the Bigleaf Cloud Connect dashboard, follow this link to a filtered list of your accessible sites that are impacted by these issues.

  2. monitoring Apr 30, 2026, 07:30 PM UTC

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

  3. resolved Apr 30, 2026, 08:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 20, 2026 Network Performance Issues - LAX 2h 29m Gateway Cluster: Los Angeles, CA

Started Feb 20, 2026, 07:00 PM UTC· resolved Feb 20, 2026, 09:30 PM UTC

  1. investigating Feb 20, 2026, 07:00 PM UTC

    We are currently investigating network congestion issues that are impacting a subset of sites connected to our LAX gateway cluster.

  2. monitoring Feb 20, 2026, 07:11 PM UTC

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

  3. resolved Feb 20, 2026, 09:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 2, 2025 Bigleaf Cloud Connect Dashboard Slow or Unresponsive 2h 3m Web Dashboard

Started Oct 02, 2025, 07:54 PM UTC· resolved Oct 02, 2025, 09:57 PM UTC

  1. investigating Oct 02, 2025, 07:54 PM UTC

    We are currently investigating an issue with our Bigleaf Cloud Connect Dashboard where it is slow or unresponsive.

  2. monitoring Oct 02, 2025, 08:12 PM UTC

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

  3. resolved Oct 02, 2025, 09:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 26, 2025 Emergency Maintenance - Seattle PoP 3h 28m Gateway Cluster: Seattle, WA

Started Sep 26, 2025, 05:01 PM UTC· resolved Sep 26, 2025, 08:30 PM UTC

  1. investigating Sep 26, 2025, 05:01 PM UTC

    We will be undergoing emergency maintenance in our Seattle Gateway Cluster. Expected Impact: No network connectivity impact is expected If you’re curious about the types of maintenance that we perform, feel free to check out the Maintenance section of our SLA here: http://www.bigleaf.net/sla . If you have any questions or concerns about this maintenance process, please let us know.

  2. monitoring Sep 26, 2025, 06:11 PM UTC

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

  3. resolved Sep 26, 2025, 08:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 12, 2025 Missing Site Metrics 1h 48m Web Dashboard, Site and Circuit Alerts

Started Sep 12, 2025, 12:41 PM UTC· resolved Sep 12, 2025, 02:30 PM UTC

  1. investigating Sep 12, 2025, 12:41 PM UTC

    We are currently investigating an issue with missing metrics and reporting in the Bigleaf Cloud Connect Dashboard.

  2. monitoring Sep 12, 2025, 01:59 PM UTC

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

  3. resolved Sep 12, 2025, 02:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 11, 2025 Emergency Maintenance - Frankfurt, DE Gateway Cluster 1h 33m Gateway Cluster: Frankfurt, DE

Started Sep 11, 2025, 08:07 PM UTC· resolved Sep 11, 2025, 09:41 PM UTC

  1. investigating Sep 11, 2025, 08:07 PM UTC

    We will be undergoing emergency maintenance in our Frankfurt, DE Gateway Cluster. Expected Impact: Customers may experience additional latency during this time, and up to three 10-second packet loss events. If you’re curious about the types of maintenance that we perform, feel free to check out the Maintenance section of our SLA here: http://www.bigleaf.net/sla . If you have any questions or concerns about this maintenance process, please let us know.

  2. monitoring Sep 11, 2025, 08:35 PM UTC

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

  3. resolved Sep 11, 2025, 09:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 8, 2025 Bigleaf Cloud Connect Dashboard Down 36m Web Dashboard, Site and Circuit Alerts

Started Aug 08, 2025, 05:58 PM UTC· resolved Aug 08, 2025, 06:34 PM UTC

  1. investigating Aug 08, 2025, 05:58 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 08, 2025, 06:18 PM UTC

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

  3. resolved Aug 08, 2025, 06:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 23, 2025 Network Performance Issues - DAL 54m Gateway Cluster: Dallas, TX

Started Jul 23, 2025, 03:14 PM UTC· resolved Jul 23, 2025, 04:09 PM UTC

  1. monitoring Jul 23, 2025, 03:14 PM UTC

    A small subset of customers served out of our Dallas PoP may experience up to two brief periods of packet loss as our team investigates and works to resolve an issue.

  2. resolved Jul 23, 2025, 04:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 2, 2025 Bigleaf Cloud Connect - Site Configuration Changes 1h 10m Web Dashboard

Started Jul 02, 2025, 10:19 PM UTC· resolved Jul 02, 2025, 11:30 PM UTC

  1. investigating Jul 02, 2025, 10:19 PM UTC

    We are currently investigating an issue that is preventing any site configuration changes in the Bigleaf Cloud Connect dashboard from applying the updates to deployed Bigleaf Routers. There should be no impact to site connectivity or alerting.

  2. monitoring Jul 02, 2025, 11:00 PM UTC

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

  3. resolved Jul 02, 2025, 11:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 20, 2025 Bigleaf Alert Emails 4d 1h Site and Circuit Alerts

Started Jun 20, 2025, 07:50 PM UTC· resolved Jun 24, 2025, 09:42 PM UTC

  1. investigating Jun 20, 2025, 07:50 PM UTC

    We are currently investigating an issue as ALL Bigleaf alert emails are not being sent from the Bigleaf Cloud Connect dashboard. This includes StatusPage updates.

  2. identified Jun 20, 2025, 08:12 PM UTC

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

  3. monitoring Jun 20, 2025, 08:27 PM UTC

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

  4. monitoring Jun 20, 2025, 10:24 PM UTC

    We are continuing to monitor for further issues and implemented a temporary change while working towards a permanent fix. Current Impact: - To reduce immediate impact, only HIGH or SITE DOWN severity alert emails will be sent as expected. - Alert severity of MEDIUM or LOW will not receive an email alert at this time despite any user configurations. - Any and all alerts are being displayed correctly on the Site and Alerts sections of the Bigleaf Cloud Connect Dashboard.

  5. resolved Jun 24, 2025, 09:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 20, 2025 Bigleaf Support Emails 2h 42m Other

Started Jun 20, 2025, 07:30 PM UTC· resolved Jun 20, 2025, 10:13 PM UTC

  1. investigating Jun 20, 2025, 07:30 PM UTC

    Emails to our primary [email protected] are currently being denied - our team can be reached at our alternative email [email protected]. Our Support Line is up as normal, as well as our Chat and Web ticket submission.

  2. identified Jun 20, 2025, 08:12 PM UTC

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

  3. monitoring Jun 20, 2025, 08:27 PM UTC

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

  4. resolved Jun 20, 2025, 10:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 30, 2025 Backup-Only Circuits 'Down' in BCC 1h 9m Gateway Cluster: Ashburn, VA, Gateway Cluster: Atlanta, GA, Gateway Cluster: Chicago, IL, Gateway Cluster: Dallas, TX and 10 more

Started May 30, 2025, 04:15 PM UTC· resolved May 30, 2025, 05:24 PM UTC

  1. identified May 30, 2025, 04:15 PM UTC

    Bigleaf has identified an issue affecting some "Backup-Only" circuits where they cannot re-establish connectivity with the Bigleaf servers if the "Backup-Only" circuit goes offline. A fix to this issue is currently being pushed out to resolve the issue.

  2. monitoring May 30, 2025, 04:17 PM UTC

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

  3. resolved May 30, 2025, 05:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2025 Network Performance Issues - Frankfurt, DE 4h 1m Gateway Cluster: Frankfurt, DE

Started May 28, 2025, 02:07 PM UTC· resolved May 28, 2025, 06:08 PM UTC

  1. investigating May 28, 2025, 02:07 PM UTC

    We are currently investigating network congestion issues that are impacting a subset of sites connected to our Frankfurt gateway cluster.

  2. resolved May 28, 2025, 06:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 31, 2025 Network Performance Issues - NYC/CHI 1h 15m Gateway Cluster: Chicago, IL, Gateway Cluster: New York, NY

Started Jan 31, 2025, 09:01 PM UTC· resolved Jan 31, 2025, 10:17 PM UTC

  1. investigating Jan 31, 2025, 09:01 PM UTC

    We are currently investigating network congestion issues that are impacting a subset of sites connected to our NYC and CHI gateway clusters.

  2. monitoring Jan 31, 2025, 09:40 PM UTC

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

  3. resolved Jan 31, 2025, 10:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 22, 2025 Bigleaf Support Line Issues 7h 33m Gateway Cluster: Ashburn, VA, Gateway Cluster: Atlanta, GA, Gateway Cluster: Chicago, IL, Gateway Cluster: Dallas, TX and 11 more

Started Jan 22, 2025, 07:08 PM UTC· resolved Jan 23, 2025, 02:42 AM UTC

  1. investigating Jan 22, 2025, 07:08 PM UTC

    We are experiencing some issues with our phone system provider that may cause difficulty in contacting Bigleaf Technical Support. Inbound calls to our main phone numbers at (888) 244-3133 and (503) 985-8298 may be affected. If you are experiencing this, please email our Support team at [email protected]. Our team is monitoring the emails, ticket requests, and voicemails. If you are experiencing an urgent issue please contact us immediately via email and we will contact you as soon as possible. Future updates will be posted here. Thanks for your patience!

  2. monitoring Jan 23, 2025, 12:56 AM UTC

    Our Bigleaf team is continuing to monitor an on-going issue with inbound call routing, but at this time we are only seeing some intermittent problems reaching Bigleaf via our (888) 244-3133 and (503) 985-8298 numbers.

  3. resolved Jan 23, 2025, 02:42 AM UTC

    Our phone service provider has resolved the issue and inbound call service is functioning normally. We apologize for any inconvenience.

Read the full incident report →

Critical January 1, 2025 Site and circuit alert emails delayed 1h 8m Site and Circuit Alerts

Started Jan 01, 2025, 12:41 AM UTC· resolved Jan 01, 2025, 01:49 AM UTC

  1. investigating Jan 01, 2025, 12:41 AM UTC

    We've found a problem with site and circuit alert emails from your Bigleaf service. These alerts have been delayed for the last 40 minutes. Production traffic is not impacted. We plan to provide an update on this incident within an hour.

  2. resolved Jan 01, 2025, 01:49 AM UTC

    We have identified the root cause and deployed a fix for the problem. All site and circuit alerts should now be sent out successfully.

Read the full incident report →