ExpressRoute \ ExpressRoute Circuits – Amsterdam

Starting at 12:00 UTC on 01 Jun 2017, customers using ExpressRoute Circuits created in Amsterdam may experience difficulties with public peering when connecting to resources hosted in this region. Customers using the standard configuration as recommended (i.e. ExpressRoute in active-active configuration or even active-passive configuration) should have seen recovery earlier today. We are currently working to mitigate the remainder of those impacted. At this stage engineers have moved customers using premium circuits to a healthy network device. Engineers are still actively investigating a network device as a potential underlying cause and are reloading the device in an effort to mitigate the issue. The reload process will cause a few minutes of connection unavailability to resources for all domain routing for some customers. The next update will be provided in 2 hours, or as events warrant.  

ExpressRoute \ ExpressRoute Circuits – West Europe and North Europe

Starting at 12:00 UTC on 01 Jun 2017, customers using ExpressRoute Circuits in West Europe and North Europe may experience difficulties with public peering and connecting to resources hosted in this region. Customers using the standard configuration as recommended (i.e. ExpressRoute in active-active configuration or even active-passive configuration) will have seen recovery earlier today. We are currently working to mitigate the remainder of those impacted.  Engineers are still actively investigating a network device as a potential underlying cause. As the investigation continues, engineers are working with a third party networking team to apply network configuration changes to circuits for mitigation. The next update will be provided in 2 hours, or as events warrant.  

ExpressRoute \ ExpressRoute Circuits – Europe West and Europe North

Starting at 12:00 UTC on 01 Jun 2017 customer using ExpressRoute Circuits in West Europe and North Europe may experience difficulties with public peering and connecting to resources hosted in this region. Engineers have identified a possible fix for the underlying cause, and are exploring implementation options. The next update will be provided in 2 hour, or as events warrant.

ExpressRoute \ ExpressRoute Circuits – Multi-Region

Starting at 12:00 UTC on 01 Jun 2017, customers using ExpressRoute Circuits in West Europe or North Europe may experience difficulties with public peering and connecting to resources hosted in this region. Engineers are actively working on mitigating the issue. The next update will be provided in 60 minutes, or as events warrant.

Onderhoud dieselaggregaten BIT-2BCD

Geachte relatie,  Dinsdag 6 juni en woensdag 7 juni tussen 07:00 en 17.30 uur zal BIT de nieuwe dieselaggregaten van BIT-2BCD in gebruik nemen. Om de ingebruikname mogelijk te maken zullen we vanaf de start van het onderhoud tot afronding op 7 juni geen reserveaggregaat beschikbaar hebben. De andere aggregaten krijgen een preventieve extra controle. Tijdens het onderhoud blijft er genoeg noodvermogen beschikbaar voor het voeden van BIT-2BCD. Engineers van BIT en de leverancier van de dieselaggregaten zullen bij het onderhoud aanwezig zijn. Mocht u vragen hebben over dit onderhoud, dan kunt u contact opnemen met onze afdeling Customer Care op 0318 648 688 of via support@bit.nl.

[opgelost] Storing algemene telefoonnummer

Op dit moment is het algemene nummer van BIT slecht bereikbaar wegens vermoedelijke problemen bij onze telefonieleverancier. Wanneer u telefonisch contact wenst met een van onze medewerkers gebruikt u dan de "Bel mij" knop bovenaan deze pagina, u word dan teruggebeld door een van onze medewerkers. Wij zijn tevens bereikbaar via e-mail op info@bit.nl en via de "Chat" knop bovenaan deze pagina. Volg de incidentmelding op onze website voor updates inzake dit incident. Update geplaatst om 11.28 Sinds ongeveer 10.40 uur zijn wij weer bereikbaar op ons reguliere nummer. De onbereikbaarheid werd veroorzaakt door een probleem bij onze VoIP leverancier. Het incident is opgelost. Heeft u vragen over dit incident, neem dan contact op met de afdeling Customer Care via +31 (0)318 648 688 of via support@bit.nl.

Issue with accessing Azure services through Mozilla Firefox

Engineers are continuing to work to resolve issues for customers accessing Azure services using Mozilla Firefox and a few other clients. An outdated OCSP response that was cached on Azure services caused failures for customers using these clients.
As a workaround, customers can use an alternative browser - Internet Explorer, Edge, Safari or Chrome. Retries may be successful for some Firefox users. Engineers have taken steps to refresh server side cache for most Azure services that were affected.

The majority of customers will notice improvements access Azure services using Mozilla Firefox and retry should succeed. This includes Azure management portal (https://portal.azure.com), Web Apps, Azure Data Lake Analytics, Azure Data Lake Store, Visual Studio Team Services, Azure Service Fabric, Service Bus, and a subset of Storage. In many cases customers would not have experienced impact to the aforementioned services.
Engineers are continuing to deploy a mitigation for remaining impacted customers. The next update will be provided as more information is available, or as events warrant.

Issue with accessing Azure services through Mozilla Firefox

Engineers are continuing to work to resolve issues for customers accessing Azure services using Mozilla Firefox or other clients which have ‘OCSP stapling’ enabled. An invalid OCSP signing certificate that has been cached is causing failures for a subset of customers. As a workaround, customers can use an alternative browser - Internet Explorer, Edge, Safari or Chrome. Retries may be successful for some Firefox users. Engineers have identified the underlying issue and are currently exploring further options to mitigate the issue for customers using Firefox. The next update will be provided as more information is available, or as events warrant.

Issue with accessing Microsoft Azure portal through Mozilla Firefox

Engineers are continuing to work to resolve issues for customers accessing Azure services using Mozilla Firefox or other clients which have ‘OCSP stapling’ enabled. An invalid OCSP signing certificate that has been cached is causing failures for a subset of customers. As a workaround, customers can use an alternative browser - Internet Explorer, Edge, Safari or Chrome. Retries may be successful for some Firefox users. Engineers have identified the underlying issue and are currently exploring further options to mitigate the issue for customers using Firefox. The next update will be provided as more information is available, or as events warrant.