User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
realyse.com · Cloud & developer
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 35 min ago. Last stored result reached it in 327 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 06 | 0 | 0.0 | 349 ms | 0 |
| Tue 08 | 0 | 0.0 | 305 ms | 0 |
| Tue 10 | 0 | 0.0 | 364 ms | 0 |
| Tue 12 | 0 | 0.0 | 361 ms | 0 |
| Tue 15 | 0 | 0.0 | 361 ms | 0 |
| Tue 17 | 0 | 0.0 | 308 ms | 0 |
| Tue 19 | 0 | 0.0 | 995 ms | 0 |
| Tue 21 | 0 | 0.0 | 350 ms | 0 |
| Wed 00 | 0 | 0.0 | 816 ms | 0 |
| Wed 02 | 0 | 0.0 | 388 ms | 0 |
| Wed 04 | 0 | 0.0 | 346 ms | 0 |
| Wed 06 | 0 | 0.0 | 382 ms | 0 |
| Wed 09 | 0 | 0.0 | 388 ms | 0 |
| Wed 11 | 0 | 0.0 | 362 ms | 0 |
| Wed 13 | 0 | 0.0 | 304 ms | 0 |
| Wed 15 | 0 | 0.0 | 365 ms | 0 |
| Wed 17 | 0 | 0.0 | 401 ms | 0 |
| Wed 19 | 0 | 0.0 | 343 ms | 0 |
| Wed 22 | 0 | 0.0 | 327 ms | 0 |
| Thu 00 | 0 | 0.0 | 329 ms | 0 |
| Thu 02 | 0 | 0.0 | 299 ms | 0 |
| Thu 04 | 0 | 0.0 | 516 ms | 0 |
| Thu 06 | 0 | 0.0 | 329 ms | 0 |
| Thu 08 | 0 | 0.0 | 302 ms | 0 |
| Thu 10 | 0 | 0.0 | 345 ms | 0 |
| Thu 12 | 0 | 0.0 | 450 ms | 0 |
| Thu 14 | 0 | 0.0 | 1075 ms | 0 |
| Thu 16 | 0 | 0.0 | 376 ms | 0 |
| Thu 18 | 0 | 0.0 | 996 ms | 0 |
| Thu 20 | 0 | 0.0 | 380 ms | 0 |
| Thu 22 | 0 | 0.0 | 300 ms | 0 |
| Fri 00 | 0 | 0.0 | 286 ms | 0 |
| Fri 02 | 0 | 0.0 | 301 ms | 0 |
| Fri 04 | 0 | 0.0 | 411 ms | 0 |
| Fri 06 | 0 | 0.0 | 337 ms | 0 |
| Fri 08 | 0 | 0.0 | 358 ms | 0 |
| Fri 10 | 0 | 0.0 | 271 ms | 0 |
| Fri 12 | 0 | 0.0 | 341 ms | 0 |
| Fri 14 | 0 | 0.0 | 365 ms | 0 |
| Fri 17 | 0 | 0.0 | 278 ms | 0 |
| Fri 19 | 0 | 0.0 | 368 ms | 0 |
| Fri 21 | 0 | 0.0 | 298 ms | 0 |
| Fri 22 | 0 | 0.0 | 414 ms | 0 |
| Sat 00 | 0 | 0.0 | 333 ms | 0 |
| Sat 01 | 0 | 0.0 | 278 ms | 0 |
| Sat 03 | 0 | 0.0 | 330 ms | 0 |
| Sat 05 | 0 | 0.0 | 392 ms | 0 |
| Sat 07 | 0 | 0.0 | 327 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for REalyse 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 REalyse goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send REalyse alerts to Slack, Discord or a webhook — free.
REalyse, at realyse.com, is one of the Cloud & developer services we monitor. REalyse provides UK residential property data, comparables, planning context and market analytics for investment, lending, advisory and public-sector teams.
REalyse publishes an official status page at status.realyse.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 336 ms average, 271–414 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public REalyse incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
336 ms on average over the last 24 hours (271–414 ms).
Yes, at https://status.realyse.com.
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 REalyse here at once, the problem is on REalyse'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 REalyse. 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.