User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is pganalyze down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → pganalyze.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 20 min ago. Last stored result reached it in 334 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 372 ms | 0 |
| Nov 7 | 0 | 0.0 | 353 ms | 0 |
| Nov 8 | 0 | 0.0 | 248 ms | 0 |
| Nov 8 | 0 | 0.0 | 296 ms | 0 |
| Nov 8 | 0 | 0.0 | 317 ms | 0 |
| Nov 8 | 0 | 0.0 | 258 ms | 0 |
| Nov 9 | 0 | 0.0 | 385 ms | 0 |
| Nov 9 | 0 | 0.0 | 339 ms | 0 |
| Nov 9 | 0 | 0.0 | 311 ms | 0 |
| Nov 9 | 0 | 0.0 | 275 ms | 0 |
| Nov 10 | 0 | 0.0 | 382 ms | 0 |
| Nov 10 | 0 | 0.0 | 335 ms | 0 |
| Nov 10 | 0 | 0.0 | 350 ms | 0 |
| Nov 10 | 0 | 0.0 | 288 ms | 0 |
| Nov 11 | 0 | 0.0 | 318 ms | 0 |
| Nov 11 | 0 | 0.0 | 334 ms | 0 |
| Nov 11 | 0 | 0.0 | 353 ms | 0 |
| Nov 11 | 0 | 0.0 | 380 ms | 0 |
| Nov 12 | 0 | 0.0 | 358 ms | 0 |
| Nov 12 | 0 | 0.0 | 317 ms | 0 |
| Nov 12 | 0 | 0.0 | 337 ms | 0 |
| Nov 12 | 0 | 0.0 | 258 ms | 0 |
| Nov 13 | 0 | 0.0 | 306 ms | 0 |
| Nov 13 | 0 | 0.0 | 286 ms | 0 |
| Nov 13 | 0 | 0.0 | 316 ms | 0 |
| Nov 13 | 0 | 0.0 | 326 ms | 0 |
| Nov 14 | 0 | 0.0 | 319 ms | 0 |
| Nov 14 | 0 | 0.0 | 162 ms | 0 |
| Nov 14 | 0 | 0.0 | 354 ms | 0 |
| Nov 14 | 0 | 0.0 | 342 ms | 0 |
Reliability
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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live pganalyze badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for pganalyze yet. Outages of 10 minutes or more get their own page here.
Having trouble with pganalyze?
One report per service every 10 minutes from this network. No account.
Follow pganalyze
Get an email when pganalyze goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
About pganalyze
pganalyze is listed in our Productivity category and checked at pganalyze.com. DBAs and developers use pganalyze to identify the root cause of performance issues, optimize queries and to get alerts about critical issues. Sign up for free!
pganalyze publishes an official status page at status.pganalyze.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 298 ms average, 157–373 ms range across 14 successful checks.
Questions
Is pganalyze down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was pganalyze last down?
We have not recorded a public pganalyze incident since monitoring began 8 days ago.
What is pganalyze's uptime?
From our own checks: 100% over 8 days of checks.
How fast does pganalyze respond?
298 ms on average over the last 24 hours (157–373 ms).
Does pganalyze have an official status page?
Yes, at https://status.pganalyze.com.
pganalyze not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report pganalyze here at once, the problem is on pganalyze'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 pganalyze. 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.