Outage and Maintenance Information

From 10:19 a.m. on 10/13/2025 to 11:30 a.m. on 10/14/2025, various notification e-mails from our system were not being sent to your registered e-mail address.
Currently, the system is sending them normally.
The emails that were not sent during the outage period will be sent sequentially with a time delay.
Please wait for a while until you receive them.

The fix has been completed by updating the application.
Please update to the latest version from the following page.

Release Notes for iOS version
https://support.millenvpn.jp/126
Please install from "Download the latest version of MillenVPN".

We deeply apologize for the long-standing inconvenience caused to our customers.

Please update to the latest version from the following page.

Release Notes for iOS version
https://support.millenvpn.jp/126
Please install from "Download the latest version of MillenVPN".

The MillenVPN app for iOS does not display the list of servers and displays the following error message.
The following error message appears in the MillenVPN app for iOS: "The operation could not be completed successfully: Could not retrieve the access token. If you experience this problem, please contact Customer Support."

If you see the above error, please follow the steps on the following page to see if there is any improvement.

▼How to deal with the case where the list of connections is not displayed in the Servers tab [iOS].
https://support.millenvpn.jp/3171

The procedure on the above page did not show any improvement,
If you wish to connect to one of the servers in "Japan, Korea, USA, or UK", please consider using MillenVPN Native.

How to get started with MillenVPN Native
https://support.millenvpn.jp/669

We will report the situation as soon as new information becomes available.
We sincerely apologize for any inconvenience this may cause to our customers.

From October 20, 2024 to October 21, 2024, at around 10:00 a.m., there were connection problems on the Japan/Tokyo #12, Australia/Sydney #1, and Germany/Frankfurt servers (Native).
We deeply apologize for any inconvenience caused.

We apologize for any inconvenience caused by the Japan/Tokyo #1-5 servers (Native).
We have confirmed that the connection problem has been resolved.
The cause of the connection problem is that the server was down due to equipment failure until the restoration is completed.

We sincerely apologize for any inconvenience this may cause.

We are experiencing connection problems on Japan/Tokyo #1-5 servers (Native).
If you wish to use MillenVPN Native, please follow the instructions below to connect to the other server currently listed on My Page.

▼How to check the connection server address for different servers
1) Log in to My Page
https://accounts.millenvpn.jp/clientarea.php
2) Click on Services
3) Click on MillenVPN Native (free option)
4) Use the server shown in the "Connection Server Address" of MillenVPN Native in the page opened in 3).

We will report the situation as soon as new information becomes available.
We sincerely apologize for any inconvenience this may cause to our customers.

We have confirmed that the MillenVPN app for Android has been improved on Android 14 and Google Pixel devices, with regard to the crash at startup and the VPN connection not working properly.

We apologize for any inconvenience caused by this matter.

Please update or reinstall to the latest version from the following page. Release Notes for Android version https://support.millenvpn.jp/412

Please update or reinstall the application to the latest version from the following page.
Android version Release Note
https://support.millenvpn.jp/412

We are investigating a problem with the Android version of MillenVPN application on Android 14 and Google Pixel devices.
If you are using Android 14 or Google Pixel, please consider using another device if possible.
If you wish to use the Japan server, please consider using MillenVPN Native.

How to get started with MillenVPN Native
https://support.millenvpn.jp/669

We will report the situation as soon as new information becomes available.
We sincerely apologize for any inconvenience this may cause to our customers.

From June 23rd around 22:00 to June 24th around 16:30, there were connection problems due to increased server load on the Japan/Tokyo #12, Australia/Sydney #1, USA/New York #1, and Germany/Frankfurt servers (Native). We deeply apologize for any inconvenience caused.

We have released v2.4.2 of the MillenVPN dedicated application and have completed support for fixing OpenVPN connections.
Please update your application from the following store page.
https://play.google.com/store/apps/details?id=com.wlvpn.consumervpn
We sincerely apologize for any inconvenience this may cause.

We have released v2.4.1 of the MillenVPN application.
We apologize for the inconvenience, but please update the application from the store page below.

Google PlayStore
https://play.google.com/store/apps/details?id=com.wlvpn.consumervpn

Update details
Default VPN protocol has been changed to IKEv2.

We are continuing to investigate this issue.

We are investigating a problem with the MillenVPN app for Android that is preventing connection with the OpenVPN protocol.
If you are using MillenVPN for Android, please reinstall the application and change the protocol to "IKEv2" or "WireGuard" by referring to the following page,
and change the protocol to "IKEv2" or "WireGuard" by referring to the following page.

▼How to deal with VPN connection not working [Android].
https://support.millenvpn.jp/474

We will report the situation as soon as new information becomes available.
We sincerely apologize for any inconvenience this may cause to our customers.

From around 20:00 on April 20 to 23:00 on April 20, there was a connection problem on Japan/Tokyo #16, 17, 24, and 25 servers (OpenConnect) due to increased server load.
We deeply apologize for any inconvenience caused.

From around 10:40 p.m. on April 17 to 11:20 p.m. on April 17, there was a connection problem on the Japan/Tokyo #16, 17, 24, and 25 servers (OpenConnect) due to an increase in server load.
We deeply apologize for any inconvenience caused.

From around 21:30 on April 14 to 23:30 on April 14, there was a connection problem on Japan/Tokyo #17, 24, and 25 servers (OpenConnect) due to an increase in server load.
We deeply apologize for any inconvenience caused.

From around 10:50 p.m. on April 12 to 11:20 p.m. on April 12, there was a connection problem on the Japan/Tokyo #17 and #25 servers (OpenConnect) due to an increase in server load.
We deeply apologize for any inconvenience caused.

From around 10:30 p.m. on April 11 to 11:15 p.m. on April 11, there was a connection problem on the Japan/Tokyo #16, 24, and 25 servers (OpenConnect) due to an increase in server load.
We deeply apologize for any inconvenience caused.

From around 10:00 p.m. on April 6 to 11:30 p.m. on April 6, there was a connection problem on Japan/Tokyo #16, 17, 24, and 25 servers (OpenConnect) due to an increase in server load.
We deeply apologize for any inconvenience caused.

From around 10:00 p.m. on April 4 to 11:30 p.m. on April 4, there was a connection problem on the Japan/Tokyo #25 server (OpenConnect) due to an increase in server load.
We deeply apologize for any inconvenience caused.

From around 23:00 on March 31 to 01:00 on April 1, there were connection problems due to increased server load on the Japan/Tokyo #24 and #25 servers (OpenConnect).
We deeply apologize for any inconvenience caused.