Websites

Know your website works for every visitor – and why when it does not

Checked from outside, the way a visitor reaches you.

Check yours nowSee the plans

Xovris at workReplaying work Xovris has done

Noticed by Xovris

Is xovris.ai answering for everyone?

  1. Asked it from every place Xovris checks from, at once
  2. 95 ms from South Africa up to 365 ms from United States

Answering everywhere

Read while this page was built

Noticed by Xovris

api.xovris.ai outgrew the database server it shared

  1. Found the cause: connections held open on a shared database server
  2. Moved the database onto a dedicated core of its own

Put right on 23 October – answering in 10–74 ms since

Noticed by Xovris

Something new joined the network at 192.168.1.30

  1. Looked over the whole network – 7 devices answered
  2. Named it HP LaserJet Pro M404: it answers a print service (ports 80, 631, 9100)

HP LaserJet Pro M404 is on the map with everything else

  • Router
  • Dell
  • 192.168.1.21
  • Synology DiskStation
  • Philips hue - bridge
  • Network Camera
  • HP LaserJet Pro M404

Asked

“A synth keyboard I can play with the mouse or my computer keys, with a choice of waveform, volume and a little echo”

  1. Wrote it – 4 files, 55 KB
  2. Running, exactly as it came out

Live – use it, or keep building it

Asked

“npx xovris init”

  1. Found Next.js, using npm.
  2. Signed in to acme
  3. Created an ingestion-only key
  4. Wrote 5 changes; each is listed in .xovris/manifest.json
  5. Xovris received the test event
  6. Telemetry received – your first event is in Xovris

Xovris is installed. Remove it any time with npx xovris remove.

$ npx xovris init
✓ install @xovris/next with npm
✓ create instrumentation.ts
✓ create instrumentation-client.ts
✓ create app/xovris/route.ts
✓ set XOVRIS_INGEST_URL, XOVRIS_INGEST_KEY, NEXT_PUBLIC_XOVRIS_INGEST_URL, NEXT_PUBLIC_XOVRIS_INGEST_KEY, NEXT_PUBLIC_XOVRIS_TUNNEL in .env.local

Asked

“A 3D viewer for a wristwatch I can rotate and zoom, with strap colour options and a close-up of the dial”

  1. Wrote it – 5 files, 76 KB
  2. Drew it in 3D, right in the browser
  3. Running, exactly as it came out

Live – use it, or keep building it

Noticed by Xovris

POST /total started failing – TypeError: Cannot read properties of undefined (reading 'valueOf')

  1. Traced it to lib/total.js, line 5
  2. Found the change that caused it: “Read the quantity straight from the order line (#212)”
  3. Ran the failing request on that change and on the one before, to be sure
  4. Took back what that change did in lib/total.js
  5. Opened a pull request with the fix

POST /total answers again

· 43 s start to finish

lib/total.js
4- const qty = item.qty;
4+ const qty = item.quantity;

Asked

“A 3D solar system I can orbit and zoom with the mouse, with each planet labelled and a slider for how fast time runs”

  1. Wrote it – 4 files, 66 KB
  2. Drew it in 3D, right in the browser
  3. Running, exactly as it came out

Live – use it, or keep building it

Asked

“A booking page for my hair salon with prices, opening hours and a contact form”

  1. Built in 27.6 s
  2. Then asked“Make it feel more luxurious - a deep charcoal background with warm gold accents - and add a gallery of my work”
  3. Changed in 17 s – the same page, carried on
  4. Then asked“Let people choose a stylist and a time slot when they book”
  5. Changed in 40.6 s – the same page, carried on

One page, carried on from each message to the next

  1. The page as it stood at 00:31:03 UTCAt 00:31:03 UTC
  2. The page as it stood at 00:31:20 UTCAt 00:31:20 UTC
  3. The page as it stood at 00:32:01 UTCAt 00:32:01 UTC
Keep building it

Asked

“A drum machine with a 16-step grid, kick, snare, hi-hat and clap sounds, tempo control, and play and stop”

  1. Wrote it – 5 files, 43 KB
  2. Running, exactly as it came out

Live – use it, or keep building it

Noticed by Xovris

greenhouse-controller stopped working

  1. Read 11 records from 2 sources
  2. Found the cause: greenhouse-controller's firmware channel changed from stable to nightly at 01:48 UTC, 12 minutes before greenhouse-controller first failed
  3. Put greenhouse-controller back to stable, its last good setting

greenhouse-controller is back on its last good setting

greenhouse-controller · firmware channel

stable

Asked

“A music player page for a band's new EP with track list, play and pause, a progress bar and tour dates”

  1. Wrote it – 16 files, 3,450 KB
  2. Running, exactly as it came out

Live – use it, or keep building it

Asked

“Start the network map from our NetBox”

  1. Read NetBox 4.7.3: 2 devices with their sites and cables
  2. Matched 1 of them to a device Xovris reads itself
  3. Marked 2 that differ from what is really there

The map stands, and what differs is marked on it

Asked

“A 3D spinning product viewer for a pair of trainers that I can rotate with the mouse, with colour options”

  1. Wrote it – 8 files, 7,729 KB
  2. Drew it in 3D, right in the browser
  3. Running, exactly as it came out

Live – use it, or keep building it

Noticed by Xovris

A switch’s link to its router went down

  1. Read the switch and its router – 17 reads in 73 s
  2. Found it: port 1 was shut by the switch’s own loop protection, a second cable closing a loop
  3. Said which cable to pull, then turned the port back on the moment the loop was gone

The link is back up and the router answers again

Port 1 – the link to the router

ShutBack on

Asked

“Look over this firewall’s set-up”

  1. Read its whole set-up through its own sign-in, changing nothing
  2. Found 3 things to tighten
  3. Tightened 1 thing and read each change back

Safer than it was, each change read back

Xovris checks your address, HTTPS answer, certificate and pages from outside, the way a visitor reaches you, and tells you in plain words what changed and what to do.

Websites, installed by Xovris

Out of 324 listed for this area; 2,021 ready to connect in all

Search the Websites ones
xovris.ai answers from 6 of the places Xovris askedRead 18 November 2026 23:05:29 UTC
  • Answering from everywhere Xovris checks
  • Answered first95 ms
  • Slowest365 ms

XovrisOn its own

  1. xovris.ai, asked from every location Xovris uses
  2. 6 of 6 answered
  3. Slowest: United States, 365 ms
  4. Checks again on a schedule from the same places
Technical detail
  • Germany, DE50.48, 12.37328 ms
  • United States, US42.89, -78.88365 ms
  • Brazil, BR-23.55, -46.64245 ms
  • Japan, JP35.69, 139.69124 ms
  • Australia, AU-33.77, 150.9195 ms
  • South Africa, ZA-26.2, 28.0495 ms
Xovris’s check of xovris.ai from several places

What Xovris read on its own domain.

xovris.ai is served from Cloudflare, Inc., keeps its DNS on Cloudflare and keeps its email on Microsoft 365. Everything Xovris could read on xovris.ai answers as it should – none of 11 readings is wrong.

Websites on xovris.ai23:05:28 UTC
  • Address

    Fine

    Browsers can find it.

  • Secure connection (HTTPS)

    Fine

    Answered your browser over HTTPS in 74 ms.

  • Page from outside

    Fine

    Answered Xovris’s probe with 200 in 98 ms.

  • Certificate

    Fine

    Valid until 31 December 2026 – 42 days left.

  • Registration

    Fine

    Registered until 1 October 2028.

XovrisOn its own

  1. What Xovris sees on a domain, line by line.
  2. The values behind each answer, exactly as they were recorded.
  3. What a fix gives you: what broke, what changed and that it works again.
Technical detail
Address
104.21.72.44172.67.175.202606:4700:3035::6815:482c+1
Secure connection (HTTPS)
Answered your browser over HTTPS in 74 ms.
Page from outside
Answered Xovris’s probe with 200 in 98 ms.
Certificate
WE1
Registration
2028-10-01Cloudflare, Inc
xovris.ai, checked 18 November 2026, 23:05:28 UTC

What it watches, may change, and what stays yours.

Enter your website address. There is nothing to install and no account to connect.

What Xovris watches

  • The address answers – browsers can find you
  • The HTTPS answer and how long it took
  • The certificate: valid, trusted and when it expires
  • The page as a visitor gets it, with every redirect
  • The domain’s registration and expiry date

What Xovris puts right

  • A site that went offline brought back – its address, its certificate or its host put right, or your visitors sent to your standby while a provider is down and back once it recovers – with its way back ready first

What waits for your permission

  • Your site’s code (always as a pull request you review), content and hosting settings

Try it now, on your own.

Each of these runs in your own browser in seconds. Here is what each says for xovris.ai, checked 18 November 2026, 23:05:28 UTC – open one to run it on yours.

  • Website down checker

    xovris.ai: Address, Secure connection (HTTPS) and Page from outside – all fine.

  • Website speed test

    You get three ratings – loading, response and stability – each Good, Needs work or Poor, and the one change that helps most.

  • SSL certificate checker

    Certificate rules Only the certificate authorities named here may issue its certificates.

  • Security headers checker

    xovris.ai: grade A+, 130 points, no failing test.

  • Payment page script checker

    You get a list: each script, the site it loads from, whether it is pinned, and what is new since your last look.

What shipped for Websites, strongest first.

Each one looks after this area today, with the day it shipped and the plan it starts on.

Every feature

Lit: live and workingOpen: Xovris is still working on it

  • Every fix on autopilot, on every plan that includes fixing – proven before it runs, and put back if it does not hold

    Xovris now fixes on its own on every plan that includes fixing.

    Shipped 3 October 2026From PersonalAsk

  • One bar on every open incident: fix it, show me first, call me or handle it

    Every open incident ends with the four choices a person actually makes – let Xovris fix it, see the fix first, be called, or have Xovris handle it from now on – the same from the app, the alert email or Slack.

    Shipped 2 October 2026From PersonalAsk

  • A Fix Report in plain words for every fix

    What was wrong, how it was found, what changed and the before and after side by side – plain words first, the technical line under each, built only from the incident’s own records.

    Shipped 2 October 2026From PersonalAsk

  • Every incident has a live tracker, like a parcel delivery

    Detected, cause found, fix ready, approved, applied, verified – each step appears when its record exists, with its time, so you always know where a problem stands.

    Shipped 2 October 2026From PersonalAsk

  • Problems solved before are recognised – and nothing that already failed is tried twice

    A new incident shows the earlier ones like it and why.

    Shipped 2 October 2026From PersonalAsk

  • A fix counts only once your own problem is gone

    Your own failing outcome is reproduced before anything changes and run again after the fix, with the checks around it, and re-checked later; a fix that does not pass is put back and the next approach starts, and you pay nothing for it until the after-test passes.

    Shipped 2 October 2026From PersonalAsk

  • A fix counts only when your own journey works again, and one that does not is put back

    After a repair your own journey is run again – the site’s address with the status and words it must answer, or the check that first failed – and only that pass marks the incident fixed and verified.

    Shipped 9 October 2026From BusinessAsk

  • A wide change goes to one place first

    A change that touches several places goes to one first, is checked against your own uptime and error rates, and is put back automatically if anything gets worse – the other places are never touched.

    Shipped 2 October 2026From BusinessAsk

Check yours, right here.

This is the same check Xovris keeps running once you keep watching. It runs in your browser now, and nothing is saved to an account.

Check yours

Read here, in your own browser. Xovris keeps nothing of it.

Questions

Does Xovris need access to my accounts to watch?

No. Watching needs nothing beyond what anyone on the internet can see. When you want Xovris to fix things, you grant access scope by scope, for as many zones and projects as you choose.

What does the free plan include?

Watching and alerts, free for good. Personal adds fixing: Xovris puts problems right, and an issue counts only once it works again.

Can I undo a fix?

Yes. Every fix has its undo written down before it runs, and a fix that fails its after-test is undone automatically.

Is my data used to train AI?

No. Your data is never used to train our AI. Your systems, files, logs and settings stay yours: they are never used to train any AI, ours or anyone else’s, and nothing of yours ever reaches another customer.

Words on this page, in plain English

Each technical word this page uses, said simply.

Plain-text data (JSON)
A common way of writing data as named values, readable by people and programs alike.
Data an app reports about itself (telemetry)
The errors, timings and records an app sends out so problems can be spotted and explained.
Domain Name System (DNS)
The internet’s address book: it turns a name you type into the number of the computer that answers for it.

Ask Xovris

Open the full page