User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 29 min ago. Last stored result reached it in 109 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 183 ms | 0 |
| Mon 19 | 0 | 0.0 | 132 ms | 0 |
| Mon 21 | 0 | 0.0 | 288 ms | 0 |
| Mon 23 | 0 | 0.0 | 191 ms | 0 |
| Tue 01 | 0 | 0.0 | 298 ms | 0 |
| Tue 03 | 0 | 0.0 | 289 ms | 0 |
| Tue 05 | 0 | 0.0 | 122 ms | 0 |
| Tue 07 | 0 | 0.0 | 273 ms | 0 |
| Tue 10 | 0 | 0.0 | 278 ms | 0 |
| Tue 12 | 0 | 0.0 | 158 ms | 0 |
| Tue 14 | 0 | 0.0 | 297 ms | 0 |
| Tue 16 | 0 | 0.0 | 308 ms | 0 |
| Tue 18 | 0 | 0.0 | 294 ms | 0 |
| Tue 21 | 0 | 0.0 | 339 ms | 0 |
| Tue 23 | 0 | 0.0 | 236 ms | 0 |
| Wed 01 | 0 | 0.0 | 320 ms | 0 |
| Wed 03 | 0 | 0.0 | 257 ms | 0 |
| Wed 06 | 0 | 0.0 | 152 ms | 0 |
| Wed 08 | 0 | 0.0 | 166 ms | 0 |
| Wed 10 | 0 | 0.0 | 383 ms | 0 |
| Wed 12 | 0 | 0.0 | 306 ms | 0 |
| Wed 14 | 0 | 0.0 | 142 ms | 0 |
| Wed 16 | 0 | 0.0 | 238 ms | 0 |
| Wed 19 | 0 | 0.0 | 89 ms | 0 |
| Wed 21 | 0 | 0.0 | 217 ms | 0 |
| Wed 23 | 0 | 0.0 | 211 ms | 0 |
| Thu 01 | 0 | 0.0 | 105 ms | 0 |
| Thu 03 | 0 | 0.0 | 179 ms | 0 |
| Thu 05 | 0 | 0.0 | 154 ms | 0 |
| Thu 07 | 0 | 0.0 | 151 ms | 0 |
| Thu 09 | 0 | 0.0 | 115 ms | 0 |
| Thu 11 | 0 | 0.0 | 149 ms | 0 |
| Thu 14 | 0 | 0.0 | 291 ms | 0 |
| Thu 16 | 0 | 0.0 | 311 ms | 0 |
| Thu 18 | 0 | 0.0 | 300 ms | 0 |
| Thu 20 | 0 | 0.0 | 266 ms | 0 |
| Thu 22 | 0 | 0.0 | 295 ms | 0 |
| Fri 00 | 0 | 0.0 | 237 ms | 0 |
| Fri 02 | 0 | 0.0 | 217 ms | 0 |
| Fri 04 | 0 | 0.0 | 139 ms | 0 |
| Fri 06 | 0 | 0.0 | 212 ms | 0 |
| Fri 08 | 0 | 0.0 | 287 ms | 0 |
| Fri 10 | 0 | 0.0 | 331 ms | 0 |
| Fri 11 | 0 | 0.0 | 346 ms | 0 |
| Fri 12 | 0 | 0.0 | 255 ms | 0 |
| Fri 14 | 0 | 0.0 | 209 ms | 0 |
| Fri 16 | 0 | 0.0 | 251 ms | 0 |
| Fri 18 | 0 | 0.0 | 109 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Line2 yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Line2 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Line2 alerts to Slack, Discord or a webhook — free.
We track Line2 (line2.com) as part of the Cloud & developer group. Protect your primary number with a private second line. Unlimited talk and text across the US and Canada, all within the Line2 app.
Line2 publishes an official status page at status.line2.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 243 ms average, 109–346 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Line2 incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
243 ms on average over the last 24 hours (109–346 ms).
Yes, at https://status.line2.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Line2 here at once, the problem is on Line2's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Line2. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.