54 Bigleaf incidents · 2022年2月 — official updates, affected components, duration and resolution details.
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.
We are continuing to monitor for any further issues.
This incident has been resolved.
10月21日,Bigleaf Networks和Bigleaf 客户网站/电路的子集因与我们NYC PoP的一个上游对等供应商的配置不当而受到连接问题的影响. 影响时间: 10/21 - 12:54 PM EDT改为1:16 PM EDT 就上游对等供应商而言,这些问题是由对等地点的错位造成的,并影响到与纽约市的NYIIX/Telehouse对等设施的大部分连接,许多网络和云层连接都集中在这些设施。 虽然与这个对等提供者的影响是重大的,但Bigleaf Networks在发现这些问题后能够依靠替代提供者和路径绕过这些问题. Bigleaf客户的子集在这些路由变化期间受到这些事件的影响并避免了这一受影响的网络路径,这导致一些站点或线路在以上受影响的撞击时间里失去2至5分钟的连接. 此时,我们小组已同上游同行机构确认,问题已经解决,但我们继续密切监测.
自动翻译自官方事件更新。
Bigleaf Networks和Bigleaf 客户网站/电路在我们NYC PoP的一个子集于10月19日,20日和22日,由于NYC的上游设施发生一系列电力故障,与上游网络和骨干供应商的连接问题而受到影响. 撞击时间: 10/19 - 8:32 PM EDT改为1:14 AM EDT 10/20 - 4:56 PM EDT至1:31AM EDT 10/22-6:43 AM EDT改为8:01 AM EDT 就受到影响的上游供应商而言,纽约市的数据中心/网络设施于10/19年失去电网,在最初故障后还出现了其他几起动力/备用发电机问题。 虽然与这家供应商的停机事件相当多,但Bigleaf Networks在发现这些问题后,能够依靠替代供应商和路径绕过这些问题. Bigleaf公司的一个子公司客户在这些线路变更期间受到这些事件的影响并避免了这一受影响的网络路径,这导致一些站点或线路在以上受影响的撞击期间失去2至5分钟的连接。 此时,我们的团队正同上游提供者密切合作,以确保所有相关问题得到解决,并继续密切监测.
自动翻译自官方事件更新。
我们正在调查连接到 Bigleaf Cloud Connect Dashboard 的连接。 网络连接不应受到影响.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
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.
This incident has been resolved.
We are currently investigating network congestion issues that are affecting a subset of customers served out of our NYC gateway cluster. Customer sites may see performance impact over some ISP circuits, causing intermittent packet loss and latency.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating network congestion issues that are impacting a subset of sites connected to our LAX gateway cluster.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A small subset of customers served out of our Los Angeles PoP may have experienced one minute of service interruption or missing performance metrics between 11:02am and 11:05am PST after an emergency change was made to avoid an upstream provider with congestion issues. We are continuing to monitor network performance after these changes, and all connectivity in this region should be performing as expected.
This incident has been resolved.
We are currently investigating an issue with our Bigleaf Cloud Connect Dashboard where it is slow or unresponsive.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with our Bigleaf Cloud Connect Dashboard where it is slow or unresponsive. Customer and network traffic is unaffected.
We have taken steps to mitigate this issue and are seeing improved response times. We are continuing to monitor the situation.
This incident has been resolved.
We are currently investigating an issue with missing metrics and reporting in the Bigleaf Cloud Connect Dashboard.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating slowness and intermittent responsiveness with our Bigleaf Cloud Connect Dashboard. Network connectivity is not affected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
We are currently investigating an issue impacting a small subset of sites in Atlanta where site and circuit status shows incorrect status of 'offline'. Connectivity and traffic should be functioning as normal despite the alerts, but there may be some brief periods of packet loss while resolving the false alerting issues.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
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.
This incident has been resolved.
