- Detected by Pingoru
- Apr 30, 2026, 05:53 PM UTC
- Resolved
- Apr 30, 2026, 08:00 PM UTC
- Duration
- 2h 6m
Affected: Gateway Cluster: Atlanta, GA
Timeline · 3 updates
-
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.
-
monitoring Apr 30, 2026, 07:30 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 30, 2026, 08:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 07:00 PM UTC
- Resolved
- Feb 20, 2026, 09:30 PM UTC
- Duration
- 2h 29m
Affected: Gateway Cluster: Los Angeles, CA
Timeline · 3 updates
-
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.
-
monitoring Feb 20, 2026, 07:11 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 20, 2026, 09:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2025, 07:54 PM UTC
- Resolved
- Oct 02, 2025, 09:57 PM UTC
- Duration
- 2h 3m
Affected: Web Dashboard
Timeline · 3 updates
-
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.
-
monitoring Oct 02, 2025, 08:12 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 02, 2025, 09:57 PM UTC
This incident has been resolved.
Read the full incident report →
Notice September 26, 2025 - Detected by Pingoru
- Sep 26, 2025, 05:01 PM UTC
- Resolved
- Sep 26, 2025, 08:30 PM UTC
- Duration
- 3h 28m
Affected: Gateway Cluster: Seattle, WA
Timeline · 3 updates
-
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.
-
monitoring Sep 26, 2025, 06:11 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 26, 2025, 08:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 12, 2025, 12:41 PM UTC
- Resolved
- Sep 12, 2025, 02:30 PM UTC
- Duration
- 1h 48m
Affected: Web DashboardSite and Circuit Alerts
Timeline · 3 updates
-
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.
-
monitoring Sep 12, 2025, 01:59 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 12, 2025, 02:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2025, 08:07 PM UTC
- Resolved
- Sep 11, 2025, 09:41 PM UTC
- Duration
- 1h 33m
Affected: Gateway Cluster: Frankfurt, DE
Timeline · 3 updates
-
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.
-
monitoring Sep 11, 2025, 08:35 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 11, 2025, 09:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 22, 2025, 05:31 PM UTC
- Resolved
- Aug 22, 2025, 06:39 PM UTC
- Duration
- 1h 8m
Affected: Web Dashboard
Timeline · 3 updates
-
investigating Aug 22, 2025, 05:31 PM UTC
We are currently investigating slowness and intermittent responsiveness with our Bigleaf Cloud Connect Dashboard. Network connectivity is not affected.
-
monitoring Aug 22, 2025, 05:43 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 22, 2025, 06:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 08, 2025, 05:58 PM UTC
- Resolved
- Aug 08, 2025, 06:34 PM UTC
- Duration
- 36m
Affected: Web DashboardSite and Circuit Alerts
Timeline · 3 updates
-
investigating Aug 08, 2025, 05:58 PM UTC
We are currently investigating this issue.
-
monitoring Aug 08, 2025, 06:18 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 08, 2025, 06:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2025, 03:14 PM UTC
- Resolved
- Jul 23, 2025, 04:09 PM UTC
- Duration
- 54m
Affected: Gateway Cluster: Dallas, TX
Timeline · 2 updates
-
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.
-
resolved Jul 23, 2025, 04:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2025, 10:19 PM UTC
- Resolved
- Jul 02, 2025, 11:30 PM UTC
- Duration
- 1h 10m
Affected: Web Dashboard
Timeline · 3 updates
-
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.
-
monitoring Jul 02, 2025, 11:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 02, 2025, 11:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2025, 07:50 PM UTC
- Resolved
- Jun 24, 2025, 09:42 PM UTC
- Duration
- 4d 1h
Affected: Site and Circuit Alerts
Timeline · 5 updates
-
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.
-
identified Jun 20, 2025, 08:12 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 20, 2025, 08:27 PM UTC
A fix has been implemented and we are monitoring the results.
-
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.
-
resolved Jun 24, 2025, 09:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2025, 07:30 PM UTC
- Resolved
- Jun 20, 2025, 10:13 PM UTC
- Duration
- 2h 42m
Affected: Other
Timeline · 4 updates
-
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.
-
identified Jun 20, 2025, 08:12 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 20, 2025, 08:27 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 20, 2025, 10:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 30, 2025, 04:15 PM UTC
- Resolved
- May 30, 2025, 05:24 PM UTC
- Duration
- 1h 9m
Affected: Gateway Cluster: Ashburn, VAGateway Cluster: Atlanta, GAGateway Cluster: Chicago, ILGateway Cluster: Dallas, TXGateway Cluster: Denver, COGateway Cluster: Los Angeles, CAGateway Cluster: New York, NYGateway Cluster: San Jose, CAGateway Cluster: Seattle, WAWeb DashboardGateway Cluster: Frankfurt, DEGateway Cluster: London, GBGateway Cluster: Amsterdam, NLSite and Circuit Alerts
Timeline · 3 updates
-
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.
-
monitoring May 30, 2025, 04:17 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 30, 2025, 05:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 28, 2025, 02:07 PM UTC
- Resolved
- May 28, 2025, 06:08 PM UTC
- Duration
- 4h 1m
Affected: Gateway Cluster: Frankfurt, DE
Timeline · 2 updates
-
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.
-
resolved May 28, 2025, 06:08 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2025, 04:02 PM UTC
- Resolved
- Feb 03, 2025, 08:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 03, 2025, 04:02 PM UTC
Customers connected to our NYC gateway clusters may have experienced up to two brief periods of packet loss between 12:12am PST and 12:22am PST.
Read the full incident report →
- Detected by Pingoru
- Jan 31, 2025, 09:01 PM UTC
- Resolved
- Jan 31, 2025, 10:17 PM UTC
- Duration
- 1h 15m
Affected: Gateway Cluster: Chicago, ILGateway Cluster: New York, NY
Timeline · 3 updates
-
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.
-
monitoring Jan 31, 2025, 09:40 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 31, 2025, 10:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2025, 07:08 PM UTC
- Resolved
- Jan 23, 2025, 02:42 AM UTC
- Duration
- 7h 33m
Affected: Gateway Cluster: Ashburn, VAGateway Cluster: Atlanta, GAGateway Cluster: Chicago, ILGateway Cluster: Dallas, TXGateway Cluster: Denver, COGateway Cluster: Los Angeles, CAGateway Cluster: New York, NYGateway Cluster: San Jose, CAGateway Cluster: Seattle, WAWeb DashboardGateway Cluster: Frankfurt, DEGateway Cluster: London, GBGateway Cluster: Amsterdam, NLSite and Circuit AlertsOther
Timeline · 3 updates
-
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!
-
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.
-
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 →
- Detected by Pingoru
- Jan 01, 2025, 12:41 AM UTC
- Resolved
- Jan 01, 2025, 01:49 AM UTC
- Duration
- 1h 8m
Affected: Site and Circuit Alerts
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Sep 10, 2024, 04:29 PM UTC
- Resolved
- Sep 10, 2024, 08:03 PM UTC
- Duration
- 3h 34m
Affected: Gateway Cluster: Atlanta, GAGateway Cluster: New York, NY
Timeline · 4 updates
-
investigating Sep 10, 2024, 04:29 PM UTC
Bigleaf is currently investigating issues with Network Performance in our ATL and NYC regions. We are working to analyze and mitigate this problem. More updates to follow shortly.
-
investigating Sep 10, 2024, 05:30 PM UTC
We are continuing to investigate this issue.
-
monitoring Sep 10, 2024, 07:04 PM UTC
A fix has been implemented and we are monitoring results
-
resolved Sep 10, 2024, 08:03 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 09, 2024, 08:16 PM UTC
- Resolved
- Aug 09, 2024, 10:25 PM UTC
- Duration
- 2h 8m
Affected: Gateway Cluster: Frankfurt, DE
Timeline · 2 updates
-
investigating Aug 09, 2024, 08:16 PM UTC
Bigleaf is currently investigating issues with Network Performance in our Frankfurt, DE region. We are working to analyze and mitigate this problem as sites in this region are experiencing higher than normal latency.
-
resolved Aug 09, 2024, 10:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2024, 01:22 PM UTC
- Resolved
- Jun 26, 2024, 02:07 PM UTC
- Duration
- 44m
Affected: Gateway Cluster: Denver, CO
Timeline · 2 updates
-
investigating Jun 26, 2024, 01:22 PM UTC
We’re currently investigating reachability problems to certain websites and services in our DEN PoP
-
resolved Jun 26, 2024, 02:07 PM UTC
We've resolved all known reachability problems. If you are experiencing any access issues, or have questions, please don't hesitate to reach out to Bigleaf Support!
Read the full incident report →
- Detected by Pingoru
- Jun 21, 2024, 04:03 PM UTC
- Resolved
- Jun 21, 2024, 06:14 PM UTC
- Duration
- 2h 11m
Affected: Gateway Cluster: San Jose, CAGateway Cluster: Seattle, WA
Timeline · 3 updates
-
investigating Jun 21, 2024, 04:03 PM UTC
We’re currently investigating reachability problems to certain websites such as ADP.
-
identified Jun 21, 2024, 05:20 PM UTC
ADP reachability is restored. We're continuing to investigate other potential reachability issues.
-
resolved Jun 21, 2024, 06:14 PM UTC
We've resolved all known reachability problems. If you are experiencing any access issues, or have questions, please don't hesitate to reach out to Bigleaf Support!
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2024, 04:20 PM UTC
- Resolved
- Jun 18, 2024, 05:31 PM UTC
- Duration
- 1h 11m
Affected: Gateway Cluster: Dallas, TXGateway Cluster: Denver, COGateway Cluster: New York, NY
Timeline · 3 updates
-
investigating Jun 18, 2024, 04:20 PM UTC
We are currently investigating reachability problems to certain websites such as ADP and advisorcompass.
-
investigating Jun 18, 2024, 04:50 PM UTC
We've implemented a workaround and are evaluating the results of it.
-
resolved Jun 18, 2024, 05:31 PM UTC
We've resolved the reachability problems. From 9am to 12pm Central time, a few websites reachable through a direct peering route were being blackholed inadvertently. Avoiding that peering route resolved the issue. We'll follow up to ensure permanent resolution.
Read the full incident report →