Customers
Xovris at work on a real fault
Found, fixed and proved by Xovris on its own.
Xovris’s own systemCritical/checkout failing on northmerefreight.comFixed and proven
Before
- HTTPS answers0 of 3
- The checkout loads0 of 3
The one change
- northmerefreight.com A 198.51.100.66
- northmerefreight.com A 203.0.113.10
After
- HTTPS answers3 of 3
- The checkout loads3 of 3
XovrisOn its own
- Saw /checkout failing on northmerefreight.com
- northmerefreight.com now points to 198.51.100.66, changed 5 minutes ago
- Changed northmerefreight.com back, its undo kept
- Working again in 1.52 seconds
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
- A wrong setting in the app’s configuration1
- Root cause found
- 1 of 1
- Outside DNS, named
- 1
- A service the app depends on went down1
- Root cause found
- 1 of 1
- Outside DNS, named
- 1
- 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
- DNSSEC signatures broken1
- Root cause found
- 1 of 1
- Outside DNS, named
- 1
- A DNS record pointed somewhere else2
- Root cause found
- 2 of 2
- Fixed and proven
- 2 of 2
- Outside DNS, named
- 0
- 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
- The hosting provider’s own outage2
- Root cause found
- 2 of 2
- Outside DNS, named
- 2
- The server behind the site went down1
- Root cause found
- 1 of 1
- Outside DNS, named
- 1
The same, as a table
| Kind of incident | Incidents | Root cause found | Fixed and proven | Outside DNS, named |
|---|---|---|---|---|
| A wrong setting in the app’s configuration | 1 | 1 of 1 | nothing to change | 1 |
| A service the app depends on went down | 1 | 1 of 1 | nothing to change | 1 |
| An error thrown in the app’s own code | 3 | 3 of 3 | 500 → 200 | 3 |
| DNSSEC signatures broken | 1 | 1 of 1 | nothing to change | 1 |
| A DNS record pointed somewhere else | 2 | 2 of 2 | 2 of 2 | 0 |
| A record restored to a version that was itself broken | 1 | 1 of 1 | 1 of 1 | 0 |
| The hosting provider’s own outage | 2 | 2 of 2 | nothing to change | 2 |
| The server behind the site went down | 1 | 1 of 1 | nothing to change | 1 |
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
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
No case matches these filters yet.
Your setup could be the next case
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.