User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 15 min ago. Last stored result reached it in 568 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:00 | 0 | 0.0 | 391 ms | 0 |
| 11:00 | 0 | 0.0 | 576 ms | 0 |
| 12:45 | 0 | 0.0 | 587 ms | 0 |
| 14:45 | 0 | 0.0 | 655 ms | 0 |
| 16:45 | 0 | 0.0 | 624 ms | 0 |
| 17:45 | 0 | 0.0 | 614 ms | 0 |
| 18:45 | 0 | 0.0 | 578 ms | 0 |
| 20:30 | 0 | 0.0 | 637 ms | 0 |
| 21:00 | 0 | 0.0 | 596 ms | 0 |
| 23:00 | 0 | 0.0 | 452 ms | 0 |
| 01:00 | 0 | 0.0 | 602 ms | 0 |
| 03:00 | 0 | 0.0 | 562 ms | 0 |
| 05:15 | 0 | 0.0 | 572 ms | 0 |
| 05:30 | 0 | 0.0 | 560 ms | 0 |
| 07:15 | 0 | 0.0 | 568 ms | 0 |
| 08:30 | 0 | 0.0 | 585 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Bright Software Group 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 Bright Software Group goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Bright Software Group alerts to Slack, Discord or a webhook — free.
Bright Software Group, at brightsg.com, is one of the Money services we monitor. Award-winning payroll, tax, practice management, and accounting software for businesses across the UK and Ireland.
Bright Software Group publishes an official status page at status.brightsg.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 572 ms average, 391–655 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Bright Software Group incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
572 ms on average over the last 24 hours (391–655 ms).
Yes, at https://status.brightsg.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Bright Software Group here at once, the problem is on Bright Software Group'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 Bright Software Group. 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.