The app residents use for their tenancy, payments and building. It covers rent and statements, maintenance requests, parcels, amenity bookings and resident chat. Residents reach it on a phone and in a browser, and it talks to the estate through the Frontend API rather than the database directly. If this is down residents cannot pay, report a fault or book anything, though the building itself carries on working.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Frontend.Api 0 error(s), 0 fault(s) Errors this app wrote to the log, and how many DISTINCT faults they were - one fault repeating and twenty separate ones mean very different things.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
Staff Portal
The staff-facing WookiVerse application, and the one the on-site team lives in all day. Lettings, residents, maintenance, inspections, finance and reporting are all here. Unlike the resident app it connects straight to the database, so its health is a fair proxy for the database being reachable. When this is down the building keeps running, but nobody can record anything about it.
Measured .
Backend.BlazorApp 0 error(s), 0 fault(s) Errors this app wrote to the log, and how many DISTINCT faults they were - one fault repeating and twenty separate ones mean very different things.OK
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
Backend API
Bulk import and export for power users. It is how spreadsheets of rooms, residents or rates get into WookiVerse, and how data gets pulled back out again. It is deliberately separate from everything the apps use, so it can be busy or broken without a resident or a staff member noticing. It also answers the per-component health checks the rest of this page is built on.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
Booking Portal
Where prospective residents search, book and sign. It carries the whole funnel: search and availability, the basket, identity and right-to-rent checks, contracts and signing, and the first payment. Marketing content and the operator landing pages are served from here too. It is the one component on this page that directly costs money while it is broken, because a visitor who cannot book usually does not come back later.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
Portals.Bookings 0 error(s), 0 fault(s) Errors this app wrote to the log, and how many DISTINCT faults they were - one fault repeating and twenty separate ones mean very different things.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
Nominations Portal
Where partner universities nominate and place students. University staff and agents sign in to submit nominations against an agreed allocation and to track who has been placed. It runs as its own portal with its own sign-in, separate from the resident and staff apps. It is seasonal by nature - quiet for much of the year, and business-critical for the few weeks around intake.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
Portals.Nominations.Api 0 error(s), 0 fault(s) Errors this app wrote to the log, and how many DISTINCT faults they were - one fault repeating and twenty separate ones mean very different things.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
Shop Portal
The resident shop, where residents buy extras: bedding packs, cleaning, storage, parking and other add-ons. Orders placed here land on the resident account rather than being a separate transaction to chase. It shares its look and its payment path with the booking portal. If it is down residents cannot buy anything new, but nothing they have already bought is affected.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
Website
The public marketing site - the pages a visitor sees long before they reach the booking funnel. It is content managed, so most changes to it are made by the marketing team rather than by a deploy. It is the most visible thing on this list to somebody who has never heard of WookiVerse. Being down here stops no existing resident doing anything, but it does stop new ones arriving.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
Assistant
The AI assistant across text, voice and realtime. It answers resident questions in the app, speaks to callers through the phone system, and gives staff a natural-language way into their own data. It leans on several third-party model providers, so the Integrations component is worth reading beside this one. When it is unavailable the apps stay up and simply stop offering the assistant.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
Sign-in / SSO
Single sign-on across every WookiVerse application. Staff and partner sign-ins are brokered through here to Microsoft Entra, and the sessions it issues are what every other component trusts. This has the widest blast radius of anything on the page: when it is down, most things are technically running and nobody can get into them. Residents signing in to their own app use a different route and are far less affected.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
Telephony
Inbound and outbound calling, and the contact centre. Calls to the published building numbers arrive here to be routed, recorded and where needed translated live, and can be passed between staff. The phone side of the assistant runs through here as well. If it is down calls ring nowhere at all, which makes it the failure most likely to be noticed first by somebody outside the company.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
VoIP 0 error(s), 0 fault(s) Errors this app wrote to the log, and how many DISTINCT faults they were - one fault repeating and twenty separate ones mean very different things.OK
Live updates
Chat and instant updates that arrive without refreshing. It is what makes a new message, a status change or a moving dashboard appear on its own rather than on the next page load. Every app uses it and none of them depends on it to function. When it is down the product degrades quietly - everything still works, it just stops being live, and people start pressing refresh.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
response 0.01s How long the average real request took, measured by the platform rather than by us.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
SignalR 0 error(s), 0 fault(s) Errors this app wrote to the log, and how many DISTINCT faults they were - one fault repeating and twenty separate ones mean very different things.OK
Integrations
The third-party services WookiVerse calls: payments, messaging, AI, mapping and identity. These are outside our control, so this reports what each vendor publishes about itself rather than anything we can prove from here. A failure usually means one specific capability stops - cards, or texts, or address lookup - rather than an application going down. The checks below name the vendor, so this list is the quickest way to see which one it is.
Measured .
AnthropicOK
Api2PdfOK
Api2Pdf credit The prepaid credit with Api2Pdf, which renders invoices and contracts when the VM is full or away. An invoice costs a fraction of a cent, so a low figure is a top-up reminder rather than an outage.OK
Azure AIOK
Azure DevOpsOK
CloudflareOK
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
ElevenLabsOK
ElevenLabs credit What is left of the voice allowance the assistant speaks from.OK
Google Maps & PlacesOK
IPinfo allowance What is left of the month's address lookups.OK
LiveKitOK
Microsoft ClarityOK
Not monitored Vendors that publish no status feed we can read for free. Checking them would mean calling their APIs, which spends an allowance to learn what they will not tell us for nothing.OK
OneSignalOK
OpenAIOK
Prepaid balances How many of the vendors we pay in advance we were able to read a balance from, and how many of those are running low. Fewer than all of them means one could not be reached - which is not the same as one being empty, and is why the count is shown rather than only the balances.OK
ReplicateOK
StripeOK
TwilioOK
Twilio credit The prepaid credit with Twilio that pays for sending texts and taking calls, and roughly how many more texts it buys at this month's blended price.OK
YotiOK
Background processing
Billing runs, document rendering, inbound email, webhooks and the scheduled jobs: email and SMS notifications, rewards points, matching content to residents, scheduled inspections and the reception desk's opening hours. This is the work nobody is watching while it happens: raising invoices, turning contracts into PDFs, receiving mail and taking payment callbacks from Stripe. Because it is all asynchronous, an outage here is invisible for a while and then arrives at once, as a pile of things that should have happened and did not. The checks are per function, so the list below shows which piece of work has stopped.
Measured .
Automatic jobs The background host is executing timers at all, rather than merely serving HTTP.OK
Backend.FunctionApp 0 error(s), 0 fault(s) Errors this app wrote to the log, and how many DISTINCT faults they were - one fault repeating and twenty separate ones mean very different things.OK
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
Email & SMS notifications Queued emails and text messages are being sent.OK
Exchange rates The daily European Central Bank exchange rates are being fetched and stored.OK
Invoice & statement PDFs Invoices and statements are being rendered to PDF.OK
Matching content to residents Residents are being matched to the events, polls, notices and other content meant for them.OK
Monthly invoicing The nightly run that raises operator invoices completed.OK
Reception presence Staff presence is being kept up to date for the reception screen.OK
response 0.05s How long the average real request took, measured by the platform rather than by us.OK
Rewards points Points earned by residents are being awarded.OK
Scheduled inspections Scheduled inspections - daily, weekly, on check-in or check-out - are being raised when they fall due.OK
server errors 0.0% The share of real requests that failed with a server error, from Azure own metrics.OK
voip-bridgeOK
Scheduled tasks
The estate monitor and the log triage, which still run on a timer outside the apps they watch. The monitor checks every other component every quarter of an hour and is what publishes the detailed checks shown against everything else on this page, so when this is down the rest of the page may be out of date. The scheduled jobs that used to run here (notifications, rewards points and the rest) now run under Background processing.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
Database
The SQL database behind every application. Everything on this page bar the marketing site ultimately reads and writes here, which makes it the one dependency with no alternative path. It is reported by the applications that connect to it rather than probed on its own, so a green badge here is several apps independently agreeing they can reach it. If this is genuinely down, expect most of the rest of the page to follow within minutes.
Measured .
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
identity-headroomOK
Building devices & sync
Laundry, energy, thermostats and the jukebox, and the sync that feeds them. A virtual machine runs the integrations that talk to physical equipment in the buildings, on schedules of their own. When it stops, the equipment carries on doing whatever it was last told to do - the machines keep working, but WookiVerse stops knowing about them and stops being able to change them. Readings arriving late is the usual symptom, rather than anything visibly broken.
Measured .
Building device messagesOK
Cloud drive syncOK
Competitor price capture The service that reads competitor room prices is running and able to drive a browser.OK
Configuration The settings the app needs at startup are set, and the addresses it calls resolve.OK
Data sync Building data is syncing between the on-site machine and the cloud.OK
Database connection The app can open a connection to the database it reads and writes.OK
Database schema The tables and views this app depends on are present and the right shape.OK
Energy readings Meters are reporting consumption.OK
FTP uploadsOK
Jukebox The in-building jukebox is reporting what it is playing.OK
Laundry machines Washing machines are reporting whether they are in use.OK
Thermostat readings Thermostats are reporting temperature and setpoint.OK
VM.Competitors 0 error(s), 0 fault(s) Errors this app wrote to the log, and how many DISTINCT faults they were - one fault repeating and twenty separate ones mean very different things.OK
Resident AppOutage24 hoursTue 18 Aug 202675%
AssistantOutage14 hours 10 minutesFri 21 Aug 202666.67%
Building devices & syncOutage12:01 – 14:01 · 2 hours
Booking PortalOutage10:40 – 16:25 · 5 hours 45 minutes
Nominations PortalOutage10:40 – 16:30 · 5 hours 50 minutes
WebsiteOutage10:40 – 13:55 · 3 hours 15 minutesThu 27 Aug 202695.52%
Shop PortalDegraded20:35 – 20:50 · 15 minutes
Staff PortalDegraded20:20 – 20:50 · 30 minutes
Live updatesOutage17:00 – 17:05 · 5 minutes
Backend APIDegraded13:05 – 13:20 · 15 minutes
IntegrationsDegraded10:35 – 14:20 · 3 hours 45 minutesSun 20 Sept 202699.83%
Sign-in / SSO
Operational
Telephony
Operational
