BART outages and problems
In the past 24 hours, 64 user reports came in for BART. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 97.92% uptime for the day.
The most recent spike big enough to count as an outage was 2 hours ago. The busiest 15-minute window of the day had 17 reports, about 2 hours ago.
-
Outage
Ended 2 h agoLasted 30 min17peak reports
BART in October 2026
- Problem reports in October (since 28 October)
- 64
Monthly report for October 2026
What went wrong
What people said was wrong in recent problem reports for BART.
Share of 6 recent reports that said what was wrong.
Where BART problem reports come from
The map shows where recent problem reports for BART came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.
- Outage now
- Problems now
- Normal
Map outlines: Natural Earth.
BART problem spikes, last 30 days
Since 28 October, BART had 1 outage spike.
-
Outage
Thu 29 Oct, 03:10–03:45Lasted 36 min19peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 28 October 2026. Monthly reports for all services
How to fix BART not working
BART is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach bart.gov over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not BART.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Problems at the same time as BART
Since 28 October, BART's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
BART: Thu 29 Oct, 03:10 to 03:45
- ESPN Fantasy Football, outage,27 Oct 19:50 to 05:15
- Character.AI, outage,28 Oct 12:30 to 04:15
- Fanduel, outage,28 Oct 15:45 to 05:15
- Facebook, outage,01:45 to 04:45
- DuckDuckGo, outage,01:55 to 03:30
- Vodafone, outage,02:00 to 03:45
- EE, outage,02:00 to 04:00
- Plusnet, outage,02:15 to 03:45
28 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
BART IP address, servers and network
- IPv4 addresses
- 104.18.30.20
Show all 2
- 104.18.31.20
- IPv6 addresses
- 2606:4700::6812:1e14
Show all 2
- 2606:4700::6812:1f14
- Network
- AS13335 · Cloudflare, Inc., registered in the United States
- Served through
- Cloudflare · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- its own name servers (bart.gov)
- HTTPS certificate
- Issued by Google Trust Services, valid until 16 Jan 2027 (78 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 1,571 ms
Checked from our server in Frankfurt, Germany, 1 h ago, for www.bart.gov. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from bart.gov. 5 of the answers turned the automated check away (HTTP 403), which many sites do with bots; the site itself was up. Fastest from Warsaw (97 ms), slowest from Milan (609 ms). Every location connected through Cloudflare, Inc. (AS13335), using 2 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 301 | 491 ms | 104.18.30.20 |
| ViennaAustria | Up · HTTP 301 | 605 ms | 104.18.30.20 |
| MilanItaly | Up · HTTP 301 | 609 ms | 104.18.30.20 |
| ParisFrance | Up · HTTP 403 | 323 ms | 104.18.30.20 |
| AmsterdamNetherlands | Up · HTTP 301 | 559 ms | 104.18.31.20 |
| MadridSpain | Up · HTTP 301 | 601 ms | 104.18.31.20 |
| WarsawPoland | Up · HTTP 403 | 97 ms | 104.18.31.20 |
| Los AngelesUSA | Up · HTTP 301 | 147 ms | 104.18.30.20 |
| São PauloBrazil | Up · HTTP 403 | 342 ms | 104.18.30.20 |
| SingaporeSingapore | Up · HTTP 403 | 228 ms | 104.18.31.20 |
| TokyoJapan | Up · HTTP 403 | 148 ms | 104.18.30.20 |
Checked with check-host.net from its servers in these cities 1 h ago, for bart.gov. Time is how long each server took to load the page.
Put the BART status badge on your site
Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.
<a href="https://isitdownrightnow.app/services/bart/"><img src="https://isitdownrightnow.app/badge/bart.svg" alt="BART status" height="20"></a>[](https://isitdownrightnow.app/services/bart/)The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.
How we track BART
The status on this page comes from user-submitted problem reports for BART, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for BART, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. BART doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.