User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 31 min ago. Last stored result reached it in 554 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 15 | 0 | 0.0 | 579 ms | 0 |
| Wed 17 | 0 | 0.0 | 633 ms | 0 |
| Wed 19 | 0 | 0.0 | 417 ms | 0 |
| Wed 21 | 0 | 0.0 | 693 ms | 0 |
| Wed 23 | 0 | 0.0 | 490 ms | 0 |
| Thu 01 | 0 | 0.0 | 652 ms | 0 |
| Thu 03 | 0 | 0.0 | 556 ms | 0 |
| Thu 05 | 0 | 0.0 | 576 ms | 0 |
| Thu 08 | 0 | 0.0 | 2262 ms | 0 |
| Thu 10 | 0 | 0.0 | 561 ms | 0 |
| Thu 12 | 0 | 0.0 | 571 ms | 0 |
| Thu 14 | 0 | 0.0 | 463 ms | 0 |
| Thu 16 | 0 | 0.0 | 359 ms | 0 |
| Thu 18 | 0 | 0.0 | 527 ms | 0 |
| Thu 20 | 0 | 0.0 | 617 ms | 0 |
| Thu 22 | 0 | 0.0 | 601 ms | 0 |
| Fri 00 | 0 | 0.0 | 211 ms | 0 |
| Fri 02 | 0 | 0.0 | 523 ms | 0 |
| Fri 04 | 0 | 0.0 | 456 ms | 0 |
| Fri 06 | 0 | 0.0 | 547 ms | 0 |
| Fri 08 | 0 | 0.0 | 369 ms | 0 |
| Fri 09 | 0 | 0.0 | 551 ms | 0 |
| Fri 11 | 0 | 0.0 | 583 ms | 0 |
| Fri 13 | 0 | 0.0 | 539 ms | 0 |
| Fri 14 | 0 | 0.0 | 570 ms | 0 |
| Fri 17 | 0 | 0.0 | 553 ms | 0 |
| Fri 18 | 0 | 0.0 | 685 ms | 0 |
| Fri 20 | 0 | 0.0 | 586 ms | 0 |
| Fri 21 | 0 | 0.0 | 432 ms | 0 |
| Fri 23 | 0 | 0.0 | 561 ms | 0 |
| Sat 01 | 0 | 0.0 | 575 ms | 0 |
| Sat 03 | 0 | 0.0 | 305 ms | 0 |
| Sat 06 | 0 | 0.0 | 511 ms | 0 |
| Sat 08 | 0 | 0.0 | 524 ms | 0 |
| Sat 10 | 0 | 0.0 | 398 ms | 0 |
| Sat 12 | 0 | 0.0 | 546 ms | 0 |
| Sat 15 | 0 | 0.0 | 578 ms | 0 |
| Sat 17 | 0 | 0.0 | 505 ms | 0 |
| Sat 19 | 0 | 0.0 | 447 ms | 0 |
| Sat 22 | 0 | 0.0 | 458 ms | 0 |
| Sun 00 | 0 | 0.0 | 537 ms | 0 |
| Sun 02 | 0 | 0.0 | 646 ms | 0 |
| Sun 05 | 0 | 0.0 | 526 ms | 0 |
| Sun 06 | 0 | 0.0 | 537 ms | 0 |
| Sun 07 | 0 | 0.0 | 532 ms | 0 |
| Sun 09 | 0 | 0.0 | 457 ms | 0 |
| Sun 11 | 0 | 0.0 | 541 ms | 0 |
| Sun 13 | 0 | 0.0 | 554 ms | 0 |
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 10 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Club Penguin Journey 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 Club Penguin Journey 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.
Club Penguin Journey, at cpjourney.net, is one of the Gaming services we monitor. Rediscover the magic of Club Penguin on Club Penguin Journey. Play mini-games, meet new friends, and take part in monthly parties and events. Join a thriving community and start your adventure today!
Club Penguin Journey publishes an official status page at status.cpjourney.net; when we can read it, its incident level is folded into the status shown here.
Typical issues with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
Measured uptime from our checks: 100% over 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 527 ms average, 447–646 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Club Penguin Journey incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
527 ms on average over the last 24 hours (447–646 ms).
Yes, at https://status.cpjourney.net.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For gaming services, watch for login and matchmaking failures, server disconnects, and store or download errors. If many people report Club Penguin Journey here at once, the problem is on Club Penguin Journey'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 Club Penguin Journey. 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.