What is BlancVPN's uptime?

Over the last 90 days, BlancVPN reported 85.56% uptime on its official status page. That figure is calculated from the public incident timeline at https://blancvpnstatus.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see BlancVPN's uptime history rolling forward in real time.

Has BlancVPN had outages in 2026?

Yes — BlancVPN has had 7 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last BlancVPN outage?

The most recent BlancVPN incident was "Connectivity Issues with Amneziawg, WireGuard, and OpenVPN", which started on August 18, 2026 and was resolved on August 18, 2026. Pingoru captured this directly from https://blancvpnstatus.com. See the full incident card above for affected components and the update timeline.

How often does BlancVPN have outages?

Based on the last 90 days, BlancVPN averages 2.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is BlancVPN's status page?

BlancVPN's official status page is https://blancvpnstatus.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is BlancVPN down right now?

BlancVPN is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment BlancVPN reports a change. Current status is based on 0 tracked services.

How does Pingoru know if BlancVPN is down?

We read https://blancvpnstatus.com directly, using BlancVPN's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.

Where can I get notified when BlancVPN has an outage?

Create a free Pingoru account and add BlancVPN as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

BlancVPN's status page says the service is up, but I'm having issues — what's wrong?

Three common reasons: • A real BlancVPN incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real BlancVPN issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official BlancVPN status?

We use BlancVPN's own status page at https://blancvpnstatus.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Partial Outage" mean?

BlancVPN has a partial outage — one or more components are down, but the rest of the service is operational.

Is BlancVPN down?

Last checked 10m ago

Current status

BlancVPN is having a partial outage

9 active incidents: Elevated VPN connection failures / Повышенное число неудачн…, Ongoing disruption across VPN locations, apps, API, website… · +7 more

Get alerts when BlancVPN breaks → View BlancVPN outage history →

Free · no credit card

Official status page: https://blancvpnstatus.com · Polled every 5 minutes · 0 components tracked

BlancVPN is reporting a partial outage right now (last checked 10m ago). Some components are affected; others remain operational.

Real-time BlancVPN status, recent outages, and incident history — pulled directly from BlancVPN's official status page at https://blancvpnstatus.com every 5 minutes. Pingoru tracks 0 BlancVPN services and has captured 16 incidents in the last 90 days (85.56% uptime). Get email, Slack, Discord, or webhook alerts the moment BlancVPN reports a new incident — free for 5 monitors, no credit card.

Users who monitor BlancVPN also follow these Security services:

Keeper View all 6,000+ providers

BlancVPN uptime 85.56% uptime · past 90 days

Mon Wed Fri

JunJulAugSep

Less More

Active incidents 9

Elevated VPN connection failures / Повышенное число неудачных подключений к VPN

Ongoing ● 3d 18h

Started Sep 10, 2026, 08:42 PM UTC
Timeline · 1 update
- monitoring · Sep 01, 2026, 05:32 AM UTC
  
  Status: Monitoring We are currently observing an elevated rate of failed VPN connection attempts affecting some users. VPN service remains operational, and most users can continue connecting through the BlancVPN app as usual. If you use a third-party VPN client and experience connection issues, please refresh your VPN subscription before reconnecting. We are monitoring the situation and working to maintain stable connectivity. Мы наблюдаем повышенное число неудачных попыток подключения к VPN у части пользователей. VPN-сервис продолжает работать, и большинство пользователей могут подключаться через приложение BlancVPN в обычном режиме. Если вы используете сторонний VPN-клиент и испытываете проблемы с подключением, пожалуйста, обновите VPN-подписку перед повторным подключением. Мы продолжаем следить за ситуацией и работаем над поддержанием стабильного подключения.
Latest: Status: Monitoring We are currently observing an elevated rate of failed VPN connection attempts affecting some users. VPN service remains operational, and most users can continue …
Ongoing disruption across VPN locations, apps, API, websites and bot

Ongoing ● 13d 9h

Started Sep 01, 2026, 05:33 AM UTC
Timeline · 1 update
- monitoring · Aug 31, 2026, 03:31 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 🇦🇪 Fujairah (Partial outage) 🇳🇬 Lagos (Partial outage) 🇷🇺 Moscow (Partial outage) 🇸🇪 Stockholm (Partial outage) 🇬🇷 Athens (Partial outage) 🇷🇴 Bucharest (Partial outage) 🇭🇺 Budapest (Partial outage) 🇸🇰 Bratislava (Partial outage) 🇳🇱 Amsterdam (Partial outage) 🇱🇹 Vilnius (Partial outage) 🇧🇷 Sao Paulo (Partial outage) 🇩🇪 Frankfurt (Partial outage) 🇵🇪 Lima (Partial outage) 🇦🇹 Vienna (Partial outage) 🇺🇸 San Jose (Partial outage) 🇵🇱 Warsaw (Partial outage) 🇰🇿 Almaty (Partial outage) 🇦🇷 Buenos Aires (Partial outage) 🇨🇭 Zurich (Partial outage) 🇰🇷 Seoul (Partial outage) 🇵🇹 Lisbon (Partial outage) 🇭🇷 Zagreb (Partial outage) 🇿🇦 Johannesburg (Partial outage) 🇮🇱 Tel Aviv (Partial outage) 🇧🇪 Brussels (Partial outage) 🇮🇪 Dublin (Partial outage) 🇺🇸 Miami (Partial outage) 🇩🇰 Copenhagen (Partial outage) 🇭🇰 Hong Kong (Partial outage) 🇫🇷 Paris (Partial outage) 🇯🇵 Tokyo (Partial outage) 🇮🇹 Milan (Partial outage) 🇨🇿 Prague (Partial outage) 🇺🇸 Los Angeles (Partial outage) 🇹🇷 Istanbul (Partial outage) 🇨🇴 Bogota (Partial outage) Website (Partial outage) Telegram Bot (Partial outage) 🇺🇸 New York (Partial outage) 🇸🇬 Singapore (Partial outage) 🇳🇴 Oslo (Partial outage) 🇺🇸 Houston (Partial outage) 🇲🇽 Queretaro (Partial outage) 🇬🇧 London (Partial outage) 🇫🇮 Oulu (Partial outage) 🇪🇸 Madrid (Partial outage) 🇦🇺 Sydney (Partial outage) 🇨🇦 Toronto (Partial outage) 🇲🇾 Kuala Lumpur (Partial outage) 🇺🇦 Kyiv (Partial outage) 🇩🇪 Berlin (Partial outage) 🇧🇬 Sofia (Partial outage)
Latest: 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 informatio…
Connectivity Issues with Amneziawg, WireGuard, and OpenVPN

Ongoing ● 26d 18h

Started Aug 18, 2026, 08:38 PM UTC
Timeline · 1 update
- monitoring · Aug 18, 2026, 08:38 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 🇵🇪 Lima (Operational) 🇧🇬 Sofia (Operational) 🇺🇸 Miami (Operational) 🇸🇰 Bratislava (Operational) 🇩🇰 Copenhagen (Operational) 🇳🇬 Lagos (Operational) 🇳🇱 Amsterdam (Operational) 🇰🇿 Almaty (Operational) 🇷🇺 Moscow (Operational) 🇯🇵 Tokyo (Operational) 🇦🇺 Sydney (Operational) 🇵🇹 Lisbon (Operational) 🇦🇪 Fujairah (Operational) 🇺🇸 San Jose (Operational) 🇸🇪 Stockholm (Operational) 🇩🇪 Berlin (Operational) 🇵🇱 Warsaw (Operational) 🇩🇪 Frankfurt (Operational) 🇸🇬 Singapore (Operational) 🇰🇷 Seoul (Operational) 🇭🇷 Zagreb (Operational) 🇿🇦 Johannesburg (Operational) 🇭🇰 Hong Kong (Operational) 🇺🇸 Los Angeles (Operational) 🇧🇪 Brussels (Operational) 🇺🇦 Kyiv (Operational) 🇧🇷 Sao Paulo (Operational) 🇨🇿 Prague (Operational) 🇪🇸 Madrid (Operational) 🇨🇭 Zurich (Operational) 🇮🇱 Tel Aviv (Operational) 🇲🇽 Queretaro (Operational) 🇷🇴 Bucharest (Operational) 🇱🇹 Vilnius (Operational) 🇦🇷 Buenos Aires (Operational) 🇺🇸 New York (Operational) 🇫🇮 Oulu (Operational) 🇨🇴 Bogota (Operational) 🇳🇴 Oslo (Operational) 🇨🇦 Toronto (Operational) 🇦🇹 Vienna (Operational) 🇬🇧 London (Operational) 🇫🇷 Paris (Operational) 🇮🇹 Milan (Operational) 🇹🇷 Istanbul (Operational) 🇭🇺 Budapest (Operational) 🇮🇪 Dublin (Operational) 🇲🇾 Kuala Lumpur (Operational) 🇺🇸 Houston (Operational) 🇬🇷 Athens (Operational)
Latest: 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 understa…
Problem with Buenos Aires

Ongoing ● 60d 4h

Started Jul 16, 2026, 10:46 AM UTC
Timeline · 1 update
- monitoring · Jul 16, 2026, 10:46 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 🇦🇷 Buenos Aires (Operational)
Latest: 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 understa…
Ongoing outage in Zürich

Ongoing ● 63d 6h

Started Jul 13, 2026, 08:45 AM UTC
Timeline · 1 update
- monitoring · Jul 13, 2026, 08:45 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 🇨🇭 Zurich (Operational)
Latest: 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 understa…

+4 more ongoing incidents — sign up free to track them all.

Recent outages & incidents

Past 90 days

Connectivity Issues with Amneziawg, WireGuard, and OpenVPN

Resolved —

Started Aug 18, 2026, 08:38 PM UTC · Resolved Aug 18, 2026, 08:38 PM UTC

🇩🇪 Berlin🇮🇹 Milan🇩🇪 Frankfurt🇪🇸 Madrid🇨🇴 Bogota🇮🇪 Dublin🇺🇸 Houston🇳🇴 Oslo🇿🇦 Johannesburg🇰🇿 Almaty
Timeline · 3 updates
- identified · Aug 18, 2026, 05:49 PM UTC
  
  Status: Identified Due to the unavailability of the ММТС-9 server facility operated by a Moscow telecommunications provider, disruptions in the VPN protocols Amneziawg, WireGuard, and OpenVPN may occur. Из-за недоступности серверной площадки ММТС-9 московского оператора связи могут наблюдаться сбои в работе VPN-протоколов Amneziawg, WireGuard и OpenVPN. Affected components 🇮🇪 Dublin (Degraded performance) 🇺🇸 Houston (Degraded performance) 🇺🇸 San Jose (Degraded performance) 🇫🇮 Oulu (Degraded performance) 🇧🇪 Brussels (Degraded performance) 🇿🇦 Johannesburg (Degraded performance) 🇦🇷 Buenos Aires (Degraded performance) 🇮🇹 Milan (Degraded performance) 🇸🇪 Stockholm (Degraded performance) 🇸🇬 Singapore (Degraded performance) 🇲🇽 Queretaro (Degraded performance) 🇬🇷 Athens (Degraded performance) 🇦🇺 Sydney (Degraded performance) 🇨🇭 Zurich (Degraded performance) 🇦🇪 Fujairah (Degraded performance) 🇭🇷 Zagreb (Degraded performance) 🇩🇰 Copenhagen (Degraded performance) 🇳🇬 Lagos (Degraded performance) 🇬🇧 London (Degraded performance) 🇵🇱 Warsaw (Degraded performance) 🇱🇹 Vilnius (Degraded performance) 🇫🇷 Paris (Degraded performance) 🇨🇿 Prague (Degraded performance) 🇺🇸 Los Angeles (Degraded performance) 🇹🇷 Istanbul (Degraded performance) 🇨🇦 Toronto (Degraded performance) 🇰🇿 Almaty (Degraded performance) 🇷🇺 Moscow (Degraded performance) 🇯🇵 Tokyo (Degraded performance) 🇪🇸 Madrid (Degraded performance) 🇩🇪 Frankfurt (Degraded performance) 🇷🇴 Bucharest (Degraded performance) 🇰🇷 Seoul (Degraded performance) 🇩🇪 Berlin (Degraded performance) 🇳🇱 Amsterdam (Degraded performance) 🇺🇦 Kyiv (Degraded performance) 🇧🇷 Sao Paulo (Degraded performance) 🇮🇱 Tel Aviv (Degraded performance) 🇨🇴 Bogota (Degraded performance) 🇵🇪 Lima (Degraded performance) 🇳🇴 Oslo (Degraded performance) 🇦🇹 Vienna (Degraded performance) 🇭🇰 Hong Kong (Degraded performance) 🇧🇬 Sofia (Degraded performance) 🇲🇾 Kuala Lumpur (Degraded performance) 🇵🇹 Lisbon (Degraded performance) 🇺🇸 Miami (Degraded performance) 🇸🇰 Bratislava (Degraded performance) 🇺🇸 New York (Degraded performance) 🇭🇺 Budapest (Degraded performance)
- monitoring · Aug 18, 2026, 07:25 PM UTC
  
  Status: Monitoring Restoration of service is being observed at the MMTS-9 server facility. Operation of Amneziawg, WireGuard, and OpenVPN has been restored. Наблюдаем восстановление работы площадки ММТС9. Работа Amneziawg, WireGuard и OpenVPN восстановлена. Affected components 🇧🇬 Sofia (Operational) 🇩🇰 Copenhagen (Operational) 🇳🇱 Amsterdam (Operational) 🇭🇰 Hong Kong (Operational) 🇯🇵 Tokyo (Operational) 🇪🇸 Madrid (Operational) 🇹🇷 Istanbul (Operational) 🇩🇪 Frankfurt (Operational) 🇳🇴 Oslo (Operational) 🇮🇪 Dublin (Operational) 🇸🇬 Singapore (Operational) 🇰🇿 Almaty (Operational) 🇺🇸 New York (Operational) 🇫🇮 Oulu (Operational) 🇮🇹 Milan (Operational) 🇩🇪 Berlin (Operational) 🇺🇸 Miami (Operational) 🇦🇪 Fujairah (Operational) 🇱🇹 Vilnius (Operational) 🇦🇷 Buenos Aires (Operational) 🇨🇿 Prague (Operational) 🇨🇴 Bogota (Operational) 🇺🇸 Houston (Operational) 🇺🇸 San Jose (Operational) 🇮🇱 Tel Aviv (Operational) 🇲🇽 Queretaro (Operational) 🇦🇹 Vienna (Operational) 🇭🇷 Zagreb (Operational) 🇵🇱 Warsaw (Operational) 🇨🇭 Zurich (Operational) 🇧🇪 Brussels (Operational) 🇰🇷 Seoul (Operational) 🇵🇹 Lisbon (Operational) 🇳🇬 Lagos (Operational) 🇬🇷 Athens (Operational) 🇷🇴 Bucharest (Operational) 🇬🇧 London (Operational) 🇿🇦 Johannesburg (Operational) 🇷🇺 Moscow (Operational) 🇫🇷 Paris (Operational) 🇲🇾 Kuala Lumpur (Operational) 🇺🇦 Kyiv (Operational) 🇧🇷 Sao Paulo (Operational) 🇦🇺 Sydney (Operational) 🇵🇪 Lima (Operational) 🇨🇦 Toronto (Operational) 🇭🇺 Budapest (Operational) 🇸🇰 Bratislava (Operational) 🇸🇪 Stockholm (Operational) 🇺🇸 Los Angeles (Operational)
- resolved · Aug 18, 2026, 08:38 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 🇸🇬 Singapore (Operational) 🇲🇽 Queretaro (Operational) 🇨🇦 Toronto (Operational) 🇧🇬 Sofia (Operational) 🇺🇸 Miami (Operational) 🇦🇷 Buenos Aires (Operational) 🇧🇷 Sao Paulo (Operational) 🇩🇪 Frankfurt (Operational) 🇵🇪 Lima (Operational) 🇮🇪 Dublin (Operational) 🇿🇦 Johannesburg (Operational) 🇭🇰 Hong Kong (Operational) 🇮🇹 Milan (Operational) 🇨🇴 Bogota (Operational) 🇺🇸 Houston (Operational) 🇱🇹 Vilnius (Operational) 🇷🇺 Moscow (Operational) 🇨🇭 Zurich (Operational) 🇹🇷 Istanbul (Operational) 🇩🇪 Berlin (Operational) 🇺🇸 New York (Operational) 🇯🇵 Tokyo (Operational) 🇺🇸 Los Angeles (Operational) 🇮🇱 Tel Aviv (Operational) 🇳🇴 Oslo (Operational) 🇭🇺 Budapest (Operational) 🇬🇧 London (Operational) 🇺🇦 Kyiv (Operational) 🇸🇪 Stockholm (Operational) 🇦🇺 Sydney (Operational) 🇲🇾 Kuala Lumpur (Operational) 🇵🇹 Lisbon (Operational) 🇸🇰 Bratislava (Operational) 🇺🇸 San Jose (Operational) 🇳🇱 Amsterdam (Operational) 🇰🇿 Almaty (Operational) 🇨🇿 Prague (Operational) 🇬🇷 Athens (Operational) 🇷🇴 Bucharest (Operational) 🇦🇪 Fujairah (Operational) 🇩🇰 Copenhagen (Operational) 🇳🇬 Lagos (Operational) 🇵🇱 Warsaw (Operational) 🇫🇷 Paris (Operational) 🇪🇸 Madrid (Operational) 🇧🇪 Brussels (Operational) 🇰🇷 Seoul (Operational) 🇦🇹 Vienna (Operational) 🇭🇷 Zagreb (Operational) 🇫🇮 Oulu (Operational)
Latest: 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 understa…
Problem with Buenos Aires

Resolved —

Started Jul 16, 2026, 10:46 AM UTC · Resolved Jul 16, 2026, 10:46 AM UTC

🇦🇷 Buenos Aires
Timeline · 2 updates
- identified · Jul 16, 2026, 08:37 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 🇦🇷 Buenos Aires (Degraded performance)
- resolved · Jul 16, 2026, 10:46 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 🇦🇷 Buenos Aires (Operational)
Latest: 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 understa…
Ongoing outage in Zürich

Resolved —

Started Jul 13, 2026, 08:45 AM UTC · Resolved Jul 13, 2026, 08:45 AM UTC

🇨🇭 Zurich
Timeline · 2 updates
- investigating · Jul 11, 2026, 03:53 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 🇨🇭 Zurich (Full outage)
- resolved · Jul 13, 2026, 08:45 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 🇨🇭 Zurich (Operational)
Latest: 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 understa…
Problem with the Colombia location

Resolved —

Started Jul 07, 2026, 10:03 PM UTC · Resolved Jul 07, 2026, 10:03 PM UTC

🇨🇴 Bogota
Timeline · 6 updates
- investigating · Jul 07, 2026, 07:21 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 🇨🇴 Bogota (Full outage)
- monitoring · Jul 07, 2026, 07:50 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 🇨🇴 Bogota (Operational)
- resolved · Jul 07, 2026, 08:22 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 🇨🇴 Bogota (Operational)
- identified · Jul 07, 2026, 08:27 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 🇨🇴 Bogota (Full outage)
- resolved · Jul 07, 2026, 10:03 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 🇨🇴 Bogota (Operational)
- resolved · Jul 07, 2026, 10:03 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 🇨🇴 Bogota (Operational)
Latest: 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 understa…
Problem with Zagreb

Resolved —

Started Jul 06, 2026, 07:56 AM UTC · Resolved Jul 06, 2026, 07:56 AM UTC

🇭🇷 Zagreb
Timeline · 3 updates
- identified · Jul 06, 2026, 07: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. Affected components 🇭🇷 Zagreb (Full outage)
- resolved · Jul 06, 2026, 07:56 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 🇭🇷 Zagreb (Operational)
- resolved · Jul 06, 2026, 07:56 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 🇭🇷 Zagreb (Operational)
Latest: 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 understa…

See the full BlancVPN outage history

11 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse BlancVPN outage history →

Or sign up free to get alerts when BlancVPN breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 16 incidents View full outage history →

Elevated VPN connection failures / Повышенное число неудачных подключений к VPN Ongoing

Started Sep 10, 2026, 08:42 PM UTC · ● 3d 18h
Ongoing disruption across VPN locations, apps, API, websites and bot Ongoing

Started Sep 01, 2026, 05:33 AM UTC · ● 13d 9h
Connectivity Issues with Amneziawg, WireGuard, and OpenVPN Ongoing

Started Aug 18, 2026, 08:38 PM UTC · ● 26d 18h
Connectivity Issues with Amneziawg, WireGuard, and OpenVPN Resolved

Started Aug 18, 2026, 08:38 PM UTC · Resolved Aug 18, 2026, 08:38 PM UTC · —
Problem with Buenos Aires Ongoing

Started Jul 16, 2026, 10:46 AM UTC · ● 60d 4h
Problem with Buenos Aires Resolved

Started Jul 16, 2026, 10:46 AM UTC · Resolved Jul 16, 2026, 10:46 AM UTC · —
Ongoing outage in Zürich Ongoing

Started Jul 13, 2026, 08:45 AM UTC · ● 63d 6h
Ongoing outage in Zürich Resolved

Started Jul 13, 2026, 08:45 AM UTC · Resolved Jul 13, 2026, 08:45 AM UTC · —