Skip to content

Outage tracker / PG&E

Is PG&E down?

Short linkrlup.io/down/pge

I'm having a problem

Awaiting datachecked 1 minute ago

Our checks of PG&E pass from 3 of the 4 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.

As of Nov 5, 2026, 3:06 PM UTC, RealUptime's checks of PG&E passed in all 3 regions that returned a reading. RealUptime could not obtain a reading from Asia-Pacific, which is a fact about our own check there and is not evidence about PG&E.

Front-door checks

Our checks of PG&E did not fail from two or more distant regions in the 3 days we have checked it (since Nov 2, 2026). This does not show PG&E works for users.

our check readinglive · checked Nov 5, 2026, 3:06 PM UTC
US-East700 msChecks passing
US-West1682 msChecks passing
Europe829 msChecks passing
Asia-Pacific1319 msAwaiting data
their status pagetheir claim, not our reading

PG&E publishes no status feed we can read, so the only reading here is our check reading on the left.

PG&E response time, by region

US-East
2.1sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
US-West
2.9sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.9s
Oct 7Oct 21Nov 5
Europe
1.7sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Asia-Pacific
2.1sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 3.2s2026-11-03 UTC: p95 2.9s2026-11-04 UTC: p95 3.6s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Why some readings show as awaiting data. 1 of 4 readings for PG&E came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about PG&E's health, so we publish no verdict for those readings rather than guessing in either direction. 1 of those reading received an actual response: the connection, the TLS handshake, and the edge all answered, with a measured latency. Our check passed there, just not through the specific path automated checks are filtered on. Read how we tell the difference.

Check your own site while you wait on PG&E

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 PG&E. It cannot diagnose PG&E's own systems.

Get an email when our checks of PG&E fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of PG&E fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not PG&E's official status.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 700msstatus code: 200checked: Nov 5, 2026, 3:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach PG&E normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1682msstatus code: 200checked: Nov 5, 2026, 2:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach PG&E normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionPG&E is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionPG&E is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionPG&E 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
      Checks passinglatency: 829msstatus code: 200checked: Nov 5, 2026, 3:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach PG&E normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionPG&E is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Awaiting dataAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Awaiting datalatency: 1319msstatus code: 403check reading: filtered as automatedchecked: Nov 5, 2026, 3:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayPG&E refused our Asia-Pacific probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from Asia-Pacific to say anything on their own.
    • Southeast Asia
      Not monitored from this regionPG&E is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionPG&E 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 PG&E, 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 PG&E yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for PG&E.

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

We have been measuring PG&E since November 2, 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 PG&E covering any window you pick, with our check readings and PG&E's own claim at the time, side by side.

Full check history for PG&E: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

PG&E uptime by RealUptime's checksLive, from this page's own readings.
[![PG&E uptime by RealUptime's checks](https://realuptime.io/outages/pge/badge.svg?days=30)](https://realuptime.io/outages/pge)
<a href="https://realuptime.io/outages/pge"><img src="https://realuptime.io/outages/pge/badge.svg?days=30" alt="PG&E uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is PG&E down?", https://realuptime.io/outages/pge. The readings change with every check, so give the date you read them.

How our checks compare with PG&E's stated SLA

At or above your target

Our checks of PG&E failed for none over the 72h 53m since we started checking it on 2026-11-02, which is 100% uptime by our checks. A 99.9% target allows 4 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from PG&E'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

primary
https://www.pge.com/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: www.pge.com

RealUptime is not affiliated with PG&E; the name identifies what we checked, and nothing here speaks for PG&E's own team. We send a single web request to PG&E from 4 regions on our own schedule and time the response. We do not see inside PG&E's systems, do not use an account or real transaction, and are not the same signal PG&E's own team has access to. Treat this as one external data point, not a verdict. What we check for PG&E is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. PG&E operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 1214 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

360LearningADPAIGAPRS.fiAXA