System status
Every five minutes a scheduled job asks the site for its home page, a fixture page and its download, the search index and a database health check, and records what came back. The results below come from those records. The job runs on the same platform that serves the site, so a complete outage stops it too: that shows here as missing data, in grey, never as green.
Asking the site for its latest checks…
What each part depends on
| Part | Depends on | What happens if it fails |
|---|---|---|
| Pages and catalogue | Vercel's servers and CDN | Public pages are built at deploy time or rendered on first request, then shared from the CDN. Fixture pages do not read the account database. |
| File downloads | Static files on the CDN | Immutable, long-cached files under /files/. Same availability as the pages themselves. |
| Search | Your browser | Runs in your browser against an index built at deploy time. There is no search server to time out. |
| Editors and studios | Your browser | Every workspace runs locally and uploads nothing, so nothing server-side can break an edit in progress. Saving a draft to an account needs the accounts service. |
| Accounts and saved work | A hosted database (Turso) | Sign-in, your account, saved fixtures and saved drafts. If the database is down you cannot sign in or open saved work; everything else keeps working. |
| Status checks | A scheduled job on Vercel | Checks the pages, a download, search and the database every five minutes and records the results. If the job stops, this page shows the gap as no data. |
| Form demo endpoint | One serverless function | POST /api/demo-submit makes the live form demos confirm. It stores nothing; if it fails, only those confirmations stop. |
| Fonts | Nothing at runtime | Typefaces are downloaded at build time and self-hosted, so there is no third-party font request to hang. |
| Analytics | Google, after consent | Loaded only once the analytics consent category is enabled. Blocked, failing, or disabled, it changes nothing about the content. |
| Advertising | Adsterra, after consent | Requested from the browser only while the advertising consent category is on, never on legal or account screens. Blocked or failing, ads simply do not appear, downloads still go ahead and nothing else changes. |
| Offline shell | Your browser's service worker | A cached app shell keeps previously visited public pages and the offline page rendering with no network at all. Account pages are never cached. |
Checking upstream yourself
The site is hosted on Vercel, which publishes its own live status. If pages are not loading at all, that is the first place to look:
Advertising and analytics load after the page and cannot affect whether the content loads. If ads are missing, the content is not broken; see cookie preferences.
Planned maintenance
When work is planned, a notice appears at the top of the results above. Deploys are atomic: a new build replaces the old one at the edge with no downtime window, and changes to the database are made to add to it, never to take the site offline.
What this build contains
These figures are counted from the catalogue at build time, so they describe the deployment you are looking at:
- 8,584 downloadable example files.
- 840 published visual templates.
- Content last materially updated: 2026-08-23. This is the date the library content changed, not the date of the last code deploy, the same value the sitemap reports to crawlers for static pages.
Report a problem
If something is broken, a download that 404s, a page that will not render, a preview that never loads, email examples@novusstreamsolutions.com with the URL, what you did, and your browser. The checks above cover a sample of pages, not every one of the Testaroo files, so a report from you is often how we find out.
Security issues follow a separate process: see the security policy. Accessibility barriers have their own reporting route on the accessibility statement. Everything else belongs on the contact page.