User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
123-reg.co.uk · Cloud & developer
Is 123 Reg down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft Office 365 Email Outage
Source: the vendor's status page · We are not affiliated with 123 Reg.
What to try while 123 Reg is having problems
Estimated fix: Not enough 123 Reg history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9 h; 83 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
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 → 123-reg.co.uk—
Your browser → us—
Our checksReaching it
Official · ReportsMajor incident · 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 40 min ago. Last stored result reached it in 881 ms.
Official status
Major incident
Microsoft Office 365 Email Outage Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 07 | 0 | 0.0 | 911 ms | 0 |
| Tue 09 | 0 | 0.0 | 424 ms | 0 |
| Tue 11 | 0 | 0.0 | 1053 ms | 0 |
| Tue 13 | 0 | 0.0 | 1188 ms | 0 |
| Tue 15 | 0 | 0.0 | 314 ms | 0 |
| Tue 17 | 0 | 0.0 | 765 ms | 0 |
| Tue 20 | 0 | 0.0 | 779 ms | 0 |
| Tue 22 | 0 | 0.0 | 374 ms | 0 |
| Wed 00 | 0 | 0.0 | 1501 ms | 0 |
| Wed 02 | 0 | 0.0 | 721 ms | 0 |
| Wed 05 | 0 | 0.0 | 1170 ms | 0 |
| Wed 07 | 0 | 0.0 | 1212 ms | 0 |
| Wed 09 | 0 | 0.0 | 1528 ms | 0 |
| Wed 11 | 0 | 0.0 | 871 ms | 0 |
| Wed 13 | 0 | 0.0 | 595 ms | 0 |
| Wed 15 | 0 | 0.0 | 860 ms | 0 |
| Wed 18 | 0 | 0.0 | 596 ms | 0 |
| Wed 20 | 0 | 0.0 | 733 ms | 0 |
| Wed 22 | 0 | 0.0 | 379 ms | 0 |
| Thu 00 | 0 | 0.0 | 1226 ms | 0 |
| Thu 02 | 0 | 0.0 | 746 ms | 0 |
| Thu 04 | 0 | 0.0 | 2664 ms | 0 |
| Thu 06 | 0 | 0.0 | 1128 ms | 0 |
| Thu 08 | 0 | 0.0 | 910 ms | 0 |
| Thu 09 | 0 | 0.0 | 1257 ms | 0 |
| Thu 11 | 0 | 0.0 | 304 ms | 0 |
| Thu 13 | 0 | 0.0 | 379 ms | 0 |
| Thu 15 | 0 | 0.0 | 1983 ms | 0 |
| Thu 17 | 0 | 0.0 | 825 ms | 0 |
| Thu 19 | 0 | 0.0 | 1218 ms | 0 |
| Thu 22 | 0 | 0.0 | 753 ms | 0 |
| Fri 00 | 0 | 0.0 | 1282 ms | 0 |
| Fri 02 | 0 | 0.0 | 412 ms | 0 |
| Fri 04 | 0 | 0.0 | 1558 ms | 0 |
| Fri 06 | 0 | 0.0 | 1564 ms | 0 |
| Fri 08 | 0 | 0.0 | 1063 ms | 0 |
| Fri 09 | 0 | 0.0 | 543 ms | 0 |
| Fri 10 | 0 | 0.0 | 1240 ms | 0 |
| Fri 11 | 0 | 0.0 | 561 ms | 0 |
| Fri 12 | 0 | 0.0 | 846 ms | 0 |
| Fri 14 | 0 | 0.0 | 1381 ms | 0 |
| Fri 16 | 0 | 0.0 | 471 ms | 0 |
| Fri 18 | 0 | 0.0 | 1005 ms | 0 |
| Fri 20 | 0 | 0.0 | 865 ms | 0 |
| Fri 22 | 0 | 0.0 | 866 ms | 0 |
| Sat 00 | 0 | 0.0 | 1489 ms | 0 |
| Sat 02 | 0 | 0.0 | 334 ms | 0 |
| Sat 03 | 0 | 0.0 | 1440 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 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live 123 Reg 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 123 Reg yet. Outages of 10 minutes or more get their own page here.
Having trouble with 123 Reg?
One report per service every 10 minutes from this network. No account.
Follow 123 Reg
Get an email when 123 Reg goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send 123 Reg alerts to Slack, Discord or a webhook — free.
About 123 Reg
We track 123 Reg (123-reg.co.uk) as part of the Cloud & developer group. Find a domain, build a website, and launch your business in minutes — powered by the UK’s web hosting experts.
123 Reg publishes an official status page at status.123-reg.co.uk; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 1002 ms average, 334–1998 ms range across 17 successful checks.
Questions
Is 123 Reg down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft Office 365 Email Outage
When was 123 Reg last down?
We have not recorded a public 123 Reg incident since monitoring began 9 days ago.
What is 123 Reg's uptime?
From our own checks: 100% over 9 days of checks.
How fast does 123 Reg respond?
1002 ms on average over the last 24 hours (334–1998 ms).
Does 123 Reg have an official status page?
Yes, at https://status.123-reg.co.uk.
123 Reg 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 123 Reg here at once, the problem is on 123 Reg'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 123 Reg. 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.