BlancVPN Outage History

BlancVPN had 35 outages in the last 2 years totaling 1h 4m of downtime — averaging 1.4 incidents per month.

There were 35 BlancVPN outages since August 26, 2025 totaling 1h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://blancvpnstatus.com

Minor June 6, 2026

Maintenance in Los Angeles

Detected by Pingoru: Jun 06, 2026, 03:09 PM UTC
Resolved: Jun 06, 2026, 03:09 PM UTC
Duration: —

Affected: 🇺🇸 Los Angeles

Timeline · 4 updates

identified Jun 06, 2026, 10:14 AM UTC

Status: Identified We have maintenance. During this period, you may experience limited functionality or brief interruptions. We’re working to complete this maintenance as quickly and smoothly as possible. Thank you for your understanding. Affected components 🇺🇸 Los Angeles (Full outage)
resolved Jun 06, 2026, 10:45 AM UTC

Status: Resolved The scheduled maintenance has been completed successfully. All systems are now fully operational. Thank you for your patience during this maintenance window. Affected components 🇺🇸 Los Angeles (Operational)
monitoring Jun 06, 2026, 11:15 AM UTC

Status: Monitoring Our provider has informed us that additional maintenance work is still ongoing in the Los Angeles location. This is a continuation of the earlier maintenance event. During this period, you may again experience limited connectivity or brief interruptions. We will keep you updated as soon as the provider confirms completion. Thank you for your continued patience and understanding. Affected components 🇺🇸 Los Angeles (Full outage)
resolved Jun 06, 2026, 03:09 PM UTC

Status: Resolved The scheduled maintenance has been completed successfully. All systems are now fully operational. Thank you for your patience during this maintenance window. Affected components 🇺🇸 Los Angeles (Operational)

Read the full incident report →

Minor May 30, 2026

Problem with the Vilnius location

Detected by Pingoru: May 30, 2026, 07:46 PM UTC
Resolved: May 30, 2026, 07:46 PM UTC
Duration: —

Affected: 🇱🇹 Vilnius

Timeline · 3 updates

identified May 30, 2026, 07:34 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 🇱🇹 Vilnius (Degraded performance)
monitoring May 30, 2026, 07:37 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 🇱🇹 Vilnius (Degraded performance)
resolved May 30, 2026, 07:46 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 🇱🇹 Vilnius (Operational)

Read the full incident report →

Minor May 28, 2026

VPN Connectivity Issues from Russia

Detected by Pingoru: May 28, 2026, 10:20 PM UTC
Resolved: May 28, 2026, 10:20 PM 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 · 4 updates

Read the full incident report →

Minor May 16, 2026

Elevated VPN connection issues with the Lithuania location

Detected by Pingoru: May 16, 2026, 05:34 PM UTC
Resolved: May 16, 2026, 05:34 PM UTC
Duration: —

Affected: 🇱🇹 Vilnius

Timeline · 2 updates

identified May 16, 2026, 05:19 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 🇱🇹 Vilnius (Full outage)
resolved May 16, 2026, 05:34 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 🇱🇹 Vilnius (Operational)

Read the full incident report →

Minor May 13, 2026

Problem with the India location

Detected by Pingoru: May 13, 2026, 08:27 AM UTC
Resolved: May 13, 2026, 08:27 AM UTC
Duration: —

Affected: 🇮🇳 Bangalore

Timeline · 2 updates

identified May 12, 2026, 04:19 PM UTC

Status: Identified We are experiencing a network-related problem specific to the India region. Our team is actively working to resolve the issue and restore normal connectivity as soon as possible. Updates will be provided as progress is made. Affected components 🇮🇳 Bangalore (Partial outage)
resolved May 13, 2026, 08:27 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 🇮🇳 Bangalore (Operational)

Read the full incident report →

Minor May 7, 2026

Payments from Russia are temporarily unavailable

Detected by Pingoru: May 07, 2026, 06:39 PM UTC
Resolved: May 07, 2026, 06:39 PM UTC
Duration: —

Timeline · 1 update

resolved May 07, 2026, 06: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.

Read the full incident report →

Minor May 7, 2026

Problem with the Querétaro location

Detected by Pingoru: May 07, 2026, 07:50 AM UTC
Resolved: May 07, 2026, 07:50 AM UTC
Duration: —

Affected: 🇲🇽 Queretaro

Timeline · 3 updates

identified May 07, 2026, 07:02 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.
identified May 07, 2026, 07:04 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 🇲🇽 Queretaro (Full outage)
resolved May 07, 2026, 07:50 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 🇲🇽 Queretaro (Operational)

Read the full incident report →

Minor May 6, 2026

Subscription Issues

Detected by Pingoru: May 06, 2026, 04:48 PM UTC
Resolved: May 06, 2026, 04:48 PM UTC
Duration: —

Timeline · 2 updates

identified May 06, 2026, 04:16 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.
resolved May 06, 2026, 04:48 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 May 6, 2026

Delays in delivery of login code emails

Detected by Pingoru: May 06, 2026, 09:14 AM UTC
Resolved: May 06, 2026, 09:14 AM UTC
Duration: —

Affected: Website

Timeline · 2 updates

investigating May 05, 2026, 10:36 PM UTC

Status: Investigating We are currently experiencing delays in the delivery of email verification codes used for login to your account dashboard and mobile app. Users may encounter longer wait times (up to several minutes) before receiving these emails. 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 Website (Degraded performance)
resolved May 06, 2026, 09:14 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 Website (Operational)

Read the full incident report →

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: —

Timeline · 2 updates

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

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.
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

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)
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

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.
identified Apr 03, 2026, 12:30 PM UTC

Status: Identified Fixed
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

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)
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

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)
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)
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

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.
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

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)
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)
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)
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

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)
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)
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

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)
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

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)
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)
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

Read the full incident report →

Minor December 31, 2025