# News: Articles for #Outage Report

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. The Messaging API has been operating normally since the following date and time. We apologize for the delayed announcement and any inconvenience that this may have caused.

# Date and time of outage

Date: April 24, 2020 Time: 14:41-17:46(GMT+9)

# Cause

Network failure

# Affected services

All functions provided by the Messaging API may have been affected by this outage.

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

[Updated] Notice about service outage in the aggregation of some APIs for 'Audience' and 'Insight'

Updated on May 1, 2020

The API we reported on April 22, 2020 is now available with a limit.

For more information, see the following pages:

We'd like to inform you about the following service outage regarding our Messaging API. We apologize for any inconvenience this may have caused.

# Date and time of outage

Date: 2020/04/13 Time: Since about 15:30 (GMT+9) (Ongoing)

# Details

After the time above, you may no longer be able to count impressions correctly in an audience for impression-based retargeting.

Therefore, we temporarily restrict the use of some features. Specifically, we will take the following actions.

We are currently investigating and responding to the issue.

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

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

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.