Is LINE down right now?

Operational. We reached LINE from all 1 region we check.

How does RealUptime check if LINE is down?

RealUptime checks LINE with scheduled HTTP probes against its public, unauthenticated functional endpoints, run from named regions on a fixed cadence, plus an extra confirmation probe whenever a signal suggests a problem. This verifies that the functional endpoints we probe actually answer, not that every feature of LINE works end to end.

What does "degraded" mean for LINE?

Degraded means LINE answered our probe but at several times its own seven-day median response time. Degraded only ever applies to a reading that answered: a surface that is down, or one that refused our probe, is reported as down or awaiting data instead, never softened into "degraded".

What is LINE's current response time?

RealUptime's most recent measured response time for LINE, by region: Asia-Pacific: 442 ms. This is the latest single probe reading per region, not an average.

When did RealUptime last check LINE?

RealUptime's probes last checked LINE at 2026-10-05T19:50:06.573Z.

Is LINE down?

Short linkrlup.io/down/line

I'm having a problem

Operationalchecked 26 minutes ago

We reached LINE from all 1 region we check.

As of Oct 5, 2026, 7:50 PM UTC, LINE answered RealUptime's probe in Asia-Pacific, the only region with a reading for it.

Functional endpoints verified

No outage recorded in the 46 days we have measured LINE (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 7:50 PM UTC

Asia-Pacific442 msOperational

LINE's user base is concentrated in Japan and neighbouring markets, so we check it from our Tokyo region, where it actually runs.

their status pagetheir claim, not our reading

LINE publishes no status feed we can read, so the only independent reading here is ours on the left.

LINE response time, by region

Asia-Pacific

922msp95 · latest

2s1s0ms

Sep 6Sep 20Oct 5

Is it LINE, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not LINE -- it cannot diagnose LINE's own systems.

What we measured, and what people reported

North America
Not monitored from this regionUS-East, US-West, US-Central, Canada
- US-East
  Not monitored from this regionLINE is not monitored from this region.
  0 people in the last 5 minutesNot enough reports to say
- US-West
  Not monitored from this regionLINE is not monitored from this region.
  0 people in the last 5 minutesNot enough reports to say
- US-Central
  Not monitored from this regionLINE is not monitored from this region.
  0 people in the last 5 minutesNot enough reports to say
- Canada
  Not monitored from this regionLINE is not monitored from this region.
  0 people in the last 5 minutesNot enough reports to say
South America
Not monitored from this regionLINE is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Europe
Not monitored from this regionEurope, UK
- Europe
  Not monitored from this regionLINE is not monitored from this region.
  0 people in the last 5 minutesNot enough reports to say
- UK
  Not monitored from this regionLINE is not monitored from this region.
  0 people in the last 5 minutesNot enough reports to say
Asia Pacific
Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
- Asia-Pacific
  Operationallatency: 442msstatus code: 200checked: Oct 5, 2026, 7:50 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach LINE normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast Asia
  Not monitored from this regionLINE is not monitored from this region.
  0 people in the last 5 minutesNot enough reports to say
- Australia
  Not monitored from this regionLINE is not monitored from this region.
  0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using LINE, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for LINE yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for LINE.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring LINE since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for LINE covering any window you pick, with our measurements and LINE's own claim at the time, side by side.

Full availability history for LINE: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

Live, from this page's own readings.

[![LINE uptime measured by RealUptime](https://realuptime.io/outages/line/badge.svg?days=30)](https://realuptime.io/outages/line)

<a href="https://realuptime.io/outages/line"><img src="https://realuptime.io/outages/line/badge.svg?days=30" alt="LINE uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What LINE's SLA implies, from our measurement

Window

What you pay per month

Uptime target in your contract

Include outages only one region saw (none)

At or above your target

We measured none of downtime for LINE over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from LINE's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

secondaryfunctional: live API

https://api.line.me/v2/profile

primary

https://line.me/en/

RealUptime is not affiliated with LINE; the name identifies what we measured, and nothing here speaks for LINE's own team. We send a single web request to LINE from 1 region on our own schedule and time the response. We do not see inside LINE's systems, do not use an account or real transaction, and are not the same signal LINE's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for LINE is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. LINE's user base is concentrated in Japan and neighbouring markets, so we check it from our Tokyo region, where it actually runs. Read the full methodology.

Related services

Bluesky Discord Facebook Google Meet Instagram