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
Feb 23, 2017

No incidents reported today.

Feb 22, 2017

No incidents reported.

Feb 21, 2017

No incidents reported.

Feb 20, 2017

No incidents reported.

Feb 19, 2017

No incidents reported.

Feb 18, 2017

No incidents reported.

Feb 17, 2017

No incidents reported.

Feb 16, 2017
Resolved - The affected upstream provider's circuit has been stable for several hours and no further issues are expected, so we've re-incorporated it into our routing.
Feb 16, 13:39 PST
Monitoring - We have detected and mitigated packet loss on a circuit from one of our redundant upstream providers in our Los Angeles POP. Some customers may have seen a brief burst of packet loss around 10:19AM, but we routed around the affected upstream circuit and no ongoing impact is expected.
Feb 16, 10:23 PST
Feb 15, 2017
Completed - The scheduled maintenance has been completed.
Feb 15, 00:46 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 14, 22:00 PST
Scheduled - We will be upgrading upstream connections at each of our Gateway Clusters to increase capacity on our network. We expect these upgrades to cause no interruption as traffic will fail over to redundant connections.

We will also be pushing a core software update including some minor bug-fixes and enhancements to our algorithms and QoS policies. These upgrades should cause no service impacts.

Expected Impact: None. All traffic will be rerouted to redundant connections during circuit upgrades, and the router upgrades should not cause any interruptions.

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 upgrade process please let us know.
Feb 7, 17:59 PST
Feb 14, 2017
Completed - The scheduled maintenance has been completed.
Feb 14, 01:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 13, 21:00 PST
Scheduled - We will be performing hardware and software upgrades on key pieces of our network infrastructure at each of our Gateway Clusters. You can expect minimal interruption as your service fails over to a redundant Gateway Cluster during the upgrades. You may notice routing changes to/from some destinations as upgrades occur at other clusters.

Expected Impact: A few seconds of packet loss during Gateway Cluster fail-overs, and possible false outage notifications during failover 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 upgrade process please let us know.
Feb 6, 16:24 PST
Feb 12, 2017

No incidents reported.

Feb 11, 2017

No incidents reported.

Feb 10, 2017

No incidents reported.

Feb 9, 2017

No incidents reported.