BlancVPN Outage History

BlancVPN is up right now

BlancVPN had 42 outages in the last 2 years totaling 6840h 25m of downtime — averaging 1.7 incidents per month.

There were 42 BlancVPN outages since October 22, 2025 totaling 6840h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://blancvpnstatus.com

Minor September 29, 2026

Subscription links for third-party VPN clients may be unavailable.

Detected by Pingoru
Sep 29, 2026, 11:09 PM UTC
Resolved
Sep 29, 2026, 11:29 PM UTC
Duration
19m
Timeline · 4 updates
  1. monitoring Sep 29, 2026, 11:09 PM UTC

    Status: Identified We have identified the cause of the issue and are now working on a fix and restoring normal operation. We’ll provide another update as soon as we have confirmed progress. Мы установили причину сбоя и сейчас работаем над исправлением и восстановлением нормальной работы сервиса. Опубликуем следующее обновление, как только появится подтверждённый прогресс.

  2. identified Sep 29, 2026, 11:09 PM UTC

    Status: Identified We have identified the cause of the issue and are now working on a fix and restoring normal operation. We’ll provide another update as soon as we have confirmed progress. Мы установили причину сбоя и сейчас работаем над исправлением и восстановлением нормальной работы сервиса. Опубликуем следующее обновление, как только появится подтверждённый прогресс.

  3. monitoring Sep 29, 2026, 11:25 PM UTC

    Status: Monitoring We have restored service and continue monitoring the situation to ensure stable operation. Thank you for your patience and understanding. Мы восстановили работу сервиса и продолжаем наблюдать за его состоянием, чтобы убедиться в стабильной работе. Спасибо за терпение и понимание.

  4. resolved Sep 29, 2026, 11:29 PM UTC

    Status: Resolved The incident has been resolved. Service has been fully restored and is operating normally. Thank you for your patience and understanding. Инцидент устранён. Работа сервиса полностью восстановлена, он работает в обычном режиме. Спасибо за терпение и понимание.

Read the full incident report →

Minor September 1, 2026

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

Detected by Pingoru
Sep 01, 2026, 05:32 AM UTC
Resolved
Sep 10, 2026, 08:42 PM UTC
Duration
9d 15h
Affected: 🇩🇪 Berlin🇮🇹 Milan🇩🇪 Frankfurt🇪🇸 Madrid🇨🇴 Bogota🇮🇪 Dublin🇺🇸 Houston🇳🇴 Oslo🇿🇦 Johannesburg🇰🇿 Almaty🇳🇱 Amsterdam🇬🇷 Athens🇷🇴 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🇳🇬 Lagos
Timeline · 8 updates

Read the full incident report →

Minor August 31, 2026

Ongoing disruption across VPN locations, apps, API, websites and bot

Detected by Pingoru
Aug 31, 2026, 03:31 PM UTC
Resolved
Sep 01, 2026, 05:33 AM UTC
Duration
14h 2m
Affected: 🇩🇪 Berlin🇮🇹 Milan🇩🇪 Frankfurt🇪🇸 Madrid🇨🇴 Bogota🇮🇪 Dublin🇺🇸 Houston🇳🇴 Oslo🇿🇦 Johannesburg🇰🇿 Almaty🇳🇱 AmsterdamWebsiteTelegram Bot🇬🇷 Athens🇷🇴 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🇳🇬 Lagos
Timeline · 7 updates

Read the full incident report →

Minor August 18, 2026

Connectivity Issues with Amneziawg, WireGuard, and OpenVPN

Detected by Pingoru
Aug 18, 2026, 05:49 PM UTC
Resolved
Aug 18, 2026, 08:38 PM UTC
Duration
2h 49m
Affected: 🇩🇪 Berlin🇮🇹 Milan🇩🇪 Frankfurt🇪🇸 Madrid🇨🇴 Bogota🇮🇪 Dublin🇺🇸 Houston🇳🇴 Oslo🇿🇦 Johannesburg🇰🇿 Almaty🇳🇱 Amsterdam🇬🇷 Athens🇷🇴 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🇳🇬 Lagos
Timeline · 4 updates

Read the full incident report →

Minor July 16, 2026

Problem with Buenos Aires

Detected by Pingoru
Jul 16, 2026, 08:37 AM UTC
Resolved
Jul 16, 2026, 10:46 AM UTC
Duration
2h 8m
Affected: 🇦🇷 Buenos Aires
Timeline · 3 updates
  1. 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)

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

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

Read the full incident report →

Minor July 11, 2026

Ongoing outage in Zürich

Detected by Pingoru
Jul 11, 2026, 03:53 PM UTC
Resolved
Jul 13, 2026, 08:45 AM UTC
Duration
1d 16h
Affected: 🇨🇭 Zurich
Timeline · 3 updates
  1. 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)

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

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

Read the full incident report →

Minor July 7, 2026

Problem with the Colombia location

Detected by Pingoru
Jul 07, 2026, 07:21 PM UTC
Resolved
Jul 07, 2026, 10:03 PM UTC
Duration
2h 41m
Affected: 🇨🇴 Bogota
Timeline · 7 updates
  1. 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)

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

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

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

  5. monitoring 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)

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

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

Read the full incident report →

Minor July 6, 2026

Problem with Zagreb

Detected by Pingoru
Jul 06, 2026, 07:16 AM UTC
Resolved
Jul 06, 2026, 07:56 AM UTC
Duration
39m
Affected: 🇭🇷 Zagreb
Timeline · 4 updates
  1. 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)

  2. monitoring 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)

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

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

Read the full incident report →

Minor June 19, 2026

Неполадки при подключении к VPN из России // VPN Connectivity Issues from Russia

Detected by Pingoru
Jun 19, 2026, 09:30 AM UTC
Resolved
Sep 17, 2026, 11:57 PM UTC
Duration
90d 14h
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 · 7 updates

Read the full incident report →

Minor June 6, 2026

Maintenance in Los Angeles

Detected by Pingoru
Jun 06, 2026, 10:14 AM UTC
Resolved
Jun 06, 2026, 03:09 PM UTC
Duration
4h 55m
Affected: 🇺🇸 Los Angeles
Timeline · 4 updates
  1. 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)

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

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

  4. 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
Aug 29, 2026, 12:04 AM UTC
Duration
90d 4h
Affected: 🇱🇹 Vilnius
Timeline · 5 updates
  1. 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)

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

  3. monitoring 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)

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

  5. 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
Aug 27, 2026, 12:01 AM UTC
Duration
90d 1h
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 · 6 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:19 PM UTC
Resolved
May 16, 2026, 05:34 PM UTC
Duration
14m
Affected: 🇱🇹 Vilnius
Timeline · 3 updates
  1. 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)

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

  3. 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 12, 2026

Problem with the India location

Detected by Pingoru
May 12, 2026, 04:19 PM UTC
Resolved
May 13, 2026, 08:27 AM UTC
Duration
16h 7m
Affected: 🇮🇳 Bangalore
Timeline · 3 updates
  1. 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)

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

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

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
  1. 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:02 AM UTC
Resolved
May 07, 2026, 07:50 AM UTC
Duration
48m
Affected: 🇲🇽 Queretaro
Timeline · 4 updates
  1. 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.

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

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

  4. 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:16 PM UTC
Resolved
May 06, 2026, 04:48 PM UTC
Duration
32m
Timeline · 3 updates
  1. 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.

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

  3. 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 5, 2026

Delays in delivery of login code emails

Detected by Pingoru
May 05, 2026, 10:36 PM UTC
Resolved
May 06, 2026, 09:14 AM UTC
Duration
10h 37m
Affected: Website
Timeline · 3 updates
  1. 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)

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

  3. 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, 04:30 AM UTC
Resolved
Apr 29, 2026, 08:39 AM UTC
Duration
4h 9m
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

Read the full incident report →

Notice April 17, 2026

Problem with V2Ray Subscription

Detected by Pingoru
Apr 17, 2026, 09:16 AM UTC
Resolved
Apr 17, 2026, 10:16 AM UTC
Duration
1h
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 →

Major April 12, 2026

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

Detected by Pingoru
Apr 12, 2026, 12:29 PM UTC
Resolved
Apr 12, 2026, 01:20 PM UTC
Duration
50m
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 →

Notice April 3, 2026

VPN Access Issue for New Users

Detected by Pingoru
Apr 03, 2026, 11:04 AM UTC
Resolved
Apr 03, 2026, 12:30 PM UTC
Duration
1h 26m
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, 07:11 AM UTC
Resolved
Mar 30, 2026, 09:03 AM UTC
Duration
1h 51m
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 →

Critical March 16, 2026

Server availability problem in India.

Detected by Pingoru
Mar 16, 2026, 12:42 PM UTC
Resolved
Mar 16, 2026, 02:27 PM UTC
Duration
1h 44m
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 →

Notice March 11, 2026

Issues with India Location

Detected by Pingoru
Mar 11, 2026, 10:49 AM UTC
Resolved
Mar 11, 2026, 11:43 AM UTC
Duration
54m
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 →