User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Utilities
pjm.com · Utilities
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1169 ms · 7 min ago.
No status feed
PJM Interconnection does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:00 | 0 | 0.0 | 1245 ms | 0 |
| 13:15 | 0 | 0.0 | 1124 ms | 0 |
| 13:30 | 0 | 0.0 | 2065 ms | 1 |
| 13:45 | 0 | 0.0 | 1416 ms | 0 |
| 14:00 | 0 | 0.0 | 1268 ms | 0 |
| 14:15 | 0 | 0.0 | 2730 ms | 0 |
| 14:30 | 0 | 0.0 | 990 ms | 0 |
| 14:45 | 0 | 0.0 | 2607 ms | 0 |
| 15:00 | 0 | 0.0 | 1504 ms | 0 |
| 15:15 | 0 | 0.0 | 1036 ms | 1 |
| 15:30 | 0 | 0.0 | 1152 ms | 0 |
| 15:45 | 0 | 0.0 | 1131 ms | 0 |
| 16:00 | 0 | 0.0 | 1332 ms | 0 |
| 16:15 | 0 | 0.0 | 950 ms | 0 |
| 16:30 | 0 | 0.0 | 2240 ms | 0 |
| 16:45 | 0 | 0.0 | 1306 ms | 0 |
| 17:00 | 0 | 0.0 | 1042 ms | 0 |
| 17:15 | 0 | 0.0 | 1027 ms | 0 |
| 17:30 | 0 | 0.0 | 1184 ms | 0 |
| 17:45 | 0 | 0.0 | 909 ms | 0 |
| 18:00 | 0 | 0.0 | 1214 ms | 1 |
| 18:15 | 0 | 0.0 | 1396 ms | 0 |
| 18:30 | 0 | 0.0 | 981 ms | 0 |
| 18:45 | 0 | 0.0 | 1901 ms | 0 |
| 19:00 | 0 | 0.0 | 1137 ms | 0 |
| 19:15 | 0 | 0.0 | 1251 ms | 0 |
| 19:30 | 0 | 0.0 | 2186 ms | 0 |
| 19:45 | 0 | 0.0 | 1219 ms | 0 |
| 20:00 | 0 | 0.0 | 788 ms | 1 |
| 20:15 | 0 | 0.0 | 1212 ms | 0 |
| 20:30 | 0 | 0.0 | 979 ms | 0 |
| 20:45 | 0 | 0.0 | 1187 ms | 0 |
| 21:00 | 0 | 0.0 | 1219 ms | 0 |
| 21:15 | 0 | 0.0 | 1442 ms | 0 |
| 21:30 | 0 | 0.0 | 1070 ms | 0 |
| 21:45 | 0 | 0.0 | 1179 ms | 0 |
| 22:00 | 0 | 0.0 | 1539 ms | 0 |
| 22:15 | 0 | 0.0 | 1623 ms | 1 |
| 22:30 | 0 | 0.0 | 1169 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for PJM Interconnection 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 PJM Interconnection goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send PJM Interconnection alerts to Slack, Discord or a webhook — free.
We track PJM Interconnection (pjm.com) as part of the Utilities group. Live checks and user reports.
PJM Interconnection has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with utilities services: outage maps and bill-pay pages slowing or failing during storms and peak demand, and account sign-in problems.
Measured uptime from our checks: 94.37% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 1402 ms average, 788–4297 ms range across 68 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public PJM Interconnection incident since monitoring began 1 day ago.
From our own checks: 94.37% over 1 day of checks.
1402 ms on average over the last 24 hours (788–4297 ms).
Not one we can read. This page uses independent checks of pjm.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For utilities services, watch for outage maps and bill-pay pages slowing or failing during storms and peak demand, and account sign-in problems. If many people report PJM Interconnection here at once, the problem is on PJM Interconnection's side.