Shipley Farms System Status
Signature Beef · Vilas, North Carolina · No Shortcuts Since 1872
| State | Wire value | Recorded when |
|---|---|---|
| OPERATIONAL | operational | 2xx or 3xx in under 4000 ms |
| DEGRADED | degraded | slow response, HTTP 429, HTTP 401 or 403, or a 200 with a suspiciously small body |
| OUTAGE | outage | 5xx, timeout, connection failure, or slower than 12000 ms |
| NO DATA | unknown | no check ran, or the probe has stopped. Excluded from every percentage on this page |
01Components, customer-facing
90 day history for Website: 1 days measured. 89 days not monitored (2026-07-01, 2026-07-02, 2026-07-03, 2026-07-04, 2026-07-05, 2026-07-06, and others). no outage or degraded day recorded.
90 day history for Product catalog: 1 days measured. 89 days not monitored (2026-07-01, 2026-07-02, 2026-07-03, 2026-07-04, 2026-07-05, 2026-07-06, and others). no outage or degraded day recorded.
90 day history for Cart: 1 days measured. 89 days not monitored (2026-07-01, 2026-07-02, 2026-07-03, 2026-07-04, 2026-07-05, 2026-07-06, and others). no outage or degraded day recorded.
90 day history for Customer accounts: 1 days measured. 89 days not monitored (2026-07-01, 2026-07-02, 2026-07-03, 2026-07-04, 2026-07-05, 2026-07-06, and others). outage on 2026-09-28.
90 day history for Wholesale: 1 days measured. 89 days not monitored (2026-07-01, 2026-07-02, 2026-07-03, 2026-07-04, 2026-07-05, 2026-07-06, and others). no outage or degraded day recorded.
90 day history for Gift cards: 1 days measured. 89 days not monitored (2026-07-01, 2026-07-02, 2026-07-03, 2026-07-04, 2026-07-05, 2026-07-06, and others). degraded on 2026-09-28.
01bComponents, platform
90 day history for Storefront API: 1 days measured. 89 days not monitored (2026-07-01, 2026-07-02, 2026-07-03, 2026-07-04, 2026-07-05, 2026-07-06, and others). no outage or degraded day recorded.
90 day history for TLS certificate: 1 days measured. 89 days not monitored (2026-07-01, 2026-07-02, 2026-07-03, 2026-07-04, 2026-07-05, 2026-07-06, and others). no outage or degraded day recorded.
01cResponse time, last 24 hours
02Incident history
2026-09-28
OUTAGE Customer accounts 1 min, 05:32 to 05:32. Slow response
DEGRADED Gift cards 1 min, 05:32 to 05:32. Slow response
2026-09-27
No incidents reported.
2026-09-26
No incidents reported.
2026-09-25
No incidents reported.
2026-09-24
No incidents reported.
2026-09-23
No incidents reported.
2026-09-22
No incidents reported.
2026-09-21
No incidents reported.
2026-09-20
No incidents reported.
2026-09-19
No incidents reported.
2026-09-18
No incidents reported.
2026-09-17
No incidents reported.
2026-09-16
No incidents reported.
2026-09-15
No incidents reported.
03Machine-readable interface
Every file below sits beside this page and is regenerated on the same schedule. They are static, cacheable, and require no key.
| File | Contents |
|---|---|
| status.json | Current state of every public component with 90 day uptime. The canonical resource. Validates against schema.json. |
| status.txt | The same reading as plain text. The first line is a single token: OPERATIONAL, DEGRADED, PARTIAL_OUTAGE, MAJOR_OUTAGE or UNKNOWN. |
| uptime.json | Per day, per component check counts across the 90 day window. A null component means no checks ran that day. |
| feed.xml | Atom feed of incidents, open and resolved. |
| schema.json | JSON Schema for status.json. |
| llms.txt | How to consume all of the above, written for automated readers. |
| index.html | This page. Component rows carry data-component, data-status, data-uptime-90d and data-checks-90d attributes. |
Examples
# is the store up right now curl -s https://shipleyfarmsbeef.com/files/status.txt | head -1 # one component, with jq curl -s https://shipleyfarmsbeef.com/files/status.json \ | jq -r '.components[] | select(.id=="cart") | .status' # fail a deploy gate when anything is not operational test "$(curl -s https://shipleyfarmsbeef.com/files/status.json | jq '.status.severity')" -eq 0
Check stale before anything else
When stale is true the probe has missed several runs, every component reports unknown, and the file is evidence of nothing except that nobody is measuring. It is not evidence the store is up and it is not evidence the store is down.
Match on id, never on name
Component ids are stable and will not change without a version bump. Display names get reworded.
Branch on severity
0 operational, 1 unknown, 2 degraded, 3 partial outage, 4 major outage. The severity integer is the field designed to be compared.
Uptime counts checks, not minutes
Days with no checks are excluded from the denominator. In uptime.json a null component means no checks ran that day: it is neither zero nor full.
Polling etiquette
Poll no more than once a minute. These files are static and regenerate every few minutes, so anything faster only costs bandwidth. Honour caching headers.
Reading is welcome, checkout is not automated
Reading status needs no permission or key. Checkout is a different matter and is covered at https://shipleyfarmsbeef.com/agents.md. If you are helping someone shop, build the cart and hand your buyer a link to approve and pay. Do not automate payment.
Corrections and requests
Something wrong with this data, or a component you wish were covered: beef@shipleyfarmsbeef.com
04Measurement method
What is measured
Every 5 minutes an unauthenticated HTTP GET is sent to each component above from a machine outside the hosting platform, and the response code, body size and elapsed time are recorded. Nothing on this board is self-reported by the site being measured, so a green reading is independent evidence rather than a claim.
How a state is decided
Operational is a 2xx or 3xx response in under 4000 ms. Degraded is a slow response, an HTTP 429, an HTTP 401 or 403, or a 200 carrying a suspiciously small body. Outage is a 5xx, a timeout, or a connection failure. A response that arrives but takes longer than 12000 ms is recorded as an outage on the grounds that nobody waits that long.
How uptime is counted
Uptime counts checks, not minutes. Days on which no check ran are excluded from the denominator rather than assumed healthy, and are drawn as hatched bars. A check that never ran is never counted as a passing one. This history covers 1 of 90 days and 18 checks so far.
What a green board does not prove
Every check is unauthenticated and read-only, so nothing behind a sign-in is measured. Checkout, payment capture, the register and order placement all require a session. Green means the storefront is serving pages, not that a card will clear.
When the probe stops
If the newest check is older than three intervals the board says so at the top, reports every component as Unknown, and states plainly that nothing on the page is evidence the site is up. A stale board is never a green board.