Incident history
Every incident we have noticed that affected an answer, or the freshness of the data behind one: what went wrong, who it reached, and what changed so it cannot happen the same way twice. This page is written by hand and only carries what we found — the live measurement is on the status page, and the ninety-day strip there is counted from requests that reached us, so it cannot see an outage that stopped them arriving.
- Two datasets had stopped syncing and nothing said so
Two weekly data syncs were failing, and because a scheduled background task throws its output away, the failures left no trace anywhere. The datasets were missing from the status page before anyone noticed.
2026-09-08
- IP answers lost their location and network flags
Files a scheduled job had synced correctly were written into directories the web process could not enter, so IP lookups answered with no location and no network operator, and the datacenter, VPN and Tor flags read false.
2026-09-05
- Documentation and content pages answered 500 in production
A class the app loads at runtime was only installed for development, so every documentation page, content page and the sitemap failed on the production server while the lookup endpoints kept answering.
2026-09-03
Try it on your own data
Every Spaw account gets 10 free credits at the start of each month, no card. One key answers every signal these pages describe, and the pricing page has every billing rule in full.