Customers

Xovris at work on a real fault

Found, fixed and proved by Xovris on its own.

Start freeSee the cases

One fault, found, fixed and proven19 October 2026, 01:02:45 UTC

Xovris’s own systemCritical/checkout failing on northmerefreight.comFixed and proven

Before

  • HTTPS answers0 of 3
  • The checkout loads0 of 3

The one change

  1. northmerefreight.com A 198.51.100.66
  2. northmerefreight.com A 203.0.113.10

After

  • HTTPS answers3 of 3
  • The checkout loads3 of 3

XovrisOn its own

  1. Saw /checkout failing on northmerefreight.com
  2. northmerefreight.com now points to 198.51.100.66, changed 5 minutes ago
  3. Changed northmerefreight.com back, its undo kept
  4. Working again in 1.52 seconds
Shown on an example site – never a customer’s.

Example incidents, each investigated and fixed each with its day

Real-world faults worked end to end – the cause found, and the fix made wherever it was Xovris’s to make. Updated 2 October 2026.

When address book records (DNS) change, signing (DNSSEC) breaks, a provider has an outage or a server goes down, Xovris investigates end to end. Where the cause is in DNS, the fix is applied under your policy and confirmed by re-running the failed check; where the cause lies outside DNS, Xovris names it and says what to do next.

  • Every cause found, every fix working
  • A fix found, its proof running on a copy
  • A cause still being found
  • Outside what Xovris changes – named
  1. A wrong setting in the app’s configuration1
    Root cause found
    1 of 1
    Outside DNS, named
    1
  2. A service the app depends on went down1
    Root cause found
    1 of 1
    Outside DNS, named
    1
  3. An error thrown in the app’s own code3
    Root cause found
    3 of 3
    Fixed and proven
    After the fix, POST /total answered 200 instead of 500 (17 November 2026)
    Outside DNS, named
    3
  4. DNSSEC signatures broken1
    Root cause found
    1 of 1
    Outside DNS, named
    1
  5. A DNS record pointed somewhere else2
    Root cause found
    2 of 2
    Fixed and proven
    2 of 2
    Outside DNS, named
    0
  6. A record restored to a version that was itself broken1
    Root cause found
    1 of 1
    Fixed and proven
    1 of 1
    Outside DNS, named
    0
  7. The hosting provider’s own outage2
    Root cause found
    2 of 2
    Outside DNS, named
    2
  8. The server behind the site went down1
    Root cause found
    1 of 1
    Outside DNS, named
    1
The same, as a table
Example incidents, each investigated and fixed – 2 October 2026. A dash under Fixed: Nothing of Xovris’s to change – cause named.
Kind of incidentIncidentsRoot cause foundFixed and provenOutside DNS, named
A wrong setting in the app’s configuration11 of 1nothing to change1
A service the app depends on went down11 of 1nothing to change1
An error thrown in the app’s own code33 of 3500 → 2003
DNSSEC signatures broken11 of 1nothing to change1
A DNS record pointed somewhere else22 of 22 of 20
A record restored to a version that was itself broken11 of 11 of 10
The hosting provider’s own outage22 of 2nothing to change2
The server behind the site went down11 of 1nothing to change1

Worked cases measured, with their day

Customers’ own stories join these as they choose to share them.

  • xovris.ai, checked by Xovris

    Xovris runs these public checks on your sites for you, each with the time it ran.

    Measured
    Every check fine
    When
    18 November 2026, 23:05:28 UTC
    See this check on the home page
  • A Next.js app connected with one command

    The wizard found the framework, signed in through the browser, wrote the configuration and waited until the first event was stored – no key copied at any point.

    Measured
    1 command typed, 0 keys copied by hand
    When
    15 November 2026, 22:49:52 UTC
    Watch the setup

Your setup could be the next case

Start free

Words on this page, in plain English

Each technical word this page uses, said simply.

Secure web connection (HTTPS)
The encrypted way a browser and a website talk, so nobody on the way can read or change what passes – the padlock in a browser.

Ask Xovris

Open the full page