TickerInside status

Checks of the website, the JSON API and the MCP server every five minutes, and of the nightly data update, with 90 days of results.

Follow updates uptime.json

All systems operational

Last check at 00:40 UTC on 16 Oct 2026, read when this page was built.

Uptime by day

One bar a day in UTC, today on the right. Point at a day for its figures, which the table under the rows also lists.

Website

Operational

A fund page, /etf/voo/, requested through the public address every five minutes.

90 days ago30 days ago100% uptime since 26 Sep100% uptime since 26 SepToday

16 Oct 2026, today so far: all 9 checks passed

Median answer 58 ms and 95th percentile 119 ms over the last 24 hours.

JSON API

Operational

The API index, /api/v1/index.json, which must parse and list the funds.

90 days ago30 days ago100% uptime since 26 Sep100% uptime since 26 SepToday

16 Oct 2026, today so far: all 9 checks passed

Median answer 56 ms and 95th percentile 116 ms over the last 24 hours.

MCP server

Operational

An initialize request to /mcp, which must answer with the server's name.

90 days ago30 days ago100% uptime since 26 Sep100% uptime since 26 SepToday

16 Oct 2026, today so far: all 9 checks passed

Median answer 42 ms and 95th percentile 102 ms over the last 24 hours. Server version 1.14.0.

Nightly data update

On time

The last build, read from status.json: due by 02:00 UTC after every weekday.

90 days ago30 days ago97.87% on time since 26 Sep97.87% on time since 26 SepToday

16 Oct 2026, today so far: on time at all 9 checks

Last build on 16 Oct 2026, prices through 15 Oct 2026. Next build due by 16 Oct 2026 at 02:00 UTC.

  • Every check passed, or the update was on time
  • Some checks failed, or the update was late
  • Down, with an incident
  • No check that day, as before the checks began on 26 Sep 2026
Every day on record, as a table

The share of checks that passed each day, and how many were made; for the update, the share that found it on time. Times are UTC.

DayWebsiteJSON APIMCP serverNightly data update
100% of 9100% of 9100% of 9100% of 9
100% of 288100% of 288100% of 288100% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 252100% of 252100% of 252100% of 252
100% of 287100% of 287100% of 287100% of 287
100% of 288100% of 288100% of 288100% of 288
100% of 287100% of 287100% of 28798.60% of 287
100% of 288100% of 288100% of 288100% of 288
100% of 287100% of 287100% of 28798.25% of 287
100% of 288100% of 288100% of 28866.31% of 288
100% of 288100% of 288100% of 28896.18% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 288100% of 288100% of 288100% of 288
100% of 54100% of 54100% of 54100% of 54

Past incidents

An incident opens after two failed checks in a row and closes after two that pass, so it is timed to within five minutes. Each is listed on the day it began, in UTC.

No incidents so far today.

No incidents.

No incidents.

No incidents.

No incidents.

No incidents.

  • Nightly data update lateResolved

    From 02:00 to 02:25 UTC, 25 minutes. Cause: the nightly build had not run by its deadline.

Earlier days with an incident

  • Nightly data update lateResolved

    From 02:00 to 02:25 UTC, 25 minutes. Cause: the nightly build had not run by its deadline.

  • Nightly data update lateResolved

    From 02:00 to 10:05 UTC, 8 hours 5 minutes. Cause: the nightly build had not run by its deadline.

  • Nightly data update lateResolved

    From 02:00 to 02:55 UTC, 55 minutes. Cause: the nightly build had not run by its deadline.

The latest data update

What the build that published this page reported in status.json. A build runs every weekday night after 22:00 UTC and is due by 02:00 UTC the next morning.

Build
16 Oct 2026, 00:41 UTC
Prices through
15 Oct 2026
5,322 funds and stocks with a weekly series
Issuer files
624 funds
Newest 14 Oct 2026, oldest 1 Oct 2026
SEC filings
2,049 funds
Data set 2026q3, quarter ends 31 Jan 2026 to 31 Aug 2026
Pages dated as changed
42 of 1,180

The fetch tried 578 issuer files and read and accepted 545, 17 of them dated later than the file held before. 79 funds are served from an earlier file, and no fund with a file here failed; 33 other funds failed that have no issuer file here, such as fixed income funds.

IssuerFundsNewest fileOn an earlier fileFailed that night
iShares2892None
Invesco1530None
State Street SPDR930None
Global X8977None

By the date of their file: 544 dated 14 Oct 2026, 1 dated 13 Oct 2026, 75 dated 12 Oct 2026, 2 dated 8 Oct 2026 and 2 dated 1 Oct 2026.

Follow this page

A feed for people, and the two files this page is drawn from for programs.

Incident feed
Atom, one entry per incident, open or resolved. It is written with each nightly build, so an incident reaches it with the next build rather than the moment it opens.
uptime.json
The checks as they stand, recomputed every five minutes: the state of each, 90 days of daily figures, the incidents and the deploys. This page reads it again when it opens.
status.json
What each nightly build did: the date of each layer of the data, the funds still on an earlier file, and the pages it dated as changed.

Both files are free to read with no key, and their fields are documented under Status on the API page. The checks go through the public address, as a visitor's request would, and a five-minute slot with no check counts as no data, never as up.

This page and its checks run on the same Cloudflare account as the site, so an outage of Cloudflare itself takes them down together; Cloudflare's own status page reports those.