All Systems Operational

About This Site

A Message from our CEO, Joel Mulkey: "Most network providers hide outage info from you, causing confusion and frustration. They all have issues, but don't inform you about them proactively. We instead have a culture of honesty and transparency, so on this public status page you'll find both real-time and historical info about outages or performance problems affecting our service. I hope this level of transparency gives you comfort that we're a partner with you, fighting hard to give you the best possible experience."

How to interpret the info below:
• As a Bigleaf customer, your service experience is generally tied to the performance of the primary gateway cluster for each of your site(s).
• Our software automatically moves your traffic to the secondary gateway cluster for your site(s) if the primary is offline.
• Your network traffic is not affected by any performance issues with the Web App Dashboard, it's solely used for administrative functions and alerting.

Gateway Cluster: Chicago Operational
Gateway Cluster: Los Angeles Operational
Gateway Cluster: New York Operational
Gateway Cluster: Seattle Operational
Web App Dashboard Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 18, 2017

No incidents reported today.

Jan 17, 2017

No incidents reported.

Jan 16, 2017

No incidents reported.

Jan 15, 2017

No incidents reported.

Jan 14, 2017

No incidents reported.

Jan 13, 2017

No incidents reported.

Jan 12, 2017

No incidents reported.

Jan 11, 2017

No incidents reported.

Jan 10, 2017

No incidents reported.

Jan 9, 2017

No incidents reported.

Jan 8, 2017

No incidents reported.

Jan 7, 2017

No incidents reported.

Jan 6, 2017
Resolved - A problem with a routine update to our alerting system caused that system to process some out-of-date site and circuit metrics. The result caused a handful of messages to be sent for site/circuit problems in the past. The resolution to this problem unfortunately required we restart the process in a way that required sending duplicate notifications for all ongoing site/circuit issues.

We apologize for any inconvenience or confusion this issue may have caused. At this point all systems are operating normally, though some notification emails may still be in transit and may continue to arrive after this message. We have already identified the root cause of the problem and are working on the correct means to address it to prevent this problem from reoccurring.

Of note, the alerting system is completely separate of our network and all systems processing customer traffic. At no point was customer traffic affected by the alerting issues.
Jan 6, 17:06 PST
Investigating - We are investigating an issue with a alerting system that may be causing delays in notifications and possibly the resending of old alert notifications. We will update as more information is known.
Jan 6, 16:39 PST
Jan 5, 2017

No incidents reported.

Jan 4, 2017

No incidents reported.