Incident log
Every fault we have recorded, including the ones no customer could have noticed. Entries are added by hand and never removed.
The log begins on November 6, 2026, when this version of Juriset began serving. It makes no claim about anything earlier. No customer-visible outage is recorded across 3 entries; 1 is still open. Live availability and planned maintenance are on the status page; corrections to published values are on the track record.
- Source · 2: an official source we cite changed or went away under us
- Prevented · 1: a fault caught before it reached anyone
Alabama's termination-law page was removed
November 8, 2026 · Source · open · Migration 0016
- What a customer saw
- Alabama's termination notice rule is still served as last verified on October 29, 2026, with the snapshot taken then, but it cannot be re-checked against a live page.
- What happened
- The Alabama labor market information page "Job Termination Laws" answers 404 since that site was redesigned. No successor page was found on the labor market information or Department of Workforce sites.
- How it was found
- A fetch of the page returned 404.
- What is being done
- Open. The source is marked inactive so it is no longer crawled, while we look for the official page that replaces it.
A Saskatchewan host stopped sending part of its certificate chain
November 6, 2026 · Source · closed November 8, 2026 · Decision 0028
- What a customer saw
- Values kept being served with their citations, but the two Saskatchewan statute and regulation sources could not be re-checked from November 6 to 8. Their last confirmed fetch was October 29.
- What happened
- publications.saskatchewan.ca stopped sending its intermediate certificate. Browsers fetch a missing intermediate on their own; our crawler does not, so it could not read robots.txt and treated the whole host as off limits, as its politeness rules require.
- How it was found
- The crawler reported the host's robots.txt as unreachable.
- Closed by
- The crawler now carries the public intermediate certificates such hosts leave out. Certificate verification is unchanged and still ends at a trusted root.
Two parallel changes gave the database schema two heads
November 6, 2026 · Prevented · closed November 6, 2026 · Pull request #13
- What a customer saw
- Nothing. Production was not affected, and staging kept serving the previous release.
- What happened
- Two changes merged the same morning each added a database migration numbered 0007, so the migration history forked. The checks on main failed and staging was not updated.
- How it was found
- The migration check that runs on every change.
- Closed by
- One migration was renumbered 0008 the same morning, and staging deployed once the checks passed.
Seen something we missed? Write to support@juriset.dev, or report a value from its page.