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 上流のピアリングプロバイダーでは、ピアリング場所における不正設定による問題が発生し、NYCのNYIIX/Telehouseピアリング施設と多くのネットワークとクラウドコネクティビティコンバージとの接続の多くに影響を与えました。 このピアリングプロバイダとのインパクトのインスタンスが重要であるが、Bigleaf Networksは、検出されたときに、代替プロバイダーとこれらの問題を回避するためのパスを頼ることができました。 Bigleafの顧客は、これらのルーティング変更中にこれらのイベントの影響を受け、この影響を受けるネットワークパスを回避しました。これにより、影響を受ける影響を受けた時間中に2〜5分間の接続を失うサイトや回路が発生しました。 今回は、問題が解決してきた上流のピアリングプロバイダでチームが確認しましたが、引き続き密接に監視しています.
公式のインシデント更新を自動翻訳しています。
10月19日、20日、22日には、Bigleaf Networksと、NYC PoPのBigleafカスタマーサイト/サーキットのサブセットが、NYCの上流施設における一連の停電により、ネットワークとバックボーンプロバイダとの接続の問題の影響を受けました。 影響の時: 10/19 - 8:32 PM EDTに1:14 AM EDT 10/20 - 4:56 PM EDTに1:31 AM EDT 10/22 - 6:43 午前 EDT に 8:01 午前 EDT 影響を受けた上流プロバイダーによって、NYCのデータセンター/ネットワーク施設は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.
