# News: Articles for #Outage Report

Notice about service outage for LINE Login and LINE Front-end Framework (resolved)

We'd like to inform you about a service outage regarding LINE Login and LINE Front-end Framework. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

October 17, 2020 11:17 - 11:22 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Impact

  • LINE Login
  • LINE Front-end Framework (LIFF)
  • Social API (v2.0, v2.1)

# Details

The API returned status code 5xx for some requests.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for LINE Login and LINE Front-end Framework (resolved)

We'd like to inform you about a service outage regarding LINE Login and LINE Front-end Framework. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: October 15, 2020
Time: Around 18:34–18:42 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Impact

  • LINE Login
  • LINE Front-end Framework
  • Social API (v2.0, v2.1)

# Details

The API returned status code 5xx for some requests.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Login (resolved)

We'd like to inform you about a service outage regarding the LINE Login. We've released a version of LINE that resolved the issue.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

August 20, 2020 - September, 21, 2020 JST (GMT+9)

# Cause

Issue with LINE for iOS and iPadOS.

# Details

When LINE Login was integrated into an iOS app with LINE SDK for iOS, some LINE Login processes didn't work properly.

Normally, in iOS apps with the LINE Login feature, these processes launch LINE.

  1. A user presses the LINE Login button on the iOS app.
  2. LINE is launched with a universal link.
  3. If step 2 fails, LINE is launched with a custom URL scheme.

Although LINE supports universal links, LINE may not be able to be launched with some universal links on certain devices or operating systems.

If you proceeded to step 3 in the above situation, LINE Login didn't work properly on some versions of LINE, and an alert saying Unable to connect. Update to the latest version of LINE or recheck the URL. was displayed on LINE.

# Affected services

If all of these conditions are met, the LINE Login process didn't work properly and an error message was displayed.

  • A user uses LINE for iOS or iPadOS.
  • A user uses LINE version 10.14.0 or 10.14.1.
  • LINE isn't launched with a universal link on a user's environment.
  • LINE Login was integrated into an iOS app with the LINE SDK for iOS Swift or LINE SDK for iOS Objective-C 5.0.0 or later.

If all of the above conditions are met, updating user's LINE version to 10.15.0 or later will resolve the issue.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. All functions provided by the Messaging API may have been affected by this outage.

The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: September 15, 2020 Time: 11:37-11:53 (GMT+9)

# Cause

Issue with our servers

# Details

The Messaging API call returned a status code 403 even if the request was correct.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*)

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for LINE Notify (resolved)

We'd like to inform you about a service outage regarding LINE Notify. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

September 11, 2020 15:16 JST (GMT+9) - September 11, 2020 16:42 JST (GMT+9)

# Cause of the outage

Issues with our operations.

# Affected services

LINE Notify (opens new window)

# Details

During the date and time stated above, LINE Notify was unable to send messages. It has been resolved and messages are now being sent properly.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Developers site (resolved)

We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

From: August 4, 2020 around 11:00 JST (GMT+9)
Until: August 14, 2020 around 13:00 JST (GMT+9)

# Cause

Issue with our servers.

# Details

During the specified time, the statistics graph in the Statistics tab for Messaging API channels in the LINE Developers Console was not displayed as intended. It is resolved now and the graph is being displayed properly.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice of failure of some analytics APIs (Partially resolved)

These problems occurred in the Messaging API, but it has been partially resolved. We apologize for any inconvenience caused to our customers.

# Date and time of outage

Issue 1: July 21, 2020 around 7:00 - 17:00 (GMT+9)

Issue 2: July 16, 2020 onwards (GMT+9)

# Situation

# (Resolved) Issue 1

When premium and verified account users called the Get number of followers API endpoint, the endpoint returned an incorrect number of followers for July 21, 2020.

This issue is now resolved and you can get the correct number for July 21, 2020.

# (Limitation) Issue 2

Some LINE Official Accounts (less than 0.5%) that used the Get number of followers API endpoint from July 16, 2020 to July 20, 2020 may have gotten incorrect numbers returned for followers, targetedReaches, and blocks.

The affected LINE Official Accounts may have had these issues:

  • If you added friends during this period, they aren't added to the total amount of friends.

  • The number of followers during this period is returned with less than the actual value.

For issue 2, the correct value can't be restored.

Note

Neither issue has any effect on the total message delivery count.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for sending webhook events (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

June 29, 2020 13:20 JST (GMT+9) - July 14, 2020 17:42 JST (GMT+9)

# Cause of the outage

Due to the detection of unauthorized communications in our network, we've blocked some communications as a preventive measure.

# Details

During the date and time stated above, webhook events couldn't be sent to some bot servers (Webhook URLs) using ngrok.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Front-end Framework (resolved)

We'd like to inform you about a service outage regarding LINE Front-end Framework. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time

Date: July 13, 2020
Time: 11:44–17:26 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

During the date and time stated above, there was an issue with our server that caused an error message to display when creating a new LIFF app. Although an error message was displayed, new LIFF apps were being created. We have already completed the recovery process.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Login (resolved)

We want to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience this may have caused.

# Date and time of outage

Date: 2020/6/24 Time: 15:30-16:14 JST (GMT+9)

# Cause

Issues with our servers.

# Details

The LINE Login process did not work properly in some cases.

Auto login and LINE login with Single Sign On (SSO) were not affected.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Messaging API服務中斷通知 (已修復)

我們必須通知您關於Messaging API近期發生的服務中斷問題。 所有由Messaging API提供的功能皆有可能受到影響。

這項問題目前已解決。Messaging API自下方的發生時間後已恢復正常運作。對於遲來的通知與此問題所造成的不便,我們致上誠摯的歉意。

# 發生時間

日期: 2020年4月24日

時間: 14:41-17:46 (GMT+9)

# 原因

網路故障

# 影響範圍

所有由Messaging API提供的功能皆有可能受到此問題影響。

LINE將會持續改善我們的服務品質以避免未來發生相關問題。感謝您的諒解。

[更新] 關於 Audience 和 Insight 在一些集成式 API 中服務故障的問題

2020年5月1日更新

在 2020 年 4 月 22 日我們回報了此 API,目前已可在有限制的狀況下使用它。

關於更多訊息,請參考下方頁面:

Messaging API 發生了下列故障的問題。對此造成您的不便,我們致上誠摯的歉意。

# 發生時間

日期: 2020 年 4 月 13 日

時間:約 15:30~ (GMT+9) (持續中)

# 細節

在上述時間發生之後,無法準確計算出曝光再行銷的受眾群的曝光量。

因此我們暫時限制了部分功能的使用。整體來說,我們將會採取以下行動:

我們正積極的調查與修復此問題。

LINE 將會持續改善我們的服務品質以避免未來發生相關問題。感謝您的諒解。

Notice about Flex Message Simulator outage (resolved)

We'd like to inform you about a service outage regarding Flex Message Simulator. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

January 21, 2020 13:03 JST (GMT+9) - January 22, 2020 11:59 JST (GMT+9)

# Cause

Issues with our servers.

# Affected services

Flex Message Simulator (https://developers.line.biz/flex-simulator/)

# Details

During the specified time, Flex Message Simulator was inaccessible.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for LINE Login (resolved)

We want to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience this may have caused.

# Date and time of outage

Date: 2019/12/19 Time: 19:10-19:32 JST (GMT+9)

# Cause

Issue with our servers.

# Details

LINE Login and LIFF operations were unstable and did not work properly.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: October 4, 2019

Time:

9:00-9:02 JST (GMT+9)

10:04 JST (GMT+9)

11:00-11:08 JST (GMT+9)

12:02-12:08 JST (GMT+9)

# Cause

Issue with our servers.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*).

# Details

The API returned status code 500 for some requests.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: September 11, 2019 Time: 17:00–18:30 JST (GMT+9)

Date: September 12, 2019 Time: 13:00–13:30 JST (GMT+9)

# Cause

Server outage due to heavy load.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*).

# Details

The API returned status code 500 for some requests. Also, the "Send reply message" endpoint (https://api.line.me/v2/bot/message/reply) returned error codes in the 400 range, even for correct requests.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for LINE Developers site (resolved)

We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: September 11th, 2019 Time: 13:46–15:58 JST (GMT+9)

# Cause

Issue with our servers.

# Details

During the specified time, the Statistics tab for Messaging API channels in the LINE Developers Console was not working as intended.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for LINE Developers site (resolved)

We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: August 28, 2019 Time: 18:15 ~ 18:40 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

During the date and time stated above, some users could not access the LINE Developers site and the LINE Developers Console.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Member users were able to retrieve Channel secret because of a bug (resolved)

We discovered and fixed a bug in the LINE Developers Console that allowed Member users to obtain a channel secret. We sincerely apologize for any inconvenience caused.

On July 24, 2019, we emailed this information to all administrators of channels with Member users.

# Issue time

Issue inception: September 21, 2017

Issue solved: July 17, 2019

# Details

There was a bug that allowed Member users to obtain the channel secret, which should have appeared only to Admin users.

The Channel settings tab did not display the channel secret when a Member user viewed the page. However, the API that the LINE Developers Console called in the background did return the channel secret. Therefore, a malicious Member user could have obtained and abused the channel secret.

What is a channel secret?

The channel secret is a secret key provided by LINE to call our APIs and validate identities. It should be kept secret from unauthorized parties.

Member user permissions

Originally, Member users can only view basic information and statistics for a channel. They don't have access to the channel secret.

# What you should do

If you're concerned that unauthorized Member users have obtained your channel secret, you should issue a new one. Doing so will invalidate the previous channel secret.

After you issue a new channel secret, you'll have to update it in the app which uses the channel secret. Carefully consider the impact of issuing a new channel secret on your app.

# How to issue a new channel secret

You can issue a new channel secret on the Channel settings tab in the LINE Developers Console.

Forced reissue of channel secret

LINE will not forcibly reissue new channel secrets. The Admin user for each channel should decide whether it's necessary to reissue a new channel secret.

# Acknowledgement

This bug was reported through the LINE Security Bug Bounty Program (opens new window).

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for LINE Login (resolved)

We want to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience this may have caused.

# Date and time of outage

Date: July 18, 2019 Time: 9:38–10:40 JST (GMT+9)

# Cause

Issue with our servers.

# Details

LINE Login returned http error codes with the pattern 5xx (500, 501, etc.) for some requests. As a result, LINE Login was unavailable in the following applications:

  • Web application
  • Desktop app

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

We encountered problems during the planned migration of accounts from the deprecated Developer Trial plan to the new free plan, which started on June 11, 2019. The problems have now been resolved. We sincerely apologize for the inconvenience this caused.

# Date and time of outage

From: June 11, 2019
Until: June 18, 2019 14:33 JST (GMT+9)

# Cause

In Japan and Thailand, accounts that were migrated from the old Developer Trial plan to the new free plan incorrectly retained their old limit on number of friends (50).

# Details

When a user tried to befriend an account that had reached the limit of 50 friends, this error was displayed:

Sorry, the account you are trying to add cannot accept any more friends.

We have now removed the limit on the number of friends.

LINE will continue improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for LINE Login (resolved)

We'd like to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: June 17, 2019 Time: 11:41–13:01 JST (GMT+9)

# Cause

Issue with our servers.

# Details

LINE Login returned error code "400 Bad Request" when some users attempted to log in.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: June 14, 2019 Time: 10:35–12:19 JST (GMT+9)

# Cause

Issue with our servers.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*).

# Details

The API returned status code 500 for some requests.

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: June 5, 2019 Time: 14:41–15:05 JST (GMT+9)

(Most errors were solved by 14:55.)

# Cause

Issue with our servers.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*) and webhook.

# Details

The API returned status code 403 or 500 error for some requests. Also, webhook events were not successfully sent.

We will continue to improve the quality of our services. Thank you for your understanding.

Notice about service outage for LINE Developers site (resolved)

We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: April 4, 2019 Time: 14:00 ~ 15:00 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

During the date and time stated above, users could not access the LINE Developers site and the LINE Developers Console.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Login and the Social API (resolved)

We'd like to inform you about a service outage regarding LINE Login and the Social API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: February 26, 2019

Time: 6:46–7:16 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

HTTP status code 500 was sometimes returned when requests were sent to the LINE Login and Social APIs.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

  • Date: February 26, 2019
  • Time: Approximately 11:15-13:00 (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

HTTP status code 500 was sometimes returned when the following API endpoints were accessed:

  • Get content API: https://api.line.me/v2/bot/message/{messageId}/content
  • Rich menu API: https://api.line.me/v2/bot/richmenu/*

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

  • Date: February 20, 2019
  • Time: Approximately 18:45-19:02 and 19:10-19:26 (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

The Messaging API experienced errors with error code 403 or 500 during the outage.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

  • Date: January 12, 2019
  • Time: 16:59-18:30 (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

The Messaging API experienced errors with status code 5xx for approximately one minute around 17:00 on January 12, 2019. Also, webhook events were not successfully sent until 18:30 on the same day.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date of recovery

Date: June 27, 2018 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

When the Messaging API was called to unlink a rich menu from a user that was not in a chat with the bot, the rich menu was not unlinked from the user. This issue occured only to users with LINE 8.7.0 or later for iOS and rich menus configured at admin-official.line.me.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Login and the Social API (resolved)

We'd like to inform you about a service outage regarding LINE Login and the Social API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: June 26, 2018

Time: 16:25–17:00 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

An error was returned when the following API features were accessed:

  • Get user profiles
  • Get friendship status
  • LINE Login

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Front-end Framework (resolved)

We'd like to inform you about a service outage regarding LINE Front-end Framework. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of recovery

Date: June 21, 2018 around 17:30 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

When a LIFF app was added to a channel, the permission to retrieve the user's email address was revoked if it had been granted to the channel. Please check if the email permission has been revoked or not from the LINE Developers Console. Request the permission again if it has been revoked.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Developers site (resolved)

We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: April 11, 2018 Time: 12:00 ~ 22:00 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

During the date and time stated above, certain users could not access the LINE Developers Console.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: March 27, 2018 Time: 21:40 ~ 23:50 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

HTTP status code 500 was sometimes returned when the following API endpoints were accessed:

  • Get content API: https://api.line.me/v2/bot/message/{messageId}/content
  • Rich menu API: https://api.line.me/v2/bot/richmenu/*

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Developers site (resolved)

We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of recovery

March 23, 2018 around 19:20 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

The icon image of a LINE@ account was not updated after setting or changing the icon image of the Messaging API (bot) channel that corresponds to the LINE@ account at the LINE Developers site.

This outage has now been resolved and the icon image of a LINE@ account can be configured by setting an icon image again on the "Channel settings" page.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Login and the Messaging API (resolved)

We'd like to inform you about a service outage regarding our Messaging API and LINE Login products. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: December 14, 2017
Time: 16:40–17:08 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

  1. Requests and responses (Messaging API and LINE Login) that contained user IDs either failed or returned incorrect user IDs.
  2. Webhooks for the Messaging API did not return correct user IDs.
  3. Push message requests with specified user IDs failed.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.