BlancVPN Outage History

BlancVPN is up right now

There were 12 BlancVPN outages since February 3, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://blancvpnstatus.com

Minor April 29, 2026

Issues with AmneziaWG in the Application

Detected by Pingoru
Apr 29, 2026, 08:39 AM UTC
Resolved
Apr 29, 2026, 08:39 AM UTC
Duration
Affected: 🇩🇪 Berlin🇮🇹 Milan🇩🇪 Frankfurt🇪🇸 Madrid🇨🇴 Bogota🇮🇪 Dublin🇺🇸 Houston🇳🇴 Oslo🇿🇦 Johannesburg🇰🇿 Almaty🇳🇱 Amsterdam🇬🇷 Athens🇮🇳 Bangalore🇷🇴 Bucharest🇦🇷 Buenos Aires🇩🇰 Copenhagen🇲🇾 Kuala Lumpur🇺🇸 Los Angeles🇫🇮 Oulu🇺🇦 Kyiv🇫🇷 Paris🇨🇿 Prague🇲🇽 Queretaro🇧🇷 Sao Paulo🇰🇷 Seoul🇺🇸 San Jose🇸🇬 Singapore🇧🇬 Sofia🇸🇪 Stockholm🇦🇺 Sydney🇯🇵 Tokyo🇺🇸 New York🇵🇪 Lima🇦🇹 Vienna🇵🇱 Warsaw🇭🇷 Zagreb🇨🇭 Zurich🇭🇺 Budapest🇸🇰 Bratislava🇹🇷 Istanbul🇬🇧 London🇺🇸 Miami🇮🇱 Tel Aviv🇧🇪 Brussels🇦🇪 Fujairah🇭🇰 Hong Kong🇵🇹 Lisbon🇨🇦 Toronto🇱🇹 Vilnius🇷🇺 Moscow
Timeline · 2 updates
  1. identified Apr 29, 2026, 04:30 AM UTC

    Status: Identified The cause of the issue has been identified. Our team is now working on implementing a solution. We expect to have a resolution soon and will keep you updated on our progress. Affected components 🇪🇸 Madrid (Partial outage) 🇳🇴 Oslo (Partial outage) 🇰🇷 Seoul (Partial outage) 🇩🇰 Copenhagen (Partial outage) 🇩🇪 Frankfurt (Partial outage) 🇮🇳 Bangalore (Partial outage) 🇿🇦 Johannesburg (Partial outage) 🇭🇰 Hong Kong (Partial outage) 🇺🇸 New York (Partial outage) 🇨🇭 Zurich (Partial outage) 🇦🇺 Sydney (Partial outage) 🇨🇿 Prague (Partial outage) 🇺🇸 Los Angeles (Partial outage) 🇷🇴 Bucharest (Partial outage) 🇨🇴 Bogota (Partial outage) 🇨🇦 Toronto (Partial outage) 🇭🇺 Budapest (Partial outage) 🇺🇸 Miami (Partial outage) 🇺🇸 San Jose (Partial outage) 🇧🇷 Sao Paulo (Partial outage) 🇳🇱 Amsterdam (Partial outage) 🇺🇦 Kyiv (Partial outage) 🇸🇬 Singapore (Partial outage) 🇧🇪 Brussels (Partial outage) 🇧🇬 Sofia (Partial outage) 🇭🇷 Zagreb (Partial outage) 🇦🇷 Buenos Aires (Partial outage) 🇫🇷 Paris (Partial outage) 🇸🇪 Stockholm (Partial outage) 🇬🇷 Athens (Partial outage) 🇵🇹 Lisbon (Partial outage) 🇦🇪 Fujairah (Partial outage) 🇸🇰 Bratislava (Partial outage) 🇰🇿 Almaty (Partial outage) 🇫🇮 Oulu (Partial outage) 🇹🇷 Istanbul (Partial outage) 🇩🇪 Berlin (Partial outage) 🇦🇹 Vienna (Partial outage) 🇺🇸 Houston (Partial outage) 🇬🇧 London (Partial outage) 🇷🇺 Moscow (Partial outage) 🇮🇹 Milan (Partial outage) 🇮🇪 Dublin (Partial outage) 🇲🇾 Kuala Lumpur (Partial outage) 🇵🇱 Warsaw (Partial outage) 🇯🇵 Tokyo (Partial outage) 🇮🇱 Tel Aviv (Partial outage) 🇲🇽 Queretaro (Partial outage) 🇵🇪 Lima (Partial outage) 🇱🇹 Vilnius (Partial outage)

  2. resolved Apr 29, 2026, 08:39 AM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process. Affected components 🇩🇰 Copenhagen (Operational) 🇭🇰 Hong Kong (Operational) 🇺🇸 New York (Operational) 🇪🇸 Madrid (Operational) 🇨🇭 Zurich (Operational) 🇲🇾 Kuala Lumpur (Operational) 🇵🇹 Lisbon (Operational) 🇺🇸 Miami (Operational) 🇬🇧 London (Operational) 🇰🇿 Almaty (Operational) 🇮🇹 Milan (Operational) 🇨🇿 Prague (Operational) 🇳🇴 Oslo (Operational) 🇭🇺 Budapest (Operational) 🇰🇷 Seoul (Operational) 🇺🇦 Kyiv (Operational) 🇧🇷 Sao Paulo (Operational) 🇷🇺 Moscow (Operational) 🇬🇷 Athens (Operational) 🇧🇬 Sofia (Operational) 🇮🇳 Bangalore (Operational) 🇦🇷 Buenos Aires (Operational) 🇫🇷 Paris (Operational) 🇯🇵 Tokyo (Operational) 🇮🇱 Tel Aviv (Operational) 🇩🇪 Frankfurt (Operational) 🇧🇪 Brussels (Operational) 🇨🇴 Bogota (Operational) 🇫🇮 Oulu (Operational) 🇺🇸 Los Angeles (Operational) 🇲🇽 Queretaro (Operational) 🇨🇦 Toronto (Operational) 🇮🇪 Dublin (Operational) 🇺🇸 Houston (Operational) 🇭🇷 Zagreb (Operational) 🇿🇦 Johannesburg (Operational) 🇷🇴 Bucharest (Operational) 🇵🇪 Lima (Operational) 🇩🇪 Berlin (Operational) 🇦🇪 Fujairah (Operational) 🇸🇰 Bratislava (Operational) 🇳🇱 Amsterdam (Operational) 🇵🇱 Warsaw (Operational) 🇹🇷 Istanbul (Operational) 🇸🇬 Singapore (Operational) 🇦🇹 Vienna (Operational) 🇺🇸 San Jose (Operational) 🇱🇹 Vilnius (Operational) 🇸🇪 Stockholm (Operational) 🇦🇺 Sydney (Operational)

Read the full incident report →

Minor April 17, 2026

Problem with V2Ray Subscription

Detected by Pingoru
Apr 17, 2026, 10:16 AM UTC
Resolved
Apr 17, 2026, 10:16 AM UTC
Duration
Timeline · 2 updates
  1. identified Apr 17, 2026, 09:16 AM UTC

    Status: Identified The cause of the issue has been identified. Our team is now working on implementing a solution. We expect to have a resolution soon and will keep you updated on our progress.

  2. resolved Apr 17, 2026, 10:16 AM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process.

Read the full incident report →

Minor April 12, 2026

There are problems with DNS resolvers on the location. Service is partially unavailable.

Detected by Pingoru
Apr 12, 2026, 01:20 PM UTC
Resolved
Apr 12, 2026, 01:20 PM UTC
Duration
Affected: 🇳🇱 Amsterdam
Timeline · 2 updates
  1. investigating Apr 12, 2026, 12:29 PM UTC

    Status: Investigating We are currently investigating an issue. Our team is actively working to identify the root cause, and we’ll provide updates as soon as we have more information. Thank you for your patience and understanding. Affected components 🇳🇱 Amsterdam (Partial outage)

  2. resolved Apr 12, 2026, 01:20 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process. Affected components 🇳🇱 Amsterdam (Operational)

Read the full incident report →

Minor April 3, 2026

VPN Access Issue for New Users

Detected by Pingoru
Apr 03, 2026, 12:30 PM UTC
Resolved
Apr 03, 2026, 12:30 PM UTC
Duration
Timeline · 3 updates
  1. identified Apr 03, 2026, 11:04 AM UTC

    Status: Identified New users are currently experiencing issues connecting to VPN. The cause has been identified. Our team is actively implementing a fix. We expect resolution soon and will update this page with progress.

  2. identified Apr 03, 2026, 12:30 PM UTC

    Status: Identified Fixed

  3. resolved Apr 03, 2026, 12:30 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process.

Read the full incident report →

Minor March 30, 2026

Issues – Canada Location

Detected by Pingoru
Mar 30, 2026, 09:03 AM UTC
Resolved
Mar 30, 2026, 09:03 AM UTC
Duration
Affected: 🇨🇦 Toronto
Timeline · 2 updates
  1. identified Mar 30, 2026, 07:11 AM UTC

    Status: Identified The cause of the issue has been identified. Our team is now working on implementing a solution. We expect to have a resolution soon and will keep you updated on our progress. Affected components 🇨🇦 Toronto (Degraded performance)

  2. resolved Mar 30, 2026, 09:03 AM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process. Affected components 🇨🇦 Toronto (Operational)

Read the full incident report →

Minor March 16, 2026

Server availability problem in India.

Detected by Pingoru
Mar 16, 2026, 02:27 PM UTC
Resolved
Mar 16, 2026, 02:27 PM UTC
Duration
Affected: 🇮🇳 Bangalore
Timeline · 3 updates
  1. investigating Mar 16, 2026, 12:42 PM UTC

    Status: Investigating We are currently investigating an issue. Our team is actively working to identify the root cause, and we’ll provide updates as soon as we have more information. Thank you for your patience and understanding. Affected components 🇮🇳 Bangalore (Full outage)

  2. monitoring Mar 16, 2026, 02:02 PM UTC

    Status: Monitoring We have implemented a fix for the issue and are currently monitoring the results to ensure stability. We’ll provide a final update once we’re confident that the issue is fully resolved. Thank you for your patience. Affected components 🇮🇳 Bangalore (Degraded performance)

  3. resolved Mar 16, 2026, 02:27 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process. Affected components 🇮🇳 Bangalore (Operational)

Read the full incident report →

Minor March 11, 2026

Issues with India Location

Detected by Pingoru
Mar 11, 2026, 11:43 AM UTC
Resolved
Mar 11, 2026, 11:43 AM UTC
Duration
Timeline · 2 updates
  1. identified Mar 11, 2026, 10:49 AM UTC

    Status: Identified The cause of the issue has been identified. Our team is now working on implementing a solution. We expect to have a resolution soon and will keep you updated on our progress.

  2. resolved Mar 11, 2026, 11:43 AM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process.

Read the full incident report →

Minor February 27, 2026

Network Issues – Bangalore Location

Detected by Pingoru
Feb 27, 2026, 11:43 PM UTC
Resolved
Feb 27, 2026, 11:43 PM UTC
Duration
Affected: 🇮🇳 Bangalore
Timeline · 4 updates
  1. investigating Feb 27, 2026, 08:29 PM UTC

    Status: Investigating We are currently experiencing network issues affecting connectivity to the Bangalore location. Users may experience packet loss or disconnections. Our team is investigating. We will provide updates as the situation develops. Affected components 🇮🇳 Bangalore (Degraded performance)

  2. identified Feb 27, 2026, 09:19 PM UTC

    Status: Identified We have identified that the current packet loss and high latency affecting India-based services are being caused by an upstream routing issue with Bharti Airtel. Specifically, the disruption is occurring at the international transit level, impacting traffic exiting or entering the Indian network. Our team is now working on implementing a solution. We expect to have a resolution soon and will keep you updated on our progress. Affected components 🇮🇳 Bangalore (Degraded performance)

  3. monitoring Feb 27, 2026, 10:45 PM UTC

    Status: Monitoring We have implemented a fix for the issue and are currently monitoring the results to ensure stability. We’ll provide a final update once we’re confident that the issue is fully resolved. Thank you for your patience. Affected components 🇮🇳 Bangalore (Degraded performance)

  4. resolved Feb 27, 2026, 11:43 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process. Affected components 🇮🇳 Bangalore (Operational)

Read the full incident report →

Minor February 27, 2026

Problem with Site and Service

Detected by Pingoru
Feb 27, 2026, 02:39 PM UTC
Resolved
Feb 27, 2026, 02:39 PM UTC
Duration
Affected: Website
Timeline · 3 updates
  1. identified Feb 27, 2026, 02:03 PM UTC

    Status: Identified We are currently experiencing issues with our websites and services. Some users may encounter difficulties accessing the site or using our services. Our team is actively investigating the problem and working to restore full functionality as soon as possible. We apologize for the inconvenience and will provide updates as the situation develops. Thank you for your patience. Affected components Website (Degraded performance)

  2. monitoring Feb 27, 2026, 02:12 PM UTC

    Status: Monitoring We have implemented a fix for the issue and are currently monitoring the results to ensure stability. We’ll provide a final update once we’re confident that the issue is fully resolved. Thank you for your patience. Affected components Website (Degraded performance)

  3. resolved Feb 27, 2026, 02:39 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process. Affected components Website (Operational)

Read the full incident report →

Minor February 17, 2026

Location degraded.

Detected by Pingoru
Feb 17, 2026, 10:58 AM UTC
Resolved
Feb 17, 2026, 10:58 AM UTC
Duration
Affected: 🇦🇹 Vienna
Timeline · 2 updates
  1. investigating Feb 17, 2026, 10:25 AM UTC

    Status: Investigating We are currently investigating an issue. Our team is actively working to identify the root cause, and we’ll provide updates as soon as we have more information. Thank you for your patience and understanding. Affected components 🇦🇹 Vienna (Full outage)

  2. resolved Feb 17, 2026, 10:58 AM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process. Affected components 🇦🇹 Vienna (Operational)

Read the full incident report →

Minor February 13, 2026

Degraded Performance Incident in Almaty

Detected by Pingoru
Feb 13, 2026, 04:49 PM UTC
Resolved
Feb 13, 2026, 04:49 PM UTC
Duration
Affected: 🇰🇿 Almaty
Timeline · 3 updates
  1. investigating Feb 11, 2026, 09:24 AM UTC

    Status: Investigating We are currently investigating an issue. Our team is actively working to identify the root cause, and we’ll provide updates as soon as we have more information. Thank you for your patience and understanding. Affected components 🇰🇿 Almaty (Degraded performance)

  2. monitoring Feb 12, 2026, 12:18 PM UTC

    Status: Monitoring We have implemented a fix for the issue and are currently monitoring the results to ensure stability. We’ll provide a final update once we’re confident that the issue is fully resolved. Thank you for your patience. Affected components 🇰🇿 Almaty (Operational)

  3. resolved Feb 13, 2026, 04:49 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process. Affected components 🇰🇿 Almaty (Operational)

Read the full incident report →

Minor February 12, 2026

Potential VPN connection issues from Russia // Возможные трудности подключения VPN из России

Detected by Pingoru
Feb 12, 2026, 12:17 PM UTC
Resolved
Feb 12, 2026, 12:17 PM UTC
Duration
Affected: 🇩🇪 Berlin🇮🇹 Milan🇩🇪 Frankfurt🇪🇸 Madrid🇨🇴 Bogota🇮🇪 Dublin🇺🇸 Houston🇳🇴 Oslo🇿🇦 Johannesburg🇰🇿 Almaty🇳🇱 Amsterdam🇬🇷 Athens🇮🇳 Bangalore🇷🇴 Bucharest🇦🇷 Buenos Aires🇲🇾 Kuala Lumpur🇺🇸 Los Angeles🇫🇮 Oulu🇺🇦 Kyiv🇫🇷 Paris🇨🇿 Prague🇲🇽 Queretaro🇧🇷 Sao Paulo🇰🇷 Seoul🇺🇸 San Jose🇸🇬 Singapore🇧🇬 Sofia🇸🇪 Stockholm🇦🇺 Sydney🇯🇵 Tokyo🇺🇸 New York🇵🇪 Lima🇦🇹 Vienna🇵🇱 Warsaw🇭🇷 Zagreb🇨🇭 Zurich🇭🇺 Budapest🇸🇰 Bratislava🇹🇷 Istanbul🇬🇧 London🇺🇸 Miami🇮🇱 Tel Aviv🇧🇪 Brussels🇦🇪 Fujairah🇭🇰 Hong Kong🇵🇹 Lisbon🇨🇦 Toronto🇱🇹 Vilnius🇷🇺 Moscow
Timeline · 6 updates
  1. identified Feb 03, 2026, 12:54 PM UTC

    Status: Identified The cause of the issue has been identified. Our team is now working on implementing a solution. We expect to have a resolution soon and will keep you updated on our progress. Affected components 🇺🇸 New York (Degraded performance) 🇫🇮 Oulu (Degraded performance) 🇯🇵 Tokyo (Degraded performance) 🇨🇿 Prague (Degraded performance) 🇪🇸 Madrid (Degraded performance) 🇳🇱 Amsterdam (Degraded performance) 🇺🇦 Kyiv (Degraded performance) 🇷🇺 Moscow (Degraded performance) 🇸🇪 Stockholm (Degraded performance) 🇩🇪 Frankfurt (Degraded performance) 🇬🇷 Athens (Degraded performance) 🇳🇴 Oslo (Degraded performance) 🇭🇺 Budapest (Degraded performance) 🇿🇦 Johannesburg (Degraded performance) 🇨🇭 Zurich (Degraded performance) 🇺🇸 Miami (Degraded performance) 🇵🇱 Warsaw (Degraded performance) 🇧🇷 Sao Paulo (Degraded performance) 🇫🇷 Paris (Degraded performance) 🇮🇹 Milan (Degraded performance) 🇹🇷 Istanbul (Degraded performance) 🇩🇪 Berlin (Degraded performance) 🇺🇸 Houston (Degraded performance) 🇸🇰 Bratislava (Degraded performance) 🇮🇳 Bangalore (Degraded performance) 🇦🇷 Buenos Aires (Degraded performance) 🇧🇪 Brussels (Degraded performance) 🇨🇴 Bogota (Degraded performance) 🇵🇹 Lisbon (Degraded performance) 🇦🇪 Fujairah (Degraded performance) 🇰🇿 Almaty (Degraded performance) 🇺🇸 Los Angeles (Degraded performance) 🇮🇱 Tel Aviv (Degraded performance) 🇵🇪 Lima (Degraded performance) 🇰🇷 Seoul (Degraded performance) 🇮🇪 Dublin (Degraded performance) 🇺🇸 San Jose (Degraded performance) 🇲🇽 Queretaro (Degraded performance) 🇷🇴 Bucharest (Degraded performance) 🇧🇬 Sofia (Degraded performance) 🇲🇾 Kuala Lumpur (Degraded performance) 🇭🇷 Zagreb (Degraded performance) 🇸🇬 Singapore (Degraded performance) 🇦🇺 Sydney (Degraded performance) 🇨🇦 Toronto (Degraded performance) 🇦🇹 Vienna (Degraded performance) 🇬🇧 London (Degraded performance) 🇱🇹 Vilnius (Degraded performance) 🇭🇰 Hong Kong (Degraded performance)

  2. identified Feb 03, 2026, 01:16 PM UTC

    Status: Identified Если у вас возникли сложности с подключением, используйте приложение V2Ray (Happ) и локации с припиской EXTRA в названии. Мы уже работаем над восстановлением подключения ко всем регионам. Инструкции по подключению: https://blancvpn.cx/ru/help Affected components 🇰🇿 Almaty (Degraded performance) 🇪🇸 Madrid (Degraded performance) 🇨🇭 Zurich (Degraded performance) 🇺🇸 Los Angeles (Degraded performance) 🇹🇷 Istanbul (Degraded performance) 🇬🇷 Athens (Degraded performance) 🇳🇴 Oslo (Degraded performance) 🇵🇱 Warsaw (Degraded performance) 🇭🇰 Hong Kong (Degraded performance) 🇺🇸 New York (Degraded performance) 🇧🇪 Brussels (Degraded performance) 🇵🇪 Lima (Degraded performance) 🇰🇷 Seoul (Degraded performance) 🇮🇱 Tel Aviv (Degraded performance) 🇧🇬 Sofia (Degraded performance) 🇺🇸 Miami (Degraded performance) 🇬🇧 London (Degraded performance) 🇳🇱 Amsterdam (Degraded performance) 🇿🇦 Johannesburg (Degraded performance) 🇱🇹 Vilnius (Degraded performance) 🇷🇺 Moscow (Degraded performance) 🇫🇷 Paris (Degraded performance) 🇯🇵 Tokyo (Degraded performance) 🇭🇺 Budapest (Degraded performance) 🇮🇳 Bangalore (Degraded performance) 🇦🇷 Buenos Aires (Degraded performance) 🇲🇽 Queretaro (Degraded performance) 🇨🇴 Bogota (Degraded performance) 🇩🇪 Berlin (Degraded performance) 🇺🇸 Houston (Degraded performance) 🇦🇪 Fujairah (Degraded performance) 🇫🇮 Oulu (Degraded performance) 🇮🇹 Milan (Degraded performance) 🇸🇪 Stockholm (Degraded performance) 🇸🇬 Singapore (Degraded performance) 🇷🇴 Bucharest (Degraded performance) 🇦🇹 Vienna (Degraded performance) 🇮🇪 Dublin (Degraded performance) 🇲🇾 Kuala Lumpur (Degraded performance) 🇧🇷 Sao Paulo (Degraded performance) 🇨🇿 Prague (Degraded performance) 🇩🇪 Frankfurt (Degraded performance) 🇦🇺 Sydney (Degraded performance) 🇨🇦 Toronto (Degraded performance) 🇸🇰 Bratislava (Degraded performance) 🇺🇸 San Jose (Degraded performance) 🇭🇷 Zagreb (Degraded performance) 🇺🇦 Kyiv (Degraded performance) 🇵🇹 Lisbon (Degraded performance)

  3. identified Feb 03, 2026, 02:52 PM UTC

    Status: Identified Если возникли сложности с подключением, перейдите в раздел Установить в личном кабинете. Выберите ваше устройство > Ключ для сторонних приложений > в параметрах "Локация и протокол" активируйте "Использовать Extra-настройки". К установке: https://blancvpn.app/install Affected components 🇵🇱 Warsaw (Degraded performance) 🇺🇸 Los Angeles (Degraded performance) 🇬🇷 Athens (Degraded performance) 🇵🇪 Lima (Degraded performance) 🇵🇹 Lisbon (Degraded performance) 🇿🇦 Johannesburg (Degraded performance) 🇲🇽 Queretaro (Degraded performance) 🇸🇰 Bratislava (Degraded performance) 🇺🇸 San Jose (Degraded performance) 🇬🇧 London (Degraded performance) 🇮🇳 Bangalore (Degraded performance) 🇦🇷 Buenos Aires (Degraded performance) 🇧🇷 Sao Paulo (Degraded performance) 🇫🇮 Oulu (Degraded performance) 🇮🇹 Milan (Degraded performance) 🇸🇪 Stockholm (Degraded performance) 🇰🇷 Seoul (Degraded performance) 🇺🇦 Kyiv (Degraded performance) 🇫🇷 Paris (Degraded performance) 🇨🇿 Prague (Degraded performance) 🇦🇺 Sydney (Degraded performance) 🇳🇴 Oslo (Degraded performance) 🇦🇹 Vienna (Degraded performance) 🇧🇬 Sofia (Degraded performance) 🇺🇸 Miami (Degraded performance) 🇳🇱 Amsterdam (Degraded performance) 🇩🇪 Frankfurt (Degraded performance) 🇸🇬 Singapore (Degraded performance) 🇧🇪 Brussels (Degraded performance) 🇨🇦 Toronto (Degraded performance) 🇮🇪 Dublin (Degraded performance) 🇱🇹 Vilnius (Degraded performance) 🇰🇿 Almaty (Degraded performance) 🇭🇰 Hong Kong (Degraded performance) 🇺🇸 New York (Degraded performance) 🇷🇺 Moscow (Degraded performance) 🇮🇱 Tel Aviv (Degraded performance) 🇨🇴 Bogota (Degraded performance) 🇭🇺 Budapest (Degraded performance) 🇯🇵 Tokyo (Degraded performance) 🇷🇴 Bucharest (Degraded performance) 🇩🇪 Berlin (Degraded performance) 🇲🇾 Kuala Lumpur (Degraded performance) 🇦🇪 Fujairah (Degraded performance) 🇭🇷 Zagreb (Degraded performance) 🇪🇸 Madrid (Degraded performance) 🇨🇭 Zurich (Degraded performance) 🇹🇷 Istanbul (Degraded performance) 🇺🇸 Houston (Degraded performance)

  4. identified Feb 03, 2026, 06:02 PM UTC

    Status: Identified Мы знаем, что некоторые пользователи столкнулись со сбоями при подключении, и уже подготовили решение. Если у вас всё работает — отлично, ничего делать не нужно. Если подключиться не получается, потребуется настроить V2Ray вручную: 1. Перейдите в раздел Установить: https://blanc.link/7Ao4Zx2 в личном кабинете 2. В параметрах «Локация и протокол» проверьте, что у вас включен параметр «Использовать Extra-настройки». Если нет, то включите его 3. Если вы уже используете V2Ray (Приложения Happ, Karing, V2box, V2rayN и др.), то вам нужно обновить подписку в приложении. Для обновления подписки нажмите на “три точки”, а затем выберите “Обновить подписку” 4. Если вы подключаете V2Ray впервые, воспользуйтесь инструкцией по установке: https://blanc.link/58ESFJp Для приложения BlancVPN мы ещё работаем над решением и расскажем, когда оно будет готово. Affected components 🇺🇸 Los Angeles (Degraded performance) 🇮🇱 Tel Aviv (Degraded performance) 🇬🇷 Athens (Degraded performance) 🇵🇹 Lisbon (Degraded performance) 🇫🇷 Paris (Degraded performance) 🇭🇺 Budapest (Degraded performance) 🇺🇸 Miami (Degraded performance) 🇲🇽 Queretaro (Degraded performance) 🇷🇴 Bucharest (Degraded performance) 🇨🇴 Bogota (Degraded performance) 🇰🇷 Seoul (Degraded performance) 🇧🇬 Sofia (Degraded performance) 🇸🇰 Bratislava (Degraded performance) 🇮🇳 Bangalore (Degraded performance) 🇿🇦 Johannesburg (Degraded performance) 🇭🇰 Hong Kong (Degraded performance) 🇫🇮 Oulu (Degraded performance) 🇸🇬 Singapore (Degraded performance) 🇦🇪 Fujairah (Degraded performance) 🇭🇷 Zagreb (Degraded performance) 🇵🇱 Warsaw (Degraded performance) 🇮🇹 Milan (Degraded performance) 🇨🇿 Prague (Degraded performance) 🇪🇸 Madrid (Degraded performance) 🇧🇪 Brussels (Degraded performance) 🇦🇺 Sydney (Degraded performance) 🇵🇪 Lima (Degraded performance) 🇩🇪 Berlin (Degraded performance) 🇬🇧 London (Degraded performance) 🇺🇦 Kyiv (Degraded performance) 🇰🇿 Almaty (Degraded performance) 🇷🇺 Moscow (Degraded performance) 🇸🇪 Stockholm (Degraded performance) 🇹🇷 Istanbul (Degraded performance) 🇨🇦 Toronto (Degraded performance) 🇮🇪 Dublin (Degraded performance) 🇳🇱 Amsterdam (Degraded performance) 🇺🇸 New York (Degraded performance) 🇧🇷 Sao Paulo (Degraded performance) 🇯🇵 Tokyo (Degraded performance) 🇨🇭 Zurich (Degraded performance) 🇩🇪 Frankfurt (Degraded performance) 🇳🇴 Oslo (Degraded performance) 🇦🇹 Vienna (Degraded performance) 🇱🇹 Vilnius (Degraded performance) 🇲🇾 Kuala Lumpur (Degraded performance) 🇺🇸 Houston (Degraded performance) 🇺🇸 San Jose (Degraded performance) 🇦🇷 Buenos Aires (Degraded performance)

  5. identified Feb 04, 2026, 04:28 AM UTC

    Status: Identified Мы восстановили стабильную работу большинства VPN-локаций без дополнительных настроек. Команда поддержки сейчас перегружена — пожалуйста, не пишите, если проблема решилась. Если все же понадобится помощь, мы на связи. Мы обязательно ответим, но это займет больше времени, чем обычно. Affected components 🇧🇷 Sao Paulo (Operational) 🇨🇦 Toronto (Operational) 🇲🇾 Kuala Lumpur (Operational) 🇦🇪 Fujairah (Operational) 🇺🇦 Kyiv (Operational) 🇨🇿 Prague (Operational) 🇷🇴 Bucharest (Operational) 🇧🇪 Brussels (Operational) 🇦🇺 Sydney (Operational) 🇨🇴 Bogota (Operational) 🇵🇪 Lima (Operational) 🇺🇸 Miami (Operational) 🇵🇱 Warsaw (Operational) 🇮🇹 Milan (Operational) 🇺🇸 Los Angeles (Operational) 🇭🇺 Budapest (Operational) 🇮🇳 Bangalore (Operational) 🇨🇭 Zurich (Operational) 🇵🇹 Lisbon (Operational) 🇺🇸 San Jose (Operational) 🇩🇪 Frankfurt (Operational) 🇲🇽 Queretaro (Operational) 🇬🇷 Athens (Operational) 🇬🇧 London (Operational) 🇳🇱 Amsterdam (Operational) 🇱🇹 Vilnius (Operational) 🇭🇰 Hong Kong (Operational) 🇦🇷 Buenos Aires (Degraded performance) 🇺🇸 New York (Operational) 🇷🇺 Moscow (Operational) 🇫🇷 Paris (Operational) 🇯🇵 Tokyo (Operational) 🇸🇪 Stockholm (Operational) 🇮🇱 Tel Aviv (Degraded performance) 🇳🇴 Oslo (Operational) 🇰🇷 Seoul (Operational) 🇫🇮 Oulu (Operational) 🇩🇪 Berlin (Operational) 🇮🇪 Dublin (Operational) 🇺🇸 Houston (Operational) 🇸🇰 Bratislava (Operational) 🇪🇸 Madrid (Operational) 🇦🇹 Vienna (Operational) 🇧🇬 Sofia (Operational) 🇭🇷 Zagreb (Operational) 🇹🇷 Istanbul (Operational) 🇸🇬 Singapore (Operational) 🇿🇦 Johannesburg (Operational) 🇰🇿 Almaty (Operational)

  6. resolved Feb 12, 2026, 12:17 PM UTC

    Status: Resolved The issue has been fully resolved, and all systems are now operating as expected. We apologize for any disruption this may have caused and appreciate your understanding throughout this process. Affected components 🇷🇺 Moscow (Operational) 🇩🇪 Frankfurt (Operational) 🇺🇸 San Jose (Operational) 🇰🇿 Almaty (Operational) 🇮🇹 Milan (Operational) 🇹🇷 Istanbul (Operational) 🇭🇺 Budapest (Operational) 🇩🇪 Berlin (Operational) 🇮🇳 Bangalore (Operational) 🇿🇦 Johannesburg (Operational) 🇺🇸 New York (Operational) 🇧🇷 Sao Paulo (Operational) 🇬🇷 Athens (Operational) 🇳🇴 Oslo (Operational) 🇲🇾 Kuala Lumpur (Operational) 🇸🇰 Bratislava (Operational) 🇭🇰 Hong Kong (Operational) 🇫🇷 Paris (Operational) 🇪🇸 Madrid (Operational) 🇷🇴 Bucharest (Operational) 🇰🇷 Seoul (Operational) 🇦🇷 Buenos Aires (Operational) 🇯🇵 Tokyo (Operational) 🇺🇸 Los Angeles (Operational) 🇮🇱 Tel Aviv (Operational) 🇸🇬 Singapore (Operational) 🇦🇹 Vienna (Operational) 🇳🇱 Amsterdam (Operational) 🇨🇿 Prague (Operational) 🇸🇪 Stockholm (Operational) 🇦🇺 Sydney (Operational) 🇵🇪 Lima (Operational) 🇮🇪 Dublin (Operational) 🇧🇬 Sofia (Operational) 🇭🇷 Zagreb (Operational) 🇬🇧 London (Operational) 🇫🇮 Oulu (Operational) 🇲🇽 Queretaro (Operational) 🇵🇹 Lisbon (Operational) 🇦🇪 Fujairah (Operational) 🇵🇱 Warsaw (Operational) 🇺🇦 Kyiv (Operational) 🇨🇭 Zurich (Operational) 🇧🇪 Brussels (Operational) 🇨🇴 Bogota (Operational) 🇨🇦 Toronto (Operational) 🇺🇸 Houston (Operational) 🇺🇸 Miami (Operational) 🇱🇹 Vilnius (Operational)

Read the full incident report →

Looking to track BlancVPN downtime and outages?

Pingoru polls BlancVPN's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when BlancVPN reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track BlancVPN alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring BlancVPN for free

5 free monitors · No credit card required