Status
Service and source status
Two different things can be wrong: the service can be down, or a source can be behind. The second is far more common and matters far more to your work, so this page covers both and is honest about what we do not yet publish.
Last updated September 10, 2026
What we publish, and what we do not
We do not run an automated public uptime page. We are not going to put a green tick on a page that nothing is checking. If the workspace is unreachable, email hello@718systems.com and you will get a person, not a status widget.
What we do publish is source health, in the product, on every page. That is the signal that actually affects a decision: not whether the site was up, but whether the data you are reading is current. Each page names the sources behind it, the date they run through, when they were last read, and whether any of them is outside its expected window.
The four states a source can be in
Current
Read on schedule, and the source's own data runs through a date inside its expected window. Nothing to think about.
Delayed
Either the agency has not published (source reporting delay) or our read has not completed on schedule (system update delayed). The two are labelled separately because only one of them is ours to fix.
Partial
A read completed but returned less than expected. The prior data is kept rather than overwritten with a short load, and the page says so.
Unavailable
No successful read on record. The source is shown as having no coverage rather than silently reporting zero results.
A delayed source is never hidden and never guessed around. We would rather show you a figure marked a month old than a fresh-looking number that is not.
Checkpoint — September 10, 2026
Of the 45 sources in Data Coverage, 33 were current and 12 were outside their expected window on the date of the last audit. This is a dated checkpoint, not a live reading — the authoritative view is inside the workspace at interchange.718systems.com, which re-reads each source on the cadence Data Coverage publishes for it. Nothing here updates in real time.
| Source | Agency | Reason | Current through | Expected refresh |
|---|---|---|---|---|
| Procurement Notices & Awards | NYC City Record | Source reporting delay | Sep 4, 2026 | Daily |
| Contract Reporter notices | NYS Contract Reporter | System update delayed | Sep 4, 2026 | Daily |
| RFx solicitations | NYC PASSPort | System update delayed | Sep 7, 2026 | Daily |
| Contracts | NYC PASSPort | System update delayed | Sep 7, 2026 | Daily |
| Vendor registry | NYC PASSPort | System update delayed | Sep 7, 2026 | Daily |
| M/WBE Certified Businesses | NYC SBS | Source reporting delay | Aug 18, 2026 | Weekly |
| M/WBE Upcoming Procurements | NYC SBS | Source reporting delay | Jul 2, 2026 | Weekly |
| Approved Permits | NYC DOB NOW | Source reporting delay | Sep 4, 2026 | Daily |
| DOB NOW Certificates of Occupancy | NYC DOB | System update delayed | Sep 3, 2026 | Daily |
| DOB NOW Safety Boiler | NYC DOB | System update delayed | Sep 4, 2026 | Daily |
| ACP Search Portal (live ACP7) | NYC DEP | System update delayed | Sep 9, 2026 | Every 6 hours |
| Certified Investigators | NYC DEP | Source reporting delay | Oct 22, 2025 | Weekly |
A source sitting behind is normal and usually not a fault: several agencies publish in monthly or quarterly bursts, and a feed that is read daily can still be weeks behind because that is how often it is released. The per-source limitation column in Data Coverage explains which of these are structural.
Reporting a problem
- Cannot sign in
- hello@718systems.com — include the email address on the account.
- Data looks stale
- Check the freshness line at the bottom of the page first; it names the source and the date. If it disagrees with the agency, tell us which page and which source.
- A record looks wrong
- Send the record identifier. See Data Methodology for how corrections are handled.
If we take on a contractual availability commitment, it is written into an Enterprise agreement rather than asserted on a page. See Terms.