Data status

Trademark data status

Every night we check Goalie IP's own daily-refreshed copy of the USPTO trademark register, and our weekly-refreshed copy of Canada's CIPO register, for freshness, completeness, and accuracy. The checks run against the same database that our search, API, and MCP tools use.

Pass All checks passed.

Report generated November 12, 2026 at 1:49 PM UTC.

Latest checks

StatusCheckResult
PassU.S. data is currentLatest USPTO daily file loaded: 2026-11-11 (loaded 2026-11-12 10:58 UTC), 1 day(s) before today.
PassNo missing U.S. filesEvery daily file the USPTO lists (680, from 2025-01-01) is loaded, plus 90 parts of the USPTO's annual backfile (1884 onward).
PassDaily files match the sourceThe last 10 daily file(s) were checked against the production database while the source file was on hand: all 388,277 records present and current, and 500 sampled records matched field for field.
PassProduction matches the verification copyThe production database and the independent verification copy agree for every record in the last 10 daily file(s).
PassCanadian data is currentLatest CIPO weekly release loaded: 2026-11-04, 8 day(s) before today.
PassRecords match the USPTO's own record11,695 randomly chosen records checked in the last 30 days were compared with the USPTO's own case record (TSDR): 99.85% matched on every field checked, 0.07% differed only because the USPTO updated the case after our latest daily file, and 0.09% differed otherwise (95% range 0.05–0.16%). Differences by field: status 9, status date 9, mark text 1.
PassNo gaps in serial-number rangesNo run of more than 100 consecutive missing serial numbers in the 50-series, 98-series, 99-series (USPTO serial numbers are issued in order, so a long run would mean missing records); 50: 197,008 records, 95.63% of the numbers in use; 98: 941,260 records, 97.26% of the numbers in use; 99: 933,277 records, 98.45% of the numbers in use.
PassEvery record matches the verification copyAll 14,411,325 U.S. records were fingerprinted on both the production database and the independent verification copy; they are identical.
InfoRegister totals14,418,986 U.S. applications and registrations (4,648,982 live); 2,196,164 Canadian records.
PassFields are populatedKey fields are populated at their usual rates.

History

Last 90 days, oldest on the left: 16 passed, 0 needed attention, 0 failed; reports began 2026-10-27.

Accuracy against the USPTO's own record

Every night, 400 records are chosen at random from our production database and compared with the USPTO's case record for the same serial number (TSDR). Fields compared: registration number, filing date, registration date, status, status date, mark text, owner, classes. A difference counts as lag, not error, when the USPTO updated the case after our latest daily file.

Records compared (last 30 days)11,695
Matched on every field99.85%
Differed only because the USPTO updated the case after our latest file0.07%
Differed otherwise (95% range)0.09% (0.05–0.16%)
Field that differedRecords
status9
status date9
mark text1

Every difference in the current sample

A record counts as a difference when our copy and the USPTO's case record disagree on a compared field and the USPTO shows no later activity on the case that would explain it. We list each one, with both values, so you can see exactly what differed. A common cause is a status change the USPTO recorded on the same day it produced its daily file, after the file was prepared, and that no later daily file carried.

Serial numberFieldOur copyUSPTO case record (TSDR)
98907749
checked 2026-11-03
status661 (response after non-final action - entered)645 (final refusal - mailed)
status date2025-09-042026-09-22
99251697
checked 2026-11-03
status688 (notice of allowance - issued)606 (abandoned - no statement of use filed)
status date2026-02-032026-09-07
88593166
checked 2026-10-29
status700 (registered)701 (section 8-accepted)
status date2020-02-042026-08-19
88744033
checked 2026-10-29
status700 (registered)702 (section 8 & 15-accepted and acknowledged)
status date2020-07-282026-09-05
97705953
checked 2026-10-29
status661 (response after non-final action - entered)641 (non-final action - mailed)
status date2026-08-182026-09-22
98884367
checked 2026-10-29
status645 (final refusal - mailed)602 (abandoned-failure to respond or late response)
status date2026-05-052026-08-19
99576056
checked 2026-10-29
status616 (revived - awaiting further action)645 (final refusal - mailed)
status date2026-08-142026-08-19
99835382
checked 2026-10-29
status638 (new application - assigned to examiner)653 (suspension letter - mailed)
status date2026-09-152026-09-22
99835389
checked 2026-10-29
status638 (new application - assigned to examiner)641 (non-final action - mailed)
status date2026-09-182026-09-22
99840537
checked 2026-10-29
mark textP(blank)

Recent daily files, checked record by record

The USPTO publishes a file of changed records every day. Right after each file is loaded, and before the file is discarded, we look up every record in it in our production database. A record is “out of date” if we hold an older version than the file. Then 50 records are picked at random and compared field by field.

USPTO daily fileRecords in fileMissingOut of dateSampled fields matched
apc261111.xml29,6560050 / 50
apc261110.xml62,9810050 / 50
apc261109.xml60,3260050 / 50
apc261108.xml12,7240050 / 50
apc261107.xml7,3300050 / 50
apc261106.xml19,6030050 / 50
apc261105.xml28,5370050 / 50
apc261104.xml41,8620050 / 50
apc261103.xml65,9070050 / 50
apc261102.xml59,3510050 / 50

Serial-number coverage

The USPTO issues serial numbers in order within each series, so a long run of numbers missing from our copy would mean missing records. Short gaps are normal, because some numbers are never used. Checked weekly, most recently on 2026-11-08.

SeriesRange checkedRecordsNumbers in useRuns of 100+ missing
5050000003–50206011197,00895.63%0
9898000000–98967800941,26097.26%0
9999000001–99948011933,27798.45%0

Known limitations

How the checks work

The same report is available as JSON at /api/v1/data-status (no API key needed) for your own monitoring. AI assistants connected to Goalie can read it with the get_data_status tool.