User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
creditorwatch.com.au · Cloud & developer
Is CreditorWatch 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 → creditorwatch.com.au—
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 47 min ago. Last stored result reached it in 599 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 |
|---|---|---|---|---|
| 05:15 | 0 | 0.0 | 611 ms | 0 |
| 07:15 | 0 | 0.0 | 511 ms | 0 |
| 09:15 | 0 | 0.0 | 890 ms | 0 |
| 11:15 | 0 | 0.0 | 663 ms | 0 |
| 13:30 | 0 | 0.0 | 866 ms | 0 |
| 15:30 | 0 | 0.0 | 1167 ms | 0 |
| 17:30 | 0 | 0.0 | 1130 ms | 0 |
| 19:45 | 0 | 0.0 | 675 ms | 0 |
| 21:45 | 0 | 0.0 | 682 ms | 0 |
| 23:45 | 0 | 0.0 | 702 ms | 0 |
| 01:45 | 0 | 0.0 | 469 ms | 0 |
| 03:45 | 0 | 0.0 | 904 ms | 0 |
| 04:00 | 0 | 0.0 | 599 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live CreditorWatch badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
Scheduled ASIC maintenance affecting some platform features
The Australian Securities and Investments Commission (ASIC) will be performing scheduled maintenance during this window. Some CreditorWatch features that rely on ASIC data may be temporarily unavailable or delayed during this time. We expect normal service to resume once ASIC's maintenance is complete. Thank you for your patience.
Announced by CreditorWatch · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for CreditorWatch yet. Outages of 10 minutes or more get their own page here.
Having trouble with CreditorWatch?
One report per service every 10 minutes from this network. No account.
Follow CreditorWatch
Get an email when CreditorWatch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CreditorWatch alerts to Slack, Discord or a webhook — free.
About CreditorWatch
CreditorWatch, at creditorwatch.com.au, is one of the Cloud & developer services we monitor. CreditorWatch helps you onboard quickly, manage credit decisions effectively and safeguard your cash flow.
CreditorWatch publishes an official status page at status.creditorwatch.com.au; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 759 ms average, 469–1167 ms range across 13 successful checks.
Questions
Is CreditorWatch down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was CreditorWatch last down?
We have not recorded a public CreditorWatch incident since monitoring began 7 days ago.
What is CreditorWatch's uptime?
From our own checks: 100% over 7 days of checks.
How fast does CreditorWatch respond?
759 ms on average over the last 24 hours (469–1167 ms).
Does CreditorWatch have an official status page?
Yes, at https://status.creditorwatch.com.au.
CreditorWatch 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report CreditorWatch here at once, the problem is on CreditorWatch'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 CreditorWatch. 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.