Skip to content
DeutschSign in

Is Los Angeles Times down right now?

latimes.com

Checking latimes.com…

Asking our locations to reach the site. This takes a few seconds.

Uptime, 24 hours
100 %
Uptime, 7 days
100 %
Uptime, 30 days
100 %

Based on 1 day of checks so far. Checks that failed because of how we test, not because of the site, are left out.

Response time, last 24 hours

2026-10-09 11:02 UTC: 25 ms2026-10-09 11:18 UTC: 21 ms2026-10-09 11:33 UTC: 19 ms2026-10-09 11:49 UTC: 20 ms2026-10-09 12:05 UTC: 22 ms2026-10-09 12:20 UTC: 24 ms2026-10-09 12:36 UTC: 24 ms2026-10-09 12:51 UTC: 28 ms2026-10-09 13:06 UTC: 22 ms2026-10-09 13:22 UTC: 34 ms2026-10-09 13:38 UTC: 26 ms2026-10-09 13:53 UTC: 21 ms2026-10-09 14:09 UTC: 21 ms2026-10-09 14:24 UTC: 21 ms2026-10-09 14:40 UTC: 25 ms2026-10-09 14:55 UTC: 30 ms2026-10-09 15:11 UTC: 22 ms2026-10-09 15:27 UTC: 23 ms2026-10-09 15:42 UTC: 23 ms2026-10-09 15:58 UTC: 26 ms2026-10-09 16:13 UTC: 21 ms2026-10-09 16:29 UTC: 24 ms2026-10-09 16:44 UTC: 24 ms
Green: response time, full height at 100 ms or more. Red: down. Amber: not confirmed.

Response time by location, last 24 hours

LocationAverage responseReached
Berlin 1, Germany20 ms23 of 23 checks
Falkenstein, Germany33 ms23 of 23 checks
Berlin 2, Germany24 ms23 of 23 checks

Each check runs from all locations at once. A location far from the site’s servers answers later; that says nothing about the site being slow.

Outage history

No confirmed outage on record. An outage is listed once Los Angeles Times could not be reached from at least two locations in two checks in a row.

Recent checks

TimeStatusLocationsResponse
2026-10-09 16:44 UTCUp3 of 324 ms
2026-10-09 16:29 UTCUp3 of 324 ms
2026-10-09 16:13 UTCUp3 of 321 ms
2026-10-09 15:58 UTCUp3 of 326 ms
2026-10-09 15:42 UTCUp3 of 323 ms
2026-10-09 15:27 UTCUp3 of 323 ms
2026-10-09 15:11 UTCUp3 of 322 ms
2026-10-09 14:55 UTCUp3 of 330 ms

Comments

0/500 · no links · do not post personal data

No comments yet. Be the first to say what you are seeing.

We can reach it, but you cannot?
  • Reload the page without the cache: Ctrl + F5 on Windows, Cmd + Shift + R on a Mac.
  • Open the site in a private window. If it works there, clear the cookies and cache for latimes.com.
  • Try another network, such as mobile data. If that works, the problem is with your provider or router.
  • Switch to a public DNS resolver such as 1.1.1.1 or 8.8.8.8, then flush your DNS cache.
  • Turn off VPNs, proxies and ad blockers for a moment. Some sites refuse those connections.
Embed a status badge

Show the current status of Los Angeles Times on your own page or in a README. The badge updates by itself.

Status of latimes.com

Similar sites