<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0" xmlns:media="http://search.yahoo.com/mrss/">
    <channel>
        <title>Brightbox status</title>
        <link>https://status.brightbox.com/rss</link>
        <description><![CDATA[Status Feed]]></description>
        <atom:link href="https://status.brightbox.com/" rel="self"></atom:link>
                                                                <language>en</language>
        <lastBuildDate>Wed, 15 Apr 2026 18:27:41 +0000</lastBuildDate>
                <item>
            <title><![CDATA[Packet loss on some IPv6 routes]]></title>
                        <link>https://status.brightbox.com/incident/113/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/113/</guid>
            <description><![CDATA[We're currently witnessing packet loss on some IPv6 routes via one of our upstream transit providers. We're investigating further and will provide more details shortly.

UPDATE 12:05 UTC: We've made some routing policy changes to shift IPv6 traffic away from the affected routes while we continue to investigate. Connectivity on affected routes should now be fully restored. If you're still experiencing issues please contact support@brightbox.com with details.

UPDATE 2024-11-19: Our upstream provider identified an issue with IPv6 neighbour instability on one of the LINX peering LANs. They have raised the issue with LINX and it has now been resolved via a configuration change. We've confirmed that traffic via the affected routes is now stable, so have reverted the previous routing policy changes.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Fri, 15 Nov 2024 11:30:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[internal networking problem]]></title>
                        <link>https://status.brightbox.com/incident/107/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/107/</guid>
            <description><![CDATA[We're currently investigating a suspected internal network problem affecting several hosts.

We've identified a problem with a switch port and everything is now back online. We're still investigating the full cause.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Sat, 09 Nov 2024 15:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Error responses from Orbit object storage]]></title>
                        <link>https://status.brightbox.com/incident/105/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/105/</guid>
            <description><![CDATA[We are currently investigating an issue with our Orbit object storage system where some uploads are resulting in 503 responses.

This is now resolved.  More details will be provided soon.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Thu, 24 Oct 2024 09:35:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Partial disruption to internet connectivity]]></title>
                        <link>https://status.brightbox.com/incident/97/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/97/</guid>
            <description><![CDATA[We detected some disruption to internet connectivity due to some abusive behaviour which had been growing since 16:30 UTC. We've identified the source and the disruption is now resolved.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 17 Jun 2024 19:20:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Packet loss on some routes]]></title>
                        <link>https://status.brightbox.com/incident/95/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/95/</guid>
            <description><![CDATA[We're currently witnessing packet loss on one of our upstream transit circuits.

We've taken measures to route around the affected circuit and are currently investigating further while continuing to monitor the situation.

Traffic is routing normally]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Sun, 19 Mar 2023 14:26:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Partial disruption to internet connectivity]]></title>
                        <link>https://status.brightbox.com/incident/93/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/93/</guid>
            <description><![CDATA[We experienced a brief period of packet loss affecting some routes via one of our upstream transit providers between approximately 14:58 UTC and 15:09 UTC this afternoon.

Traffic has now been rerouted via alternative paths, so reachability should have recovered fully. If you're still experiencing network performance issues then please contact us at support@brightbox.com

We're continuing to investigate the root cause and will provide further details shortly.

UPDATE 16:30 UTC: we haven't seen any further disruption on the affected routes since 15:09 UTC, though we're continuing to monitor performance closely.

UPDATE 17:00 UTC: the provider has confirmed they experienced an incident during the period above which has now been fully resolved and no further disruption is anticipated. We're awaiting the completion of their investigation and will provide further details in due course. We're continuing to monitor the performance of the affected routes closely.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Fri, 03 Mar 2023 15:15:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Partial disruption to internet connectivity]]></title>
                        <link>https://status.brightbox.com/incident/91/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/91/</guid>
            <description><![CDATA[We're currently witnessing packet loss on one of our upstream transit circuits. We've taken measures to route around the affected circuit and are currently investigating further while continuing to monitor the situation.

0800 UTC: We're continuing to work with our upstream provider to identify the root cause of the issue. We're still routing traffic via alternative paths as we complete our investigation, so network performance is not impacted.

0940 UTC: Our carrier experienced a core router failure in Telehouse North, affecting traffic routed via London. They're continuing to complete an investigation of the root cause and we'll provide further details once available.

1100 UTC: A critical hardware problem was responsible for the failure of the core router in THN. The router has now been physically replaced and recommissioned. We're continuing to monitor the performance and stability of affected network paths before bringing them back in to service.

1330 UTC: We've started to route some traffic over the previously affected paths as we continue to monitor performance closely.

1530 UTC: We've now restored our standard routing policy and continue to monitor performance.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Thu, 08 Sep 2022 20:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Partial internet disruption]]></title>
                        <link>https://status.brightbox.com/incident/89/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/89/</guid>
            <description><![CDATA[One of our upstream network providers experienced some disruption which affected traffic on some routes.  The issue is now rectified but we're still investigating the root cause.

EDIT: Our provider experienced a power failure in one of their sites between 10:02 and 10:17 BST which lead to the loss of some equipment. Power has now been restored with full redundancy and the root cause has been identified as a battery cell failure in a UPS. Engineers are currently working to replace the failed battery cell.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Tue, 24 May 2022 10:10:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Packet loss to some destinations]]></title>
                        <link>https://status.brightbox.com/incident/87/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/87/</guid>
            <description><![CDATA[We're currently witnessing packet loss on some transit routes which is causing disruption to internet connectivity. We're investigating further and will provide more details ASAP.

UPDATE 11:10 UTC: We're still witnessing packet loss on a subset of routes via one of our upstream transit providers. We've taken steps to reroute affected traffic to minimise any impact while we continue to investigate and attempt to isolate the root cause.

UPDATE 11:18 UTC: Network performance should now be returning to normal. We're still working with the upstream provider to resolve the issue and mitigations remain in place. We'll provide further details as soon as able. If you're still experiencing performance problems then please contact our support team on support@brightbox.com

UPDATE 11:35 UTC: The upstream provider experienced the loss of a core network link between London and Manchester, which lead to errors/packet loss on some routes. The affected circuit has now been removed and traffic has been rerouted across their network via alternative paths. However, we're continuing to keep our own routing mitigations in place at this time and will continue to monitor the situation.

UPDATE 18:35 UTC: An issue has been identified on a fibre segment in Manchester and the estimated time for repair is Wednesday 27th April. Traffic has been rerouted via multiple alternative diverse paths between Manchester and London. We're continuing to monitor the situation, but network performance and redundancy is no longer affected.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 25 Apr 2022 10:45:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Partial network outage]]></title>
                        <link>https://status.brightbox.com/incident/85/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/85/</guid>
            <description><![CDATA[Packet loss has been resolved.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 01 Nov 2021 05:10:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network outage]]></title>
                        <link>https://status.brightbox.com/incident/83/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/83/</guid>
            <description><![CDATA[We're currently investigating a network outage that looks to be related to a switch problem.

UPDATE: This issue is now resolved.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Tue, 26 Oct 2021 23:15:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Power feed interuption in one of our datacentres resuled in network disruption]]></title>
                        <link>https://status.brightbox.com/incident/79/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/79/</guid>
            <description><![CDATA[The interruption of power to networking infrastructure caused some networking disruption as systems failed over to new routes.

The disruption was brief and there are no ongoing issues.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Wed, 19 May 2021 13:05:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[partial internet disruption]]></title>
                        <link>https://status.brightbox.com/incident/77/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/77/</guid>
            <description><![CDATA[One of our upstream network providers experienced some network disruption which affected a small number of routes.  The issue is now rectified and attributed to a router fault in London.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Wed, 31 Mar 2021 14:45:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[partial internet disruption]]></title>
                        <link>https://status.brightbox.com/incident/73/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/73/</guid>
            <description><![CDATA[One of our upstream network providers experienced some network disruption which affected a small number of routes.  The issue is now rectified but we're still investigating the root cause.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Wed, 10 Mar 2021 21:55:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[network outage due to switch stack failure]]></title>
                        <link>https://status.brightbox.com/incident/71/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/71/</guid>
            <description><![CDATA[we're currently investigating a network outage

04:37: this looks to be a partial core switch failure, still investigating

05:31: one of the switches in a core switch stack has failed in an unexpected way and is preventing proper failover. this is affecting connectivity to one zone. we're removing the failed unit. ETA is currently 1 hour.

06:01: the switch stack is now functioning normally and connectivity is resumed.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Wed, 16 Dec 2020 03:46:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[network disruption]]></title>
                        <link>https://status.brightbox.com/incident/69/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/69/</guid>
            <description><![CDATA[A failing PSU caused a some disruption to a switch stack which resulted in some momentary network disruption. Networking is now stable. The unit has been removed from service we're arranging a replacement.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Sat, 08 Aug 2020 20:42:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Emergency network maintenance tonight]]></title>
                        <link>https://status.brightbox.com/incident/67/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/67/</guid>
            <description><![CDATA[One of our upstream transit providers is planning emergency scheduled maintenance to their network tonight (2020-07-09) commencing at 22:00 UTC (23:00 BST). This work is crucial to ensuring the continued performance of the service. The work may result in possible disruption to connectivity to some internet destinations for a period of approximately 20 minutes.

Update: The work was completed with no disruption to service]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Thu, 09 Jul 2020 20:20:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Packet loss on some transit routes]]></title>
                        <link>https://status.brightbox.com/incident/65/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/65/</guid>
            <description><![CDATA[We're currently seeing intermittent packet loss on routes via one of our upstream transit providers. They are aware of the issue and are investigating further. We're currently taking steps to mitigate any impact by rerouting traffic and will provide further information when available.

UPDATE 11:38 UTC: We're continuing to take steps to reroute affected traffic and network performance should now be back to normal. We are continuing to monitor the situation closely.

UPDATE 15:40 UTC: The upstream issue has now been resolved.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 06 Jul 2020 11:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[network disruption]]></title>
                        <link>https://status.brightbox.com/incident/63/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/63/</guid>
            <description><![CDATA[A PDU failure caused a switch stack failover which resulted in some momentary network disruption. Networking is now stable and we're investigating.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Sat, 27 Jun 2020 23:05:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Issues building new Cloud SQL instances]]></title>
                        <link>https://status.brightbox.com/incident/61/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/61/</guid>
            <description><![CDATA[We're currently experiencing an issue which is preventing new Cloud SQL instance builds from completing successfully. We're investigating further and will provide more details shortly.

Existing Cloud SQL instances are unaffected and should continue to perform normally.

UPDATE 11:40 UTC: We've identified a certificate chain issue during the build process causing some configuration steps to fail. We're currency working on a fix and hope to have it deployed within the next 30 minutes.

UPDATE 12:45 UTC: We've deployed a fix and Cloud SQL instance builds are back to normal]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 01 Jun 2020 10:55:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[At risk: emergency network maintenance this evening]]></title>
                        <link>https://status.brightbox.com/incident/59/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/59/</guid>
            <description><![CDATA[One of our transit providers is planning some emergency network maintenance this evening to make critical configuration changes following recommendations from one of their vendors. No impact is anticipated on their network during the work, but it should be considered at risk for the duration.

 

Start: 2020-03-17 20:00 UTC


End: 2020-03-18 00:00 UTC

 

We will continue to monitor network performance and availability closely throughout the scheduled window and will route traffic via alternative paths if necessary.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Tue, 17 Mar 2020 18:28:25 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Packet loss affecting some routes]]></title>
                        <link>https://status.brightbox.com/incident/57/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/57/</guid>
            <description><![CDATA[We experienced two brief periods of disruption on one of our upstream transit routes between 22:00 UTC and 22:15 UTC yesterday evening (2020-03-02), which resulted in significant packet loss to some destinations on the internet. We're currently investigating the root cause of the incident further with the provider in question and will provide more details in due course.

We haven't witnessed any further disruption since yesterday evening and network performance is currently normal.

UPDATE 2020-03-03: The provider was carrying out some planned maintenance work on a core switch in Manchester which was not anticipated to impact our service. We were not notified in advance and were unable to take appropriate action to reroute traffic for the duration of the work. The provider has completed a review of their impact assessment and notification procedure and updated it to ensure we don't see a repeat of this incident in future.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 02 Mar 2020 22:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Overnight network disruption: packet loss on some routes]]></title>
                        <link>https://status.brightbox.com/incident/55/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/55/</guid>
            <description><![CDATA[Last night (2019-09-19) we experienced several short periods of complete packet loss on a number of inbound transit routes between 22:25 and 23:50 UTC, resulting in some disruption to network reachability. Due to the limited number of impacted routes, our monitoring systems failed to detect and respond to the incident as quickly as we'd expect and our engineering team were unable to take any mitigating action at the time as a result.

We've now identified that the incident was caused by disruption in one of our upstream transit networks and we're currently working with the provider to establish the root cause. We'll provide more information here in due course.

We have not experienced any further disruption since 2019-09-19 23:50 UTC and do not anticipate any further impact on network performance going forward. If you have any concerns or are still experiencing any difficulty as a result of the incident then please contact support via email at support@brightbox.com.

We take the performance and reliability of our infrastructure very seriously and are conducting an immediate review of our network monitoring systems to improve the coverage of our reachability monitoring so we can avoid similar failures in future.

UPDATE: The provider was performing scheduled network maintenance work which was not deemed to impact our connectivity, so we were not given prior notice. An issue during the maintenance work resulted in some services flapping on a number of their routers in the London metro area, resulting in the disruption we experienced. We've requested a review of the provider's maintenance notification procedure and that we be informed of any "at risk" works in future.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Thu, 19 Sep 2019 22:25:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network disruption: packet loss on some routes]]></title>
                        <link>https://status.brightbox.com/incident/53/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/53/</guid>
            <description><![CDATA[We're currently seeing 100% packet loss on some routes via one of our transit providers, which is causing some disruption to internet connectivity. We're currently investigating as a matter of urgency and will provide further details ASAP.

UPDATE 11:17 UTC: We're no longer seeing packet loss on the affected routes, though are continuing to monitor performance closely. We're continuing to investigate the root cause.

UPDATE 11:42 UTC: Initial investigation suggests the incident was caused by a line card reboot on one of our provider's core routers in London. Further investigation is currently underway and we'll provide updates in due course.

UPDATE 13:05 UTC: The provider is continuing to monitor the affected router closely and it has remained stable since the incident. Senior engineers from their team are continuing to investigate the underlying cause.

UPDATE 14:10 UTC: Investigation has indicated that the line card reboot was triggered by a potential system bug in the traffic flow analysis process on the affected router. Traffic flow analysis has been disabled temporarily while the provider works with the hardware vendor to verify the bug and produce a permanent resolution.

UPDATE 2019-08-06: The affected router has now been stable for 24 hours. The traffic flow analysis feature which triggered the line card reboot remains disabled and our provider is continuing to work with the hardware vendor to identify a permanent resolution. Any necessary corrective actions will be performed during a future scheduled maintenance window.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 05 Aug 2019 11:10:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Host issue]]></title>
                        <link>https://status.brightbox.com/incident/51/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/51/</guid>
            <description><![CDATA[Our monitoring has reported an issue with one of our hosts, we are currently investigating.

*Update* 00:40 We've resolved an issue with the host and all guests should be responding normally.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Sat, 06 Jul 2019 00:05:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network disruption: packet loss affecting some routes]]></title>
                        <link>https://status.brightbox.com/incident/49/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/49/</guid>
            <description><![CDATA[At approximately 11:25 UTC (12:25 BST) we experienced a brief period of packet loss on some routes due to a incident at one of upstream transit providers. The provider has identified an issue with their network in North London and engineers are currently working on a resolution.

We haven't seen any further disruption since the initial incident and we are continuing to monitor the situation closely.

UPDATE 12:15 UTC: The provider has confirmed that the issue has now been resolved. They're continuing to investigate the root cause of the issue and will provide more details in due course.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Fri, 05 Apr 2019 11:25:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Packet loss between gb1 zones]]></title>
                        <link>https://status.brightbox.com/incident/47/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/47/</guid>
            <description><![CDATA[We have just experienced a period of intermittent packet loss between the gb1 region zones due to a flapping interface on one of our core switches. We have rerouted traffic and shutdown the affected interface and expect everything to recover quickly. We're currently continuing to investigate.

18:30 UTC: We've re-enabled the interface and are continuing to monitor it closely. Traffic is still being routed via alternative paths.

20:00 UTC: Traffic is now being routed normally again.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 18 Feb 2019 16:15:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network disruption: packet loss]]></title>
                        <link>https://status.brightbox.com/incident/45/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/45/</guid>
            <description><![CDATA[We're investigating a problem with internet connectivity.

This looks to be a denial of service attack against one of our customers. It's not under control but but we're still investigating.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Sat, 21 Jul 2018 18:53:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network maintenance: BGP session migrations]]></title>
                        <link>https://status.brightbox.com/incident/43/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/43/</guid>
            <description><![CDATA[We're planning to migrate the BGP sessions with one of our IP transit providers to new hardware within their network. This work will resolve an issue which has caused several incidents of packet loss on some routes over the last few weeks.

We've scheduled the work to take place between 2018-06-25 22:00 UTC (23:00 BST) and 2018-06-25 22:30 UTC (23:30 BST).

We do not anticipate any impact on our network performance or availability as a result, but the network should be considered "at risk" for the duration of the works.

UPDATE 22:20 UTC: The work has been completed as planned.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Thu, 21 Jun 2018 11:01:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network disruption: further packet loss on some routes]]></title>
                        <link>https://status.brightbox.com/incident/41/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/41/</guid>
            <description><![CDATA[We're currently seeing packet loss affecting some routes via the same transit provider as yesterday evening. We're investigating as a matter of urgency.

21:30 UTC: We're no longer seeing packet loss on the affected routes and network performance has returned to normal.

22:05 UTC: We've shutdown the BGP sessions facing the affected transit provider as a precaution until we've received full details of the outage and are routing traffic via alternative paths.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Tue, 29 May 2018 21:10:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network disruption: packet loss on some routes]]></title>
                        <link>https://status.brightbox.com/incident/39/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/39/</guid>
            <description><![CDATA[We're currently seeing packet loss affecting some routes via one of our transit providers. We're investigating as a matter of urgency.

01:00 UTC: The transit provider experienced instability with a router in the path of our service. They are now planning scheduled maintenance to replace the affected device in the coming days.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 28 May 2018 23:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Scheduled network maintenance]]></title>
                        <link>https://status.brightbox.com/incident/37/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/37/</guid>
            <description><![CDATA[One of our IP transit providers will be performing planned maintenance between 2018-06-05 21:00 and 2018-06-06 05:00 UTC to replace a faulty router, which will have an impact on our service. We'll be shutting down our sessions facing them prior to the maintenance window as a precaution and will bring the sessions back up after the work is complete.

We do not anticipate any impact on our network performance or availability, but resilience will be reduced for the duration of the works.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Fri, 25 May 2018 12:35:54 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Network disruption: packet loss]]></title>
                        <link>https://status.brightbox.com/incident/33/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/33/</guid>
            <description><![CDATA[We're currently seeing packet loss affecting some routes via one of our transit providers. We're investigating as a matter of urgency.

15:55 UTC: Throughput on the affected circuit has now returned to normal. If you're still experiencing network performance issues then please contact support@brightbox.com. We're currently continuing to investigate the cause and will provide more information here when available.

16:30 UTC: We haven't seen any further performance problems, but we're still waiting for more details of the incident from one of our upstream transit providers.

20:00 UTC: We're expecting a full outage report to be issued by the provider tomorrow (2018-04-20).

2018-04-24: The outage report indicates the cause was "human error" and that change procedures have been reviewed and updated to prevent a repeat incident in future.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Thu, 19 Apr 2018 15:45:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Transit outage, packet loss to some destinations]]></title>
                        <link>https://status.brightbox.com/incident/31/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/31/</guid>
            <description><![CDATA[We experienced an unexpected outage on one of our transit provider BGP sessions in Manchester between 2018-04-17 3:05:00 UTC and 3:50:00 UTC due to a software issue with their equipment.

Traffic was automatically re-routed via alternative paths, but customers may have experienced a brief period of packet loss between 3:50:00 UTC and 3:55:00 UTC after the session came back up, but some traffic was still being  dropped in the transit provider network.

We're currently awaiting full details of the route cause from the provider and will publish details here once available.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Tue, 17 Apr 2018 03:05:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Partial network disruption]]></title>
                        <link>https://status.brightbox.com/incident/29/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/29/</guid>
            <description><![CDATA[At approximately 13:50 UTC we experienced a brief period of intermittent packet loss across the core network due to a routing misconfiguration. We have now resolved the configuration issue and are conducting an investigation into the cause and taking steps to prevent a reoccurrence.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 29 Jan 2018 13:50:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Packet loss to some US destinations]]></title>
                        <link>https://status.brightbox.com/incident/27/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/27/</guid>
            <description><![CDATA[We're currently experiencing packet loss to some US destinations via one of our upstream transit providers. We're working to identify the affected routes and mitigate the disruption.

UPDATE 12:15 UTC: We've taken steps to route affected traffic via alternative paths and we're currently working with our upstream to identify the cause of the issue.

UPDATE 13:05 UTC: Our transit provider has identified an issue with a third party circuit and is now routing traffic via alternative paths. We're currently waiting for full details of the incident and will provide them here in due course.

UPDATE 2018-01-29: A faulty line card carrying the third party circuit was identified and has now been replaced.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Wed, 24 Jan 2018 11:30:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[maintenance window extended]]></title>
                        <link>https://status.brightbox.com/incident/21/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/21/</guid>
            <description><![CDATA[Tonight's planned maintenance is taking longer than expected. Cloud servers affected by the maintenance window may still be unavailable while we continue the work.

UPDATE: The maintenance is now complete.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Fri, 19 Jan 2018 23:59:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Let's Encrypt certificate validation currently unavailable]]></title>
                        <link>https://status.brightbox.com/incident/19/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/19/</guid>
            <description><![CDATA[Let's Encrypt have identified a security issue with their TLS SNI verification method and have disabled it while they investigate. Our Load Balancers use the TLS SNI verification method so currently cannot create or renew Let's Encrypt certificates.

Let's Encrypt expect that have this solved by Friday 12th January. Currently no overdue renewals are pending, so no existing Load Balanacers should be affected. Creating new load balancers with Let's Encrypt certificates will currently not complete verification.

If you need to build a Load Balancer with SSL/TLS support, you'll need to purchase a certificate and provide it manually.

More information is available on the [Let's Encrypt status page](https://community.letsencrypt.org/t/2018-01-09-issue-with-tls-sni-01-and-shared-hosting-infrastructure/49996)

Update, 11th January 17:40: We've been whitelisted by Let's Encrypt and verifications are now re-enabled. Renewals and new certificate creation is now working fully.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Wed, 10 Jan 2018 10:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Switch stack member crashed]]></title>
                        <link>https://status.brightbox.com/incident/17/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/17/</guid>
            <description><![CDATA[A member of a switch stack has crashed, which is causing some partial network disruption. We're currently investigating further and working to restore service as quickly as possible.

UDPATE 11:30: all affected traffic has been automatically routed via alternative paths and network performance should now be back to normal. We're continuing to investigate the cause of the failure and will provide further updates in due course.

UPDATE 1600: we have identified a power supply fault with the failed unit. The failed unit has now been removed and replaced with a new one and the stack is fully redundant again.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Wed, 12 Jul 2017 11:00:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Host server unresponsive: ps150]]></title>
                        <link>https://status.brightbox.com/incident/15/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/15/</guid>
            <description><![CDATA[Hosts ps150 has become unresponsive and Cloud Servers running on it are currently unavailable. We're investigating and will provide further information as soon as possible.

UPDATE: The affected host has now been rebooted and Cloud Servers which are currently unavailable will be started up again shortly. We're continuing to investigate the cause of the crash.

UPDATE: All affected Cloud Servers have now been started back up. If you're still experiencing problems then please raise a support ticket with support@brightbox.com.

UPDATE: We believe this was due to a Linux kernel bug related to the ksm subsystem. A change that enabled ksm was mistakenly rolled out to these hosts yesterday. We've reversed that chang and ensured that ksm is fully disabled everywhere and will improve monitoring to ensure it isn't changed again.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Sat, 22 Apr 2017 08:07:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Host server unresponsive: ps149]]></title>
                        <link>https://status.brightbox.com/incident/13/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/13/</guid>
            <description><![CDATA[Hosts ps149 has become unresponsive and Cloud Servers running on it are currently unavailable. We're investigating and will provide further information as soon as possible.

UPDATE: The affected host has now been rebooted and Cloud Servers which are currently unavailable will be started up again shortly. We're continuing to investigate the cause of the crash.

UPDATE: All affected Cloud Servers have now been started back up.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Sat, 22 Apr 2017 01:06:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Scheduled maintenance on core router cr1.ifl.gb1.brightbox.com]]></title>
                        <link>https://status.brightbox.com/incident/11/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/11/</guid>
            <description><![CDATA[We're planning to perform some routine maintenance on core router cr1.ifl.gb1.brightbox.com between 2017-03-20T12:00 UTC and 2017-03-20T18:00 UTC. Traffic will be routed via alternative paths and cr1.ifl will be taken out of service prior to carrying out the work, so no customer impact is expected. However, the network should be considered "at risk" for the duration of the work.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Mon, 20 Mar 2017 08:00:54 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Host crash, some servers unavailable]]></title>
                        <link>https://status.brightbox.com/incident/9/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/9/</guid>
            <description><![CDATA[One of our host servers has become unresponsive and crashed, resulting in a small number of servers being unavailable. We're currently investigating further.

UPDATE: The host has now been rebooted and is back online, affected guests have been booted back up and should now be available again. If you're still seeing problems with any of your servers then please contact support.

We identified an issue with the host configuration which may have been responsible for the crash, which has now been fixed.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Sat, 11 Mar 2017 07:35:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Scheduled maintenance on core router cr2.ifl.gb1.brightbox.com]]></title>
                        <link>https://status.brightbox.com/incident/7/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/7/</guid>
            <description><![CDATA[We're planning to perform some routine maintenance on core router cr2.ifl.gb1.brightbox.com between 03-03-2017T11:00 UTC and 03-03-2017T18:00 UTC. Traffic will be routed via alternative paths and cr2.ifl will be taken out of service prior to carrying out the work, so no customer impact is expected. However, the network should be considered "at risk" for the duration of the work.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Thu, 02 Mar 2017 18:20:00 +0000</pubDate>
                                                                                                        </item>
                <item>
            <title><![CDATA[Switch problem affecting access to some cloud servers]]></title>
                        <link>https://status.brightbox.com/incident/5/</link>
            <guid isPermaLink="true">https://status.brightbox.com/incident/5/</guid>
            <description><![CDATA[We're currently investigating an issue with a switch that has affected access to a small number of cloud servers.

*Update:*
We're power cycling the affected switch at the moment and expect it to come back online. ETA currently 15 minutes.

*Update:*
The power cycle of the affected switch is now complete and traffic is passing normally to the affected servers. We are continuing to investigate the issue.]]></description>
                        <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brightbox status</dc:creator>
            <pubDate>Thu, 02 Mar 2017 16:41:00 +0000</pubDate>
                                                                                                        </item>
            </channel>
</rss>
