Is Core Practice down?

Last checked 3m ago
Current status
Core Practice is up

No incidents right now.

Get alerts when Core Practice breaks →

Free · no credit card

Official status page: https://status.corepractice.com.au · Polled every 5 minutes · 10 components tracked

Real-time Core Practice status, recent outages, and incident history — pulled directly from Core Practice's official status page at https://status.corepractice.com.au every 5 minutes. Pingoru tracks 10 Core Practice services and has captured 5 incidents in the last 90 days (98.83% uptime). Get email, Slack, Discord, or webhook alerts the moment Core Practice reports a new incident — free for 5 monitors, no credit card.

Core Practice uptime 98.83% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Logged out when Generating Invoices
    Resolved 9h 11m
    Started Apr 28, 2026, 11:12 PM UTC · Resolved Apr 29, 2026, 08:23 AM UTC
    Core Practice Application
    8 updates · show timeline
    • investigating · Apr 28, 2026, 11:12 PM UTC

      We are aware of an issue with generating invoices and are currently investigating. We apologise for the inconvenience and will provide an update in 15 mins.

    • identified · Apr 28, 2026, 11:31 PM UTC

      We have identified a permission issue that is affecting a number of users. A hotfix is currently being prepared, and we will have a further update in the next 15mins.

    • identified · Apr 28, 2026, 11:50 PM UTC

      We are continuing to work on the hotfix for the permission issue affecting invoice generation. Our development team has identified the root cause and the fix is currently being prepared and tested before deployment. We will provide a further update in 30 minutes, or sooner if the hotfix is ready to deploy. We appreciate your patience while we work to resolve this.

    • identified · Apr 29, 2026, 12:25 AM UTC

      The hotfix for the permission issue affecting invoice generation has been completed and is now being packaged for deployment. We will provide a further update once deployment is underway, or within 30 minutes — whichever is sooner. We appreciate your patience while we work to resolve this.

    • identified · Apr 29, 2026, 01:27 AM UTC

      Apologies for the delay in this update. The hotfix has been completed and is currently undergoing final testing before deployment. We will provide a further update once deployment begins. We appreciate your patience while we work to resolve this

    • identified · Apr 29, 2026, 02:10 AM UTC

      The hotfix has completed testing and is scheduled for deployment between 12:30pm and 1:00pm AEST. Users may experience brief intermittent slowness during the window. We will provide a further update once deployment is complete and the fix has been verified. We appreciate your patience while we work to resolve this.

    • monitoring · Apr 29, 2026, 03:11 AM UTC

      The hotfix has been deployed. We are now monitoring the system to confirm the issue is fully resolved. Users should now be able to generate invoices as normal. If you continue to experience issues, please contact support. We will provide a further update shortly to confirm full resolution.

    • resolved · Apr 29, 2026, 08:23 AM UTC

      Summary: Between 07:00 AEST and 13:00 AEST, a number of users were unexpectedly logged out when attempting to generate invoices. The issue was caused by a regression in the most recent application release. A hotfix was deployed between 12:30pm and 1:00pm AEST and testing confirmed users are no longer being logged out. We will continue to monitor closely. Investigation: Telemetry indicated a consistent pattern of authorisation failures on an endpoint called during the invoice generation workflow. Further review identified that recent changes were causing some users to be logged out when this response was received, rather than handling it gracefully. Next Steps: The hotfix has corrected the client-side handling of these responses. Some users may need to refresh their browser to receive the updated application files. A problem ticket has been raised to review our pre-release testing process, specifically to ensure least-privileged user scenarios are covered in regression testing for permission-sensitive workflows. We apologise for the inconvenience caused and thank affected users for their patience.

    Latest: Summary: Between 07:00 AEST and 13:00 AEST, a number of users were unexpectedly logged out when attempting to generate invoices. The issue was caused by a regression in the most re…

See the full Core Practice outage history

4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 1 incident
  • Logged out when Generating Invoices Resolved
    Started Apr 28, 2026, 11:12 PM UTC · Resolved Apr 29, 2026, 08:23 AM UTC · 9h 11m

See Core Practice in your Pingoru dashboard

Monitor Core Practice alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Core Practice to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Core Practice incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Core Practice or see every provider at once.

Maintenance calendar

Scheduled Core Practice maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Core Practice status change, one inbox

Pingoru watches Core Practice's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Core Practice reports on 10 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Core Practice alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Core Practice maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Core Practice services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Core Practice from the same account, with per-user notification preferences for any monitor.

Get notified on Core Practice status changes

Pingoru watches Core Practice's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Core Practice free

Monitor Core Practice along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Core Practice and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Core Practice uptime & incident history

See 90 days of Core Practice uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Core Practice uptime history

Frequently asked questions

What is Core Practice's uptime?
Over the last 90 days, Core Practice reported 98.83% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.corepractice.com.au — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Core Practice's uptime history rolling forward in real time.
Has Core Practice had outages in 2026?
Yes — Core Practice has had 5 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Core Practice outage?
The most recent Core Practice incident was "Logged out when Generating Invoices", which started on April 28, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.corepractice.com.au. See the full incident card above for affected components and the update timeline.
How often does Core Practice have outages?
Based on the last 90 days, Core Practice averages 1.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Core Practice's status page?
Core Practice's official status page is https://status.corepractice.com.au. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Core Practice down right now?
Core Practice is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Core Practice reports a change. Current status is based on 10 tracked services.
How does Pingoru know if Core Practice is down?
We read https://status.corepractice.com.au directly, using Core Practice's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Core Practice has an outage?
Create a free Pingoru account and add Core Practice as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Core Practice's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Core Practice incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Core Practice issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Core Practice status?
We use Core Practice's own status page at https://status.corepractice.com.au. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Core Practice components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Core Practice's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Core Practice free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →